Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Who's it for Active job seekers who apply to 10–30 roles a week and lose track of which application is at what stage. Built for anyone tired of manually updating a spreadsheet every time a recruite...
n8n-nodes-base.stickynote, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.merge, n8n-nodes-base.if, n8n-nodes-base.scheduletrigger, @n8n/n8n-nodes-langchain.chainllm, n8n-nodes-base.googlesheets
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Pratistha Thapa.
Original n8n.io sourceActive job-seekers who apply to 10–30 roles a week and lose track of which application is at what stage. Built for anyone tired of manually updating a spreadsheet every time a recruiter replies — or worse, realizing their tracker has been lying to them for two weeks.
This workflow runs every morning at 9 AM, scans your Gmail for job-application emails, and uses GPT-4o-mini to extract three things from each one:
It then writes structured rows into a Google Sheet — one row per application, identified by a Match Key of Company | Position. New applications get appended automatically. Status changes for existing rows (Applied → Interview, Interview → Offer / Rejected) are gated behind a one-tap email approval, so an LLM misclassification can never silently demote a row.
Daily 9 AM Trigger ↓ Fetch Gmail (filtered by ATS senders & job-keyword subjects, last 2 days) ↓ Process Email Data (clean & truncate body to 4000 chars) ↓ Extract Key Information (GPT-4o-mini, structured JSON output) ↓ Format Data (build Match Key) ↓ Filter Valid Job Updates ──→ Other ──→ "Other app" sheet tab ↓ Branch by Status ├─ Applied ──→ Track New Application (append row) └─ Interview / Offer / Rejected ↓ Aggregate into single digest ↓ Email & Wait for Approval (sendAndWait) ↓ Merge → Split → Update Application (match by Match Key)
Key design choices:
Company | Position should stay one row.Prerequisites:
gpt-4o-mini accessSteps:
Sheet1 — columns: Thread ID | Match Key | Date | Company | Position | Status | Modified DateOther app — same columns (used for unclassifiable emails)Import this template. Open n8n → Workflows → Import from File. n8n will flag missing credentials.
Configure three credentials:
Open AI nodeFetch Job Application Emails and Email Updates & Wait for ApprovalYOUR_GOOGLE_SHEET_ID → your real sheet ID (from the sheet's URL)[email protected] → the address that should receive approval digestsTest it manually. Click "Execute workflow" and verify the Gmail node returns recent emails, the LLM extracts clean JSON, and a sample appears in your sheet.
Activate. Toggle the workflow to active and it will run daily at 9 AM.
Daily 9 AM Trigger to any cron expression.newer_than:2d. Bump to 7d if your daily run sometimes fails — the workflow handles re-processed emails idempotently because Match Key updates are no-ops on identical data.Extract Key Information includes English and French status phrases. Add your language's equivalents to each section (Rejected, Applied, etc.).options.limitWaitTime.values.resumeAmount (in hours) to the approval node if you want stale digests to auto-cancel.Manual spreadsheet tracking lasted me two weeks before it became the chore I'd skip on busy days. By week three the sheet was lying to me — half the "Applied" rows were rejections I hadn't logged yet. So I built this. It's not a system of record; it's a guided draft I skim once a week. The bones might be useful to someone else.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 31 workflow blocks. Download the JSON for the full node graph.
| Workflow | Track daily job applications from Gmail to Google Sheets via GPT-4o-mini with approval |
|---|---|
| Complexity | advanced |
| Nodes | 31 |
| Categories | Personal Productivity, AI Summarization |
| Author | Pratistha Thapa |
| Published | 04 May 2026 |
Use the JSON export at /data/workflows/15463/15463.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Who's it for Active job seekers who apply to 10–30 roles a week and lose track of which application is at what stage. Built for anyone tired of manually updating a spreadsheet every time a recruite...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity, AI Summarization use case.