OpenRouter + Gmail: job digests you actually read
You find a promising job post, then lose it. Or you skim 30 listings and realize only two were relevant. The tabs pile up, the details blur, and “I’ll check again later” turns into missed opportunities.
This OpenRouter Gmail digest setup hits freelancers first, honestly. But agency leads tracking pipeline and ops folks doing light market research feel it too. You get one clean email that summarizes what matters, with links ready to click.
Below, you’ll see how the workflow pulls new n8n forum job posts, uses OpenRouter to write tight summaries, and delivers a formatted digest to your inbox on a schedule.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: OpenRouter + Gmail: job digests you actually read
flowchart LR
subgraph sg0["Run Weekly on Monday Morning Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Each post"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/html.dark.svg' width='40' height='40' /></div><br/>Extract title & description"]
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Last 7 days", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get list page"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/html.dark.svg' width='40' height='40' /></div><br/>Extract posts"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Merge objects"]
n6@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n7@{ icon: "mdi:brain", form: "rounded", label: "OpenRouter Chat Model", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Generate Job Summary", pos: "b", h: 48 }
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Combine Job Data & Summary"]
n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Format Summary Output"]
n11["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Aggregate All Jobs"]
n12@{ icon: "mdi:message-outline", form: "rounded", label: "Send Weekly Job Digest", pos: "b", h: 48 }
n13@{ icon: "mdi:play-circle", form: "rounded", label: "Run Weekly on Monday Morning", pos: "b", h: 48 }
n0 --> n1
n0 --> n8
n2 --> n9
n2 --> n0
n4 --> n5
n3 --> n4
n5 --> n2
n11 --> n12
n8 --> n9
n10 --> n11
n7 -.-> n8
n6 -.-> n8
n9 --> n10
n1 --> n9
n13 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n13 trigger
class n6,n8 ai
class n7 aiModel
class n2 decision
class n0,n3 api
class n5,n10,n11 code
classDef customIcon fill:none,stroke:none
class n0,n1,n3,n4,n5,n9,n10,n11 customIcon
The Problem: Job hunting turns into tab chaos
Keeping up with new work on the n8n community job board sounds simple until you do it for a few weeks. You check “real quick,” then you’re deep in posts that don’t fit your stack, your budget, or your timeline. And even when a listing is good, you still have to extract the important parts (what they need, what tools they mention, how urgent it is) and remember where you saw it. Do that Monday after Monday and you’re spending the best part of an hour just to stay informed.
The friction compounds. Here’s where it breaks down.
- You waste time rereading the same posts because there’s no weekly “single view” of what’s new.
- Good opportunities slip by because the key requirement is buried in a long paragraph.
- Copying titles, dates, and links into notes is tedious, and mistakes happen more than you’d like.
- You end up reacting late, which is brutal when multiple people reply fast.
The Solution: AI-summarized job posts delivered to Gmail
This workflow monitors the n8n forum job board on a schedule (the default is a Monday run) and builds a digest of posts from the last 7 days. It starts by fetching the listing index, scraping out the job links, and then visiting each posting page to pull the real details like title, date, and description. Next, it sends each listing through an OpenRouter chat model, which writes concise summaries focused on requirements and “what the client actually wants.” Finally, everything gets merged into a clean collection and compiled into a formatted email you can skim in minutes. You open one message, scan summaries, and click through only when it’s worth your attention.
The workflow begins with a scheduled trigger, then scrapes and filters to keep only recent posts. From there, OpenRouter generates consistent summaries and n8n assembles them into a single Gmail-ready digest.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you check the n8n job board three times a week. Each time, you spend maybe 15 minutes opening posts, skimming, and saving links, so that’s about 45 minutes weekly. With this workflow, you spend about 2 minutes reading one email, then another 5 minutes clicking into the two or three posts that look real. The browsing part basically disappears, while you still catch the same opportunities (often faster).
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- OpenRouter for AI summaries of job listings
- Gmail (or SMTP email) to send the digest to your inbox
- OpenRouter API key (get it from your OpenRouter account dashboard)
Skill level: Beginner. You’ll paste an API key, connect email, and tweak a couple of filters if you want.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Weekly trigger fires. The workflow runs on a schedule (default is Monday) so you’re not thinking about it, and you’re not relying on “I’ll remember to check later.”
Job links are gathered and filtered. n8n fetches the forum index page, scrapes out the listing URLs, then filters the set down to posts from the last 7 days so the digest stays tight.
Each posting gets summarized by OpenRouter. The workflow pulls the title and description from every job page, then asks an OpenRouter chat model to produce a concise overview that’s easier to scan than raw forum text.
A formatted digest hits your inbox. n8n merges the scraped metadata with the AI summaries, compiles the collection, and sends a single email so you can read, click, and reply quickly.
You can easily modify the date range to run daily instead of weekly based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
Set up the weekly schedule so the workflow runs every Monday morning and starts the scraping process.
- Add and open Scheduled Monday Trigger.
- Set the cron rule to
0 9 * * 1in Rule → Interval → cronExpression. - Connect Scheduled Monday Trigger to Fetch Listing Index.
Step 2: Connect the Listing Source
Fetch the jobs index page and extract the job links and post dates.
- Open Fetch Listing Index and set URL to
https://community.n8n.io/c/jobs/13. - Connect Fetch Listing Index to Scrape Job Links.
- In Scrape Job Links, keep Operation as
extractHtmlContentand confirm extraction values for jobLink and date use the provided CSS selectors. - Connect Scrape Job Links to Combine Link Records.
Step 3: Filter the Weekly Set and Fetch Individual Posts
Merge link/date arrays into records and keep only jobs from the last 7 days, then request each job page.
- In Combine Link Records, keep the JavaScript that maps
jobLinkanddateinto a unified record array. - Open Filter Recent Week and set the condition to dateTime → after with Left Value
{{ $json.date }}and Right Value{{$now.minus({days: 7})}}. - Connect Filter Recent Week to both Merge Details and Summary and Retrieve Posting Page in parallel.
- In Retrieve Posting Page, set URL to
{{ $json["jobLink"] }}.
Retrieve Posting Page outputs to both Parse Title and Summary and Draft Job Overview in parallel, so the HTML is parsed and summarized at the same time.
Step 4: Set Up Parsing and AI Summarization
Extract job title/description and use the LLM to generate a structured summary.
- In Parse Title and Summary, keep Operation as
extractHtmlContentand ensure the extraction values includejobTitleandjobDescriptionfrom the meta tags. - Open Draft Job Overview and confirm Text is set to
=<content> {{ $('Retrieve Posting Page').item.json.data }} </content>. - Ensure Draft Job Overview uses OpenRouter Chat Engine as its language model and Structured Result Parser as its output parser.
- Credential Required: Connect your
openRouterApicredentials in OpenRouter Chat Engine.
Note: Structured Result Parser is a sub-node; add credentials to the parent OpenRouter Chat Engine, not the parser.
Step 5: Merge, Refine, and Compile the Job Collection
Combine the parsed details, filter outputs, and AI summaries into a clean collection for the email digest.
- In Merge Details and Summary, set Mode to
combine, Combine By tocombineByPosition, and Number Inputs to3. - Open Refine Summary Payload and keep the JavaScript that maps
summary:item.json.output.summaryand removesoutput. - Open Compile Job Collection and keep the JavaScript that returns
{data: items}. - Connect Merge Details and Summary → Refine Summary Payload → Compile Job Collection.
Step 6: Configure the Email Digest Output
Send the compiled jobs as a formatted HTML email.
- Open Dispatch Weekly Digest and set To Email and From Email to your address (replace
[YOUR_EMAIL]). - Keep Subject as
Job Opportunities. - Ensure HTML is set to the provided expression that builds the grouped job digest:
{{(() => { ... })()}}. - Credential Required: Connect your
smtpcredentials in Dispatch Weekly Digest. - Connect Compile Job Collection to Dispatch Weekly Digest.
Step 7: Test and Activate Your Workflow
Run a manual test to validate scraping, summarization, and email delivery before turning the schedule on.
- Click Execute Workflow and verify Fetch Listing Index returns the forum HTML and Scrape Job Links outputs arrays for
jobLinkanddate. - Confirm Filter Recent Week only passes items newer than the last 7 days.
- Check that Draft Job Overview outputs structured summaries and Merge Details and Summary combines all three inputs correctly.
- Verify Dispatch Weekly Digest sends a formatted email with grouped sections and clickable job titles.
- Once successful, toggle the workflow to Active so Scheduled Monday Trigger runs weekly.
Common Gotchas
- OpenRouter credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and your OpenRouter dashboard usage/keys first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Gmail/SMTP sending can fail due to “less secure app” settings or provider limits. Check your email provider’s security settings and the n8n execution log for authentication errors.
Frequently Asked Questions
About 10 minutes if you already have your API key and email ready.
No. You’ll mostly connect accounts and paste an API key. Any optional tweaks (like keyword filters) are simple edits inside n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenRouter model costs, which are usually pennies per digest depending on the model and how many posts are summarized.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s the kind of customization that actually pays off. Change the Scheduled Monday Trigger to a daily schedule, then adjust the “last 7 days” filter to something like “last 24 hours.” If you want only certain jobs, add a keyword check right after the text is extracted (after parsing the title/summary) so you filter before paying for AI summaries. You can also tweak the AI prompt in the OpenRouter summarization step so it always pulls out budget, timeline, and required tools in the same order.
Usually it’s an expired or incorrect API key. Regenerate the key in OpenRouter, then update the credential in n8n and rerun one test execution. If the key is fine, check rate limits or account billing, because some models will reject requests when you hit usage caps.
Dozens per run is normal, and if you self-host it mainly depends on your server and your OpenRouter limits.
For this use case, n8n is usually the better tool because scraping + parsing + merging + AI summarization is more than a simple two-step Zap. You can branch, filter, and reshape data without paying extra for every path, and self-hosting removes execution anxiety if you run it often. Zapier or Make can still work if you keep the scope small and avoid heavy HTML parsing. The bigger issue is control: with n8n you can tune the summarization prompt, the date logic, and the final email formatting in one place. Talk to an automation expert if you want help choosing.
Set this up once and your Monday “job browsing session” becomes one email you actually finish reading. The workflow handles the repetitive scanning so you can spend your time applying, following up, and shipping work.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.