Google Sheets to Gmail, send ready newsletters fast
Copying links into a doc, opening ten tabs, skimming, summarizing, then fighting with formatting in Gmail is the kind of “small task” that quietly steals your afternoon.
Newsletter writers usually feel it first. But marketing managers and busy founders end up in the same loop, too. This Sheets Gmail automation turns a simple Google Sheets link list into a clean newsletter draft you can send with confidence.
You’ll see how the workflow pulls URLs from Sheets, crawls the pages, summarizes them with GPT-4o, and delivers a polished HTML email through Gmail.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets to Gmail, send ready newsletters fast
flowchart LR
subgraph sg0["Start Workflow Manually Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Start Workflow Manually", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Get Website URLs from Google..", 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/>Crawl and Extract Site Conte.."]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Extracted Results into..", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-vertical", form: "rounded", label: "Map Title, URL, and Page Text", pos: "b", h: 48 }
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/> Combine Articles into Singl.."]
n6@{ icon: "mdi:robot", form: "rounded", label: " Generate HTML Newsletter wi..", pos: "b", h: 48 }
n7@{ icon: "mdi:message-outline", form: "rounded", label: "Send Newsletter via Gmail", pos: "b", h: 48 }
n0 --> n1
n4 --> n5
n1 --> n2
n5 --> n6
n3 --> n4
n2 --> n3
n6 --> n7
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 ai
class n1 database
class n2 api
class n5 code
classDef customIcon fill:none,stroke:none
class n2,n5 customIcon
The Problem: Newsletter Drafts Still Start as Manual Chaos
Curating a newsletter sounds simple until you do it weekly. You collect a handful of links, then you have to read enough of each article to extract the point, rewrite it in your voice, and keep the issue consistent from section to section. The worst part is the context switching: browser tabs, notes, formatting, subject lines, and then Gmail decides to “help” with spacing. It’s easy to miss a key detail, paste the wrong URL, or ship an issue that feels stitched together instead of intentional.
The friction compounds. Here’s where it usually breaks down.
- Reading and summarizing even 6–10 articles can eat about 2 hours, especially when the content is dense.
- Formatting in Gmail becomes a second job, because copying from different sources rarely keeps clean HTML.
- Consistency slips over time, so your “brand voice” becomes whatever mood you’re in that day.
- One bad paste or broken link makes the whole issue feel sloppy (and you only notice after sending).
The Solution: From Google Sheets Links to a Gmail Newsletter Draft
This workflow starts with something you already have: a Google Sheet where column A contains the article URLs you want to include. When you run it (manually, or later on a schedule), n8n pulls those URLs, sends each one to Dumpling AI to crawl and extract readable content, then processes the results one by one so nothing gets mashed together. A formatting step cleans the text and keeps key fields like title and URL in a predictable structure. After that, GPT-4o turns the whole batch into a single newsletter package: a subject line and HTML body that reads like a cohesive issue, not a pile of summaries. Finally, Gmail sends the draft to your inbox or team so you can do a quick review and hit send.
The workflow begins when you launch it in n8n and it reads your URLs from Google Sheets. Dumpling AI fetches the page text, then GPT-4o generates a branded newsletter in HTML. Gmail delivers the finished draft so you’re working from a near-final issue instead of a blank page.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish one curated newsletter per week with 8 links. Manually, you might spend about 10 minutes skimming each article (80 minutes), then another 40 minutes writing clean summaries, plus 30 minutes formatting in Gmail. Call it roughly 2.5 hours. With this workflow, you drop the 8 URLs into Google Sheets and run it: about 5 minutes to prep, then 10–20 minutes of processing time while Dumpling AI and GPT-4o do the heavy lifting. You get a draft email you can tweak and send, usually in under 30 minutes total effort.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store the article URL list.
- Dumpling AI to crawl pages and extract content.
- OpenAI API key (get it from the OpenAI API dashboard).
Skill level: Beginner. You’ll connect accounts, paste API keys, and edit one prompt for tone.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A manual (or scheduled) run kicks things off. In the current setup, you click to launch the workflow in n8n. If you want a weekly newsletter, you can swap the trigger to a Schedule node later.
Your URLs are pulled from Google Sheets. The workflow reads the sheet row data and collects the web addresses you want to curate for this issue.
Dumpling AI crawls each page and returns the raw content. n8n sends each URL to Dumpling’s crawl endpoint, then splits the results so articles get processed one at a time (cleaner summaries, fewer weird merges).
GPT-4o writes the issue and Gmail delivers it. A code step structures the article data, GPT-4o generates a subject line and HTML body, and Gmail sends the formatted newsletter draft to the recipient you choose.
You can easily modify the prompt tone to match your brand voice based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow with a manual execution so you can validate the end-to-end newsletter generation before scheduling.
- Add the Manual Launch Trigger node as the workflow trigger.
- Leave the Manual Launch Trigger parameters empty (this node requires no configuration).
- Optionally keep Flowpast Branding as a visual reference note (it does not affect execution).
Step 2: Connect Google Sheets
Pull the list of website URLs to crawl from a Google Sheet.
- Add the Retrieve Sheet Web Addresses node and connect it to Manual Launch Trigger.
- Set Document to the spreadsheet named
sites. - Set Sheet to
Sheet1. - Credential Required: Connect your googleSheetsOAuth2Api credentials.
⚠️ Common Pitfall: Ensure your sheet includes a websites column, since the downstream crawler expects {{ $json.websites }}.
Step 3: Set Up the Crawl and Data Preparation
Scrape content from each URL, split the results into individual items, and normalize fields for the prompt assembly.
- Add Scrape Pages via Dumpling AI and connect it to Retrieve Sheet Web Addresses.
- Set Method to
POSTand URL tohttps://app.dumplingai.com/api/v1/crawl. - Enable Send Body and set Body Content Type to
JSON. - Set JSON Body to
{ "url": "{{ $json.websites }}", "limit": "5", "depth": "2", "format": "text" }. - Credential Required: Connect your httpHeaderAuth credentials.
- Add Divide Crawl Results and set Field to Split Out to
results. - Add Assign Page Fields and map the fields with expressions:
- Set metadata.title to
{{ $json.metadata.title }}, content to{{ $json.content }}, and metadata.original_url to{{ $json.metadata.original_url }}.
⚠️ Common Pitfall: If the crawler returns empty results, the downstream split node will output no items. Confirm the Dumpling AI API key and URL column values are valid.
Step 4: Set Up the Newsletter Generation (AI)
Aggregate all scraped items into a single prompt and pass it to GPT‑4o to generate the newsletter subject and body.
- Add Assemble Prompt Text and connect it to Assign Page Fields.
- Paste the provided JavaScript Code into Assemble Prompt Text to produce
aggregatedArticles. - Add Create Newsletter with GPT-4o and connect it to Assemble Prompt Text.
- Set Model to
gpt-4o. - Ensure the prompt includes the input expression
{{ $json.aggregatedArticles }}in the message body. - Enable JSON Output so the node returns structured fields.
- Credential Required: Connect your openAiApi credentials.
Step 5: Configure the Email Output
Send the AI-generated newsletter as an email using Gmail.
- Add Dispatch Newsletter Email and connect it to Create Newsletter with GPT-4o.
- Set Subject to
{{ $json.message.content.subject }}. - Set Message to
{{ $json.message.content.body }}. - Fill in To with a valid recipient email address (the field is currently empty).
- Credential Required: Connect your gmailOAuth2 credentials.
⚠️ Common Pitfall: The Gmail node sends HTML in the body. Verify your GPT output contains valid HTML tags as instructed in the prompt.
Step 6: Test and Activate Your Workflow
Run a manual test to verify crawling, AI generation, and email delivery before activating the workflow.
- Click Execute Workflow to run Manual Launch Trigger.
- Confirm Retrieve Sheet Web Addresses outputs rows with a
websitesfield. - Verify Scrape Pages via Dumpling AI returns a
resultsarray and Divide Crawl Results outputs individual items. - Check that Create Newsletter with GPT-4o returns JSON with
subjectandbodyfields. - Confirm Dispatch Newsletter Email sends the email with the expected subject and HTML body.
- When satisfied, toggle the workflow to Active for production use.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n credential connection status and sheet sharing settings 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.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your accounts and API keys are ready.
No. You’ll connect Google, add a Dumpling key, and paste an OpenAI key. The only “techy” part is editing a prompt to match your voice.
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 OpenAI API costs (often just a few cents per issue) plus Dumpling AI usage.
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 a common tweak. Replace the Manual Launch Trigger with a Schedule Trigger, then adjust the “Retrieve Sheet Web Addresses” node to target the correct tab or a date-filtered range. You can also modify the GPT-4o prompt to enforce sections like “Top story,” “Quick hits,” and “Worth a read,” so the output matches your house style every time.
Usually it’s expired Google credentials or the sheet not being shared with the connected Google account. Reconnect the Google Sheets credential in n8n, then re-check the Sheet ID and tab name in the “Retrieve Sheet Web Addresses” node. If you recently changed permissions, give it a minute and retry. Also confirm the URLs are actually in column A, because an empty range looks like “the workflow is broken” when it’s really just no input.
Practically, most people run 5–20 links per issue; beyond that, crawling and summarizing can get slow and the email becomes too long.
Often, yes, because this flow needs batching, content cleanup, and a structured AI prompt before the email goes out. n8n makes that kind of multi-step logic straightforward, and self-hosting avoids per-task pricing when you run it frequently. Zapier or Make can still work if you keep it simple, like “summarize one link and email it.” If you’re building a repeatable newsletter engine with consistent formatting, n8n is usually the calmer choice. Talk to an automation expert if you want help picking the right setup.
Set it up once and your newsletter starts with a draft, not a blank screen. Honestly, that’s the difference between “we should send something” and “it’s already ready.”
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.
