So something that has happened to me so far when working with new people is that after a large majority of projects, the person I’m working with asks me, ‘What else can you do for me?’ or says we need to work more together because they’re really impressed. The craziest part is that I’m not doing anything crazy. When I get the job, I build the solution as fast as possible, ask for feedback, and then keep building until it’s done. This is actually how the people I work with end up upselling themselves on more things from me. What I’m trying to say is that once I get hired, I try to deliver the automation within 2 to 4 days. Most of the time it goes even faster, depending on how complex it is. By doing that, I get repeat business and more orders. So for anyone out there who wants to get clients, when you get that one, overdeliver so they’ll pay you more.

Guess what? It's exactly 80 days ago, when I started with a local n8n setup. Not more than some "maybe" and the desire to do something. 80 days ago. That was Oct, 1st. I accepted the challenge. The last 80 days I spent hours building, supporting, coaching, reading. I texted some friends and family. I registered a server. A domain. Participated in a challenge - successfully. Went through the 30 Day accountability plan here. --> Thanks to @Duy Bui Amazing how far I have come in this short time! 80 out of 360 days (roughly about 22%). I got stuck - and you helped me to get unstuck! --> Thanks to @Chris Jadama, I still remember your Loom spotting my HTTP request issue, spot on. I found friends 😊 --> Thank you, @AI Automate Services 🥰 My lesson? Conclusion? I'm right at the beginning. Next year is around the corner. It will be good, really good. Some fresh new 365 days. Check this out. This, was meant to encourage you. Every single one of you. You might be at the beginning or before the finish line, doesn't matter, everyone can do it, everyone can share. And if you need some inspiration, check out @Sarah Martinez posts. 🎉

I have a client that needs to connect multiple Gmail accounts to the same n8n instance without sharing the n8n interface with their employees. My issue is that if you do not use n8n’s built-in signup via nodes, you do not actually save the credentials inside n8n in a secure way. You can, of course, create a URL with the secret key, ID, and callback URL, then store the access token in an HTTP request to perform actions. However, this means you will need to keep the secret key and ID in that HTTP node forever since you must refresh the token every hour. My question is: has anybody run into this and solved it in a clever way? They want a webpage where their employees can go and sign in, but that is not really how n8n works. As far as I know, n8n is meant more for internal use rather than being used as a SaaS.

- Create a demo that will show a lot of instant proof in no time. It takes time, but if you can land a gig, why not? I made one demo and got the offer without any questions at all. - Some clients will pay just to build things for the sake of building. I’ve run into this multiple times now, and I get paid every single time. - If you’re getting paid, and you know why and how you got paid, you’re on the right path.

HR team was drowning in resumes. Manually reviewing 50 applications took 8 hours. Built automated screening workflow. Now takes 10 minutes. THE PROBLEM: Startup hiring for 3 positions. Received 150 applications in one week. Each resume needed: skills extracted, experience calculated, fit assessment written. Manual process: 10 minutes per resume × 150 = 25 hours of work. THE SOLUTION (N8N WORKFLOW): Manual Trigger → Start batch processing Google Drive node → Retrieves resume files from folder PDF Vector Parse node → Extracts all candidate information Function node → Calculates years of experience per skill PDF Vector AI node → Evaluates candidate fit and seniority HTTP Request node → Posts to Airtable candidate database Slack node → Notifies team with top candidates Total workflow: 6 nodes. Processes any resume format - PDF, Word, even phone photos. WHAT IT EXTRACTS: Personal info: name, email, phone, location, LinkedIn Work history: companies, dates, technologies used per role Education: degrees, institutions, graduation dates Skills: technical and soft skills with experience levels Certifications: current and relevant to role Calculated metrics: total experience, skill proficiency scores THE SCORING LOGIC: Built custom scoring in Function node: ```javascript // Calculate experience score per skill const skillScores = {}; workHistory.forEach(job => { job.technologies.forEach(tech => { if (!skillScores[tech]) skillScores[tech] = 0; skillScores[tech] += job.durationYears; }); }); // Weighted ranking const rankingScore = (totalYears * 0.3) + (skillCount * 0.2) + (certCount * 0.1) + (requirementMatch * 0.4); ``` Assigns tier: A (interview immediately), B (strong candidate), C (consider), D (pass). THE AI ASSESSMENT: PDF Vector AI node writes custom assessment for each candidate: "Evaluates technical depth, leadership experience, culture fit. Determines if candidate is junior, mid-level, senior, or lead material based on scope of past projects."