Google Jobs + Gmail: job digests with cover drafts

Job hunting can turn into a daily browser scavenger hunt. Ten tabs open, the same listings showing up twice, and you still end up rewriting the same “excited to apply” paragraph from scratch.

Recruiters don’t see this side, but job seekers definitely do. And if you’re a career coach helping clients stay consistent, you know how quickly momentum dies without a system. This job digest automation gives you a clean daily shortlist plus cover letter drafts you can actually use.

Below you’ll see what the workflow does, what you get out of it, and what you’ll need to run it without babysitting anything.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Jobs + Gmail: job digests with cover drafts

Click to explore

flowchart LR

    subgraph sg0["Schedule Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule", pos: "b", h: 48 }
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Settings", pos: "b", h: 48 }
        n2["<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/>Search Google Jobs"]
        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/>Search RemoteOK"]
        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/merge.svg' width='40' height='40' /></div><br/>Merge"]
        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/>Process Jobs"]
        n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Results", pos: "b", h: 48 }
        n7@{ icon: "mdi:message-outline", form: "rounded", label: "No Results Email", pos: "b", h: 48 }
        n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Jobs", 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/code.svg' width='40' height='40' /></div><br/>Extract Job"]
        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/httprequest.dark.svg' width='40' height='40' /></div><br/>Generate Letter"]
        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/>Combine Letter"]
        n12@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
        n13["<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 Email"]
        n14@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email", pos: "b", h: 48 }
        n4 --> n5
        n0 --> n1
        n1 --> n2
        n1 --> n3
        n12 --> n13
        n8 --> n9
        n9 --> n10
        n13 --> n14
        n5 --> n6
        n6 --> n7
        n6 --> n8
        n11 --> n12
        n10 --> n11
        n3 --> n4
        n2 --> n4
    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 n0 trigger
    class n6 decision
    class n2,n3,n10 api
    class n5,n9,n11,n13 code
    classDef customIcon fill:none,stroke:none
    class n2,n3,n4,n5,n9,n10,n11,n13 customIcon

The Problem: Daily job searching turns into busywork

Most job searches don’t fail because you aren’t qualified. They fail because the process is exhausting. You check Google Jobs, then RemoteOK, then a couple other sites “just in case.” You copy a description into notes, try to remember where you saw it, and later realize you already applied to something similar last week. Meanwhile, the roles that actually fit you get buried under duplicates, vague postings, and listings that are already old.

It adds up fast. Here’s where it usually breaks down.

Searching two sources every day can eat about 2 hours, even when you “keep it quick.”
Duplicates and near-duplicates waste attention, so you miss the few high-quality roles that were worth a thoughtful application.
Cover letters become a bottleneck, because you’re rewriting the same structure again and again.
When results are scattered across tabs, you can’t build a repeatable routine (and consistency is the whole game).

The Solution: Daily job digests with AI cover drafts

This workflow runs on a schedule (every 24 hours) and does the job searching for you. It queries Google Jobs using SerpAPI and pulls RemoteOK listings in parallel, then merges everything into a single set of results. Next, it cleans the data, filters out low-quality or duplicate postings, and checks if there’s anything worth sending. If the list is empty, you get a simple “no results” email so you don’t wonder if the automation broke.

When there are matches, it batches the best items (up to about four per day), extracts the useful details, and asks OpenAI (GPT-3.5 in this template) to write a short, tailored cover letter draft for each role. Finally, n8n builds a polished HTML email digest with job snippets, a clear “Apply” button per role, plus the cover draft so you can edit quickly and submit with confidence.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It searches Google Jobs (via SerpAPI) and RemoteOK on a daily schedule.
It merges results, then removes duplicates and low-signal listings.
It generates a unique 60-word cover letter draft per job using OpenAI.
It sends a formatted Gmail/SMTP digest, or an empty alert if nothing matched.

Cut a 2-hour daily search down to a quick inbox review.
Apply faster because the “first draft” work is already done.
Cleaner decision-making, since you see a small shortlist instead of 40 tabs.
Fewer duplicate applications and fewer “where did I see that?” moments.
A consistent routine you can stick with, even on busy weeks.

Example: What This Looks Like

Say you check Google Jobs and RemoteOK every weekday. If you spend about an hour per site (searching, opening listings, skimming, copying notes), that’s roughly 2 hours a day, or about 10 hours a week. With this workflow, you spend maybe 10 minutes reading one email and opening the best “Apply” links. The cover drafts mean you’re starting from something usable, not a blank page, so you can often finish an application in one focused pass.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
SerpAPI to query Google Jobs results
OpenAI for generating cover letter drafts
SMTP email (Gmail works) to send the daily digest
SerpAPI API key (from your SerpAPI dashboard)
OpenAI API key (from OpenAI “View API keys”)

Skill level: Beginner. You’ll paste API keys, connect email credentials, and edit a few search settings like role and location.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A scheduled run kicks it off. The workflow triggers every 24 hours, then loads your defaults like search query, location, and the email address that should receive the digest.

Two job sources are queried in parallel. One request hits Google Jobs through SerpAPI, and another pulls RemoteOK results. n8n merges them into a single list so you’re not comparing sites by hand.

Results get cleaned and checked. A processing step removes duplicates and trims out low-quality items, then an “if” check decides what happens next. No matches means a simple alert email so you know the workflow ran.

Cover drafts are generated and sent. The remaining jobs are batched, details are extracted, OpenAI creates short cover drafts, and everything is assembled into an HTML email with snippets and apply links that land in your inbox.

You can easily modify the search query to target different roles, or adjust the daily number of jobs included 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 the workflow schedule so the job search and lettering process runs automatically.

Add and open Scheduled Trigger.
Define your desired schedule (for example, daily or weekly) to control when the workflow runs.
Connect Scheduled Trigger to Configure Defaults.

Step 2: Connect Job Listing Sources

Configure the two API calls that fetch job listings, which run in parallel after defaults are set.

Open Configure Defaults and set any fields you want to reuse across the workflow (search terms, locations, or shared parameters).
Ensure Configure Defaults outputs to both Query Google Listings and Query RemoteOK Listings in parallel.
Open Query Google Listings and configure the HTTP request settings (URL, method, headers, query parameters) for your Google job listings source.
Open Query RemoteOK Listings and configure the HTTP request settings for RemoteOK.
Connect both nodes into Combine Search Results (Google to input 1, RemoteOK to input 2).

Configure Defaults outputs to both Query Google Listings and Query RemoteOK Listings in parallel.

Tip: If either API requires authentication, add the appropriate HTTP credentials directly in the corresponding Query Google Listings or Query RemoteOK Listings node.

Step 3: Set Up Job Processing and Validation

Process the combined results, validate if any jobs were found, and split results into batches for letter generation.

Open Combine Search Results and confirm it is set to merge data from both sources.
Open Process Job Records and implement logic to normalize or filter job records.
Open Validate Results and configure the IF condition that determines whether jobs exist.
Connect the “true” output of Validate Results to Batch Job Items and the “false” output to Dispatch Empty Alert.
Open Batch Job Items and set the batch size to control how many jobs are processed per loop.

⚠️ Common Pitfall: If Validate Results is not configured correctly, you may always trigger Dispatch Empty Alert or never process jobs. Test with sample data to confirm the condition logic.

Step 4: Generate and Aggregate Cover Letters

Extract job details, generate draft letters, and assemble a combined email-ready output.

Open Extract Job Details and implement logic to isolate key fields (company, role, URL, requirements).
Open Generate Cover Draft and configure the HTTP request to your letter-generation service.
Open Assemble Final Letter and format the final text per job.
Open Aggregate Letters and configure it to collect all letters into a single dataset.
Open Compose Email Body and format the aggregated letters into your desired email structure.

Tip: If Generate Cover Draft calls an AI or external service, verify request payloads and authentication are correct before running large batches.

Step 5: Configure Output and Empty Results Alert

Send results and handle the no-results scenario using the email nodes.

Open Dispatch Email and set recipient, subject, and message fields to deliver the compiled letters.
Open Dispatch Empty Alert and configure a clear “no jobs found” notification for your inbox.
Ensure Compose Email Body connects to Dispatch Email and Validate Results connects to Dispatch Empty Alert on the false branch.

Credential Required: Connect your Email credentials in Dispatch Email.

Credential Required: Connect your Email credentials in Dispatch Empty Alert.

Step 6: Test and Activate Your Workflow

Verify each stage produces the expected output and then turn the workflow on for production use.

Click Execute Workflow to run a manual test from Scheduled Trigger.
Confirm Query Google Listings and Query RemoteOK Listings return data and Combine Search Results merges them correctly.
Check that Validate Results routes to Batch Job Items when results exist and to Dispatch Empty Alert when none are found.
Verify Dispatch Email sends an email containing the aggregated letters from Aggregate Letters and Compose Email Body.
Toggle the workflow to Active once test outputs are correct.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

SerpAPI credentials can expire or hit free-tier limits. If Google Jobs results suddenly stop, check your SerpAPI dashboard usage and the API key stored in n8n credentials.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your voice (role, industry, a couple proof points) early or you will keep rewriting the drafts every day.

Frequently Asked Questions

How long does it take to set up this job digest automation?

About 20 minutes if you already have your API keys.

Do I need coding skills to automate job digests?

No. You’ll mainly paste credentials and change your search query and location.

Is n8n free to use for this job digest automation workflow?

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 SerpAPI and OpenAI usage, which is often around a few dollars a month for this daily digest setup.

Where can I host n8n to run this job digest automation?

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.

Can I customize this job digest automation workflow for multiple job titles?

Yes, but you’ll want to do it intentionally. The simplest approach is duplicating the workflow and changing the Configure Defaults settings (query, location, and recipient email) so each role has its own digest. If you’d rather keep one workflow, you can store multiple queries in Google Sheets and loop through them in the “Process Job Records” / batching section, then send separate emails per query.

Why is my Gmail connection failing in this workflow?

Most of the time it’s authentication. If you’re using Gmail via SMTP, you usually need 2FA enabled and an App Password, not your normal Google password. Also confirm the “from” address in the email node matches the SMTP user, because Gmail can reject sends that look spoofed. If it worked once and then stopped, re-save the SMTP credential and check Google’s security alerts for a blocked sign-in.

How many job listings can this job digest automation handle?

Plenty for a personal daily search.

Is this job digest automation better than using Zapier or Make?

Often, yes, because this workflow needs multi-source scraping, filtering, batching, and custom email formatting in one run. In Zapier, you can do it, but you’ll usually end up paying more once you add paths, loops, and higher task volume. Make is flexible, but this template’s “code + AI + HTML digest” approach tends to feel cleaner in n8n, especially if you want to self-host. The honest answer is that it depends on how picky you are about filtering and formatting. Talk to an automation expert if you’re not sure which fits.

This workflow turns job search time into application time. Set it once, then let your inbox do the heavy lifting.

Google Jobs + Gmail: job digests with cover drafts

How This Automation Works

n8n Workflow Template: Google Jobs + Gmail: job digests with cover drafts

The Problem: Daily job searching turns into busywork