When should you use it?
- You apply to many similar roles
- Your country has a jobs API
- You want a log of what was sent
Not for: Roles that need hand-written letters; Sending applications without reading them first
What do you need, and what do you get?
You need
- Profile links
- Job source API
- Gmail
- Google Sheet
You get
- Daily shortlist
- Draft cover letter per job
- Application log
How does it work, step by step?
- Feed your profilePoint the workflow at your public profile and portfolio pages.
- Generate queriesLet the model build searches from your skills and preferences.
- Fetch and dedupePull listings from your jobs API and skip any already in the sheet.
- Pick and draftThe model ranks matches and drafts a letter for each.
- Review, send, logYou approve each email before it goes; every result lands in the sheet.
The prompt
Our own prompt, inspired by u/Fresh-Daikon-9408 on r/n8n and written to work in n8n and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Profile summary: {profile}. Job listing: {listing}. 1. Score the match 1-10 and give two reasons. 2. If 7 or above, draft a cover letter under 200 words that cites two specific requirements from the listing and matching experience from my profile. Do not invent experience. 3. Return company, role, link, score and the draft for my review.
Inspired by u/Fresh-Daikon-9408 on r/n8n: I built a fully automated job application pipeline in n8n — daily scheduling, AI cover letters, CV adaptation, and email sending. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The job API is country-specific; swap the node for your market.
- Auto-sent letters with errors hurt you; keep a review step.
Our take
This is a well-built pipeline with two honest notes from its author: the job source is tied to one country, and the resume-compiling branch is optional. The dedupe step against a sheet is what keeps it from spamming the same employer. We changed the send step to a review queue, because a cover letter with the wrong company name does more harm than no letter. Keep answers about salary and work authorization as fixed text you wrote. Prefer the official country job API over scraping random boards. The job API node is country-specific, so swap it for your market. Read each letter for the right company name and role before approving it. The dedupe sheet doubles as a record of every application, which helps when an employer calls back weeks later. Gemini's picks are a ranking, not a verdict; skim the rejected listings occasionally to make sure good roles are not being filtered out by your profile wording.
Where the time goes back: Searching, deduping and first-draft letters run each morning, leaving you to approve and send.
FAQ
Do I need the CV-as-code part?
How big is it?
Source and credit
Inspired by u/Fresh-Daikon-9408 on r/n8n. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I built a fully automated job application pipeline in n8n — daily scheduling, AI cover letters, CV adaptation, and email sending
- Creator
- u/Fresh-Daikon-9408 on r/n8n
- Published on
- Original date
- Feb 19, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- n8n
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.