January 22, 2026

Google Sheets to Notion, newsletter drafts ready fast

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

You sit down to “just write the newsletter,” and somehow you’re already 45 minutes deep in copy-pasting, reformatting, and hunting for the latest topic notes.

This hits marketers and newsletter operators first, but founders writing their own updates feel it too. With this Sheets Notion automation, your ideas move from a simple spreadsheet row to a clean Notion draft without the usual busywork.

You’ll see how the workflow turns “Pending” rows into ready-to-edit drafts, keeps a clear queue, and prevents the classic “did we publish this?” confusion.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Sheets to Notion, newsletter drafts ready fast

Click to explore

flowchart LR

    subgraph sg0["When clicking ‘Execute workflow’ Flow"]
        direction LR
        n0@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
        n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
        n2@{ icon: "mdi:database", form: "rounded", label: "Get row(s) in sheet", pos: "b", h: 48 }
        n3@{ icon: "mdi:database", form: "rounded", label: "Update row in sheet", pos: "b", h: 48 }
        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/httprequest.dark.svg' width='40' height='40' /></div><br/>UpdateNotionBlock"]
        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/>Code"]
        n6["<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/notion.dark.svg' width='40' height='40' /></div><br/>Create Page"]
        n7@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
        n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
        n5 --> n4
        n0 --> n6
        n6 --> n5
        n8 --> n0
        n1 -.-> n0
        n4 --> n3
        n2 --> n8
        n3 --> n8
        n7 --> n2
    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 n7 trigger
    class n0 ai
    class n1 aiModel
    class n2,n3,n6 database
    class n4 api
    class n5 code
    classDef customIcon fill:none,stroke:none
    class n4,n5,n6 customIcon

The Problem: Newsletter Drafts Get Stuck in “Almost Done”

Newsletter writing rarely fails because of ideas. It fails in the in-between. Someone has a solid topic in a Google Sheet, the outline lives in a doc, the actual draft is half-built in Notion, and the formatting gets “fixed later” (which means never). Then you lose time doing the same mechanical steps every issue: copy the title, paste the brief, rewrite sections from scratch, create a new Notion page, and try to keep a status column updated. After a few weeks, the process becomes harder to trust than the writing itself. Honestly, that’s the part that drains you.

The friction compounds. Here’s where it breaks down.

Drafts start in a spreadsheet but don’t reliably make it into your writing workspace, so “good ideas” quietly expire.
Formatting and page setup in Notion becomes repetitive, and it steals the time you wanted to spend on the hook and subject line.
Status tracking is fragile, so you end up double-writing, double-checking, or asking someone, “Is this one done?”
When you scale beyond a few drafts a month, the copy-paste workflow creates small errors that turn into big credibility problems.

The Solution: Turn “Pending” Sheet Rows Into Notion Draft Pages

This n8n workflow treats Google Sheets like a lightweight content queue and Notion like your draft library. You click “Execute workflow” in n8n (or schedule it later), and it pulls every row where N8n Status is set to Pending. For each row, an AI writing agent takes two inputs (the Newsletter Title and About the Newsletter) and generates a full, structured draft that matches your preferred style. The workflow then creates a new page in your Notion database and writes the content into the page as real Notion blocks, not a messy pasted wall of text. Once it finishes, it flips that row in Google Sheets from Pending to Done and moves on to the next item.

The run starts with a manual trigger, then Google Sheets becomes the “to-do list.” OpenAI writes the draft, Notion receives a new page plus the full content, and the spreadsheet updates itself so the queue stays clean.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It only pulls Google Sheets rows labeled “Pending,” so you always know what’s next.
It generates a consistent newsletter draft from your title and brief using an AI agent.
It creates a Notion page in your chosen database and fills it with properly chunked blocks.
It updates the original sheet row to “Done” after the Notion draft is written.

Most teams get about 1–2 hours back per issue, because setup and formatting disappear.
Your drafts land in the same Notion database every time, which makes review and reuse simple.
The “Pending → Done” queue reduces missed drafts and accidental duplicates.
You can batch five or ten ideas at once without turning your afternoon into admin work.
Editing becomes the main job again, not draft creation from a blank page.

Example: What This Looks Like

Say you publish two newsletters per week and you manage drafts in a Google Sheet. Manually, creating a Notion page, pasting your title and brief, formatting sections, and updating status is usually about 20 minutes per draft, so around 40 minutes a week before you’ve written a single good paragraph. With this workflow, adding a new idea is about 2 minutes in the sheet, then you run the automation and the draft appears in Notion after a few minutes of AI processing. That’s roughly half an hour back every week, and the bigger win is a queue you can trust.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for the Pending/Done content queue.
Notion to store drafts in a database.
OpenAI API key (get it from your OpenAI dashboard).

Skill level: Intermediate. You’ll connect accounts, paste a few IDs (Sheet and Notion database), and test with two or three sample rows.

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

How It Works

You start the run manually. In n8n, clicking “Execute workflow” kicks things off, which is great when you want control and predictable output while you fine-tune the draft style.

Google Sheets acts as the filter and queue. The workflow reads your chosen tab (often called something like “newsletter”) and pulls only the rows where N8n Status equals Pending, so completed items stay out of the way.

The AI generates the actual newsletter draft. The agent loads your “System Role Instructions” (your rules for sections, tone, and structure), then uses the Newsletter Title and About the Newsletter fields to create a full draft you can edit, polish, and approve.

Notion receives a clean page, with content that fits API limits. The workflow creates the page first, then splits the long draft into smaller chunks and appends them as Notion paragraph blocks via an HTTP request, so the whole thing lands reliably.

You can easily modify the status values (like Pending and Done) to match your team’s naming, or swap the manual trigger for a Cron schedule based on your publishing cadence. 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 trigger so you can test the newsletter drafting flow end-to-end.

Add and position Manual Run Trigger as the entry point.
Connect Manual Run Trigger to Fetch Sheet Records to begin data retrieval.
Keep Flowpast Branding as a visual reference note (optional, no configuration required).

Step 2: Connect Google Sheets

Pull pending newsletter rows and later update their status after drafting is complete.

Open Fetch Sheet Records and select the spreadsheet Document as [YOUR_ID] with the sheet Sheet Name set to newsletter.
Set the filter so Lookup Column is N8n Status and Lookup Value is Pending.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Fetch Sheet Records.
Configure Modify Sheet Row with Operation set to update and map columns to update N8n Status as Done and Newsletter Title as {{ $('Iterate Batch Items').item.json['Newsletter Title'] }}.
Match rows in Modify Sheet Row using Matching Columns set to Newsletter Title.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Modify Sheet Row.

Tip: Ensure your sheet has columns named Newsletter Title, About the Newsletter, and N8n Status to avoid mapping issues.

Step 3: Set Up the AI Drafting Stage

Generate the newsletter draft per row using the AI agent and OpenAI model.

Connect Fetch Sheet Records to Iterate Batch Items so each row is processed individually.
Ensure Iterate Batch Items routes to Newsletter Draft Agent on its second output (the per-item output).
In Newsletter Draft Agent, keep the system prompt in the Text field as provided, including expressions like {{ $json['Newsletter Title'] }} and {{ $json['About the Newsletter'] }}.
Open OpenAI Chat Engine and set Model to gpt-5-mini.
Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine. This node is the language model for Newsletter Draft Agent, so credentials must be added on the parent model node, not the agent.

⚠️ Common Pitfall: If the AI output is empty, verify the Newsletter Title and About the Newsletter fields exist in the incoming row data.

Step 4: Configure Notion Output and Block Patching

Create a Notion page for each draft, transform the AI output into Notion blocks, and patch the blocks into the page.

In Generate Notion Page, set Resource to databasePage and Title to {{ $('Iterate Batch Items').item.json["Newsletter Title"] }}.
Credential Required: Connect your notionApi credentials in Generate Notion Page.
In Transform Blocks Script, keep the JavaScript that chunks the AI output into Notion-safe blocks. The script references the agent output: $('Newsletter Draft Agent').first().json.output.
Open Patch Notion Blocks and set Method to PATCH and URL to https://api.notion.com/v1/blocks/{{ $('Generate Notion Page').item.json.id }}/children.
Enable Send Body and set Body Parameters → children to {{ $json.children }}.
Credential Required: Connect your notionApi credentials in Patch Notion Blocks.

Tip: If Notion block updates fail, confirm that the Notion database ID and integration permissions allow page creation and block edits.

Step 5: Test and Activate Your Workflow

Validate the flow end-to-end before enabling it for production use.

Click Execute Workflow to run Manual Run Trigger and process a pending row.
Confirm that Generate Notion Page creates a new page with the title matching {{ $('Iterate Batch Items').item.json["Newsletter Title"] }}.
Verify Patch Notion Blocks adds the draft content blocks and Modify Sheet Row updates N8n Status to Done.
Once the test succeeds, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Google Sheets credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and confirm the connected Google account still has access to the spreadsheet.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Notion integrations must be explicitly shared to the target database (Share → Invite the integration). If page creation works but block updates fail, your database access is usually the culprit.

Frequently Asked Questions

How long does it take to set up this Sheets Notion automation?

About 30 minutes if your Sheet and Notion database are ready.

Do I need coding skills to automate Sheets to Notion newsletter drafts?

No. You’ll mostly connect accounts and paste in a few IDs (your spreadsheet and Notion database).

Is n8n free to use for this Sheets Notion 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 OpenAI API costs, which are usually a few cents per draft depending on length and model.

Where can I host n8n to run this 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 Sheets Notion automation workflow for a different newsletter format?

Yes, and you should. The quickest win is editing the AI Agent “System Role Instructions” so it writes in your voice and uses your exact sections. You can also change which Google Sheets columns get passed into the OpenAI Chat Model (for example, add “Audience,” “Links,” or “CTA”). If your Notion database has custom properties, adjust the Notion “Create Page” mapping so every draft is tagged correctly.

Why is my Notion connection failing in this workflow?

Usually the integration was never shared to the database you’re writing into, or the Database ID is wrong. Re-check Notion’s Share settings, then confirm the database ID in n8n matches the destination. If page creation works but content doesn’t append, the HTTP Request node may be pointing at the wrong block/page ID.

How many rows can this Sheets Notion automation handle?

On n8n Cloud Starter, you can comfortably run batches of dozens of drafts at a time, and bigger plans handle more volume. If you self-host, there’s no hard execution cap (it mostly depends on your server and OpenAI rate limits). Because the workflow processes items one-by-one with Split in Batches, it stays stable even when your sheet grows.

Is this Sheets Notion automation better than using Zapier or Make?

Often, yes, because this flow isn’t just “move text from A to B.” You’re generating long content, chunking it to satisfy Notion’s API limits, then appending blocks with an HTTP request, which is the kind of logic that gets awkward (and pricey) in simpler tools. n8n also makes looping through rows and updating statuses straightforward, so your queue stays honest. Zapier or Make can still work if you only need a tiny two-step draft creator and you’re fine with less control. If you want help choosing, Talk to an automation expert.

Once this is running, your spreadsheet becomes a calm, reliable queue and Notion becomes the single place drafts land. Set it up once, then get back to publishing.

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.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "9aa6d2a93ebf6f21a91647d7d5f2ea449035c404ebf1c4fe4614bcb5a083e787"
},
"name": "Automated Newsletter Drafting Flow",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-7848",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 960,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "62e67b86-a0f0-4933-9bbc-f02c159975b2",
"name": "Manual Run Trigger",
"type": "n8n-nodes-base.manualTrigger",
"position": [
0,
125
],
"parameters": [],
"typeVersion": 1
},
{
"id": "089d9188-2ad9-4eed-a29d-4072b0c5c35b",
"name": "Fetch Sheet Records",
"type": "n8n-nodes-base.googleSheets",
"position": [
260,
145
],
"parameters": {
"options": [],
"filtersUI": {
"values": [
{
"lookupValue": "Pending",
"lookupColumn": "N8n Status"
}
]
},
"sheetName": {
"__rl": true,
"mode": "list",
"value": 1587951649,
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]",
"cachedResultName": "newsletter"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]",
"cachedResultName": "Newsletter Automation"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.6
},
{
"id": "25b33ac0-44b4-493e-8b3b-4591d67bf100",
"name": "Iterate Batch Items",
"type": "n8n-nodes-base.splitInBatches",
"position": [
540,
120
],
"parameters": {
"options": []
},
"executeOnce": true,
"typeVersion": 3
},
{
"id": "6828ddf2-9504-4944-892a-adf294822ec6",
"name": "Newsletter Draft Agent",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
860,
155
],
"parameters": {
"text": "=## System Role Instructions\n\nYou are an expert newsletter writer tasked with creating engaging, professional, and story-driven newsletters for our audience. Your job is to take the given **title** and **about text** and turn them into a polished newsletter draft.\n\nFollow these detailed rules and guidelines:\n\n---\n\n### \u270d\ufe0f Writing Style & Voice\n\n* Inspired by **Ali Abdaal\u2019s newsletters**: warm, friendly, conversational, yet structured and reflective.  \n* The email should feel like it\u2019s written to a friend, while still delivering value and insight.  \n* Use **plain English**. No jargon unless explained simply.  \n* Flow naturally from **story \u2192 reflection \u2192 takeaway**.  \n* Keep a **narrative feel** \u2014 avoid heavy subheadings or too many bullet points.  \n* Use paragraphs as the main building blocks (with the occasional list if absolutely needed).  \n* Balance personal anecdotes with **clear, useful lessons**.  \n\n---\n\n### \ud83c\udfd7\ufe0f Structure to Follow\n\n1. **Subject Line**  \n   * Must be curiosity-driven (can include 1 emoji).  \n   * Example: \u201c\u26a1 The One Decision That Changed Everything.\u201d  \n\n2. **Hero Caption**  \n   * Short supporting line that adds intrigue or context.  \n\n3. **Opening Hook**  \n   * Friendly, personal update or anecdote that draws the reader in.  \n\n4. **Main Story / Insights**  \n   * Expand on `{{ $json['About the Newsletter'] }}`.  \n   * Present it as a flowing story with reflections woven in.  \n   * Prefer paragraphs (80%) over lists (20%).  \n\n5. **Reactions / Internet Pulse (optional)**  \n   * If relevant, mention how people reacted online or in your circle.  \n\n6. **Personal Reflection / Lesson**  \n   * Add your own viewpoint.  \n   * End with a **clear, memorable takeaway**.  \n\n7. **Optional Plug / CTA Section**  \n   * Natural and conversational \u2014 like recommending something to a friend.  \n   * Never salesy.  \n\n8. **Closing**  \n   * Warm sign-off, often with a reflective or open-ended question.  \n\n---\n\n### \ud83d\udccc Content Guidelines\n\n* Keep paragraphs short (2\u20134 sentences for readability).  \n* Use bold only for **emphasis**.  \n* \u274c No emojis in the body text (only in subject line).  \n* \u274c Avoid filler, robotic tone, or clickbait.  \n* \u2705 Must always sound **human, authentic, and thoughtful**.  \n\n---\n\n### \ud83d\ude80 Output Format\n\nGenerate the newsletter draft with these sections in order:\n\n1. **Subject Line**  \n2. **Hero Caption**  \n3. **Body**  \n   * Hook  \n   * Story/Insights (based on `{{ $json['About the Newsletter'] }}`)  \n   * Reflection/lesson  \n   * Optional plug  \n   * Closing  \n\n---\n\n## User Prompt\n\nGenerate a newsletter using the following inputs:\n\n* **Newsletter Title**: `{{ $json['Newsletter Title'] }}`  \n* **About the Newsletter**: `{{ $json['About the Newsletter'] }}`  \n\n---\n\n## Assistant Task\n\nTake the above inputs and produce a **complete, story-driven newsletter draft** following the system role instructions.\n\n\ud83d\udc49 Each time you pass a new `{{ $json['Newsletter Title'] }}` and `{{ $json['About the Newsletter'] }}`, the assistant will output a full, narrative-style newsletter in this exact tone and structure.",
"options": {
"systemMessage": "=You are an expert newsletter writer tasked with creating engaging, professional, and **story-driven** newsletters for our audience.  \nYour job is to take the **topics provided by the user** and turn them into polished newsletters that follow these rules and guidelines.\n\n---\n\n## \u270d\ufe0f Writing Style & Voice\n\n* Inspired by **Ali Abdaal\u2019s LifeNotes style** \u2014 warm, reflective, conversational.  \n* Feels like an **email to a friend** rather than a blog article.  \n* Prioritize paragraphs and flow \u2014 avoid overuse of bullet points or subheadings.  \n* Use **short, varied sentences** to create rhythm.  \n* Inject personal reflections, small anecdotes, and lessons.  \n* Always **balance storytelling with useful takeaways**.  \n\n---\n\n## \ud83c\udfd7\ufe0f Structure\n\n1. **Subject Line**  \n   * Curiosity-driven, can include one emoji.  \n\n2. **Hero Caption**  \n   * Short, intriguing supporting line.  \n\n3. **Opening Hook**  \n   * A friendly anecdote or casual update that sets the tone.  \n\n4. **Main Story**  \n   * Narrative expansion of the newsletter topic.  \n   * Keep flow conversational \u2014 no rigid sectioning.  \n   * Prefer **paragraph storytelling** (80%) with light use of lists (20%).  \n\n5. **Reflection / Lesson**  \n   * Share your key insight and leave the reader with a clear takeaway.  \n\n6. **Optional Plug**  \n   * Smoothly integrate recommendations, resources, or links.  \n   * Must feel natural, never sales-pitchy.  \n\n7. **Closing**  \n   * Warm sign-off with an optional reflective question to invite replies.  \n\n---\n\n## \ud83d\udccc Content Guidelines\n\n1. **Language & Tone**  \n   * Conversational, professional, but never stiff.  \n   * No jargon unless explained.  \n   * No fluff, filler, or robotic tone.  \n\n2. **Formatting**  \n   * Short paragraphs (2\u20134 sentences).  \n   * Bold sparingly for emphasis.  \n   * Minimal lists; narrative should dominate.  \n\n3. **Do\u2019s**  \n   * Keep curiosity alive.  \n   * Share stories + reflections.  \n   * Provide **actionable or thoughtful takeaways**.  \n\n4. **Don\u2019ts**  \n   * \u274c No emojis in body (only in subject line).  \n   * \u274c No clickbait or over-promises.  \n   * \u274c No generic motivational filler.  \n\n---\n\n## \ud83d\ude80 Output Expectations\n\n* Always generate a **complete newsletter draft** (subject line \u2192 closing).  \n* Must feel **human, authentic, and narrative-driven**.  \n* No heavy subheadings or over-structured blog style.  \n\n\u2705 For each new `{{ $json['Newsletter Title']}}` and `{{ $json['About the Newsletter'] }}`, output a **storytelling-style newsletter** in this format.\n"
},
"promptType": "define",
"hasOutputParser": true
},
"retryOnFail": false,
"typeVersion": 2.1
},
{
"id": "5be862bd-44bf-4ffb-a196-cf44d5b7c274",
"name": "Generate Notion Page",
"type": "n8n-nodes-base.notion",
"position": [
860,
345
],
"parameters": {
"title": "={{ $('Iterate Batch Items').item.json[\"Newsletter Title\"] }}",
"options": [],
"resource": "databasePage",
"databaseId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://www.notion.so/[YOUR_ID]",
"cachedResultName": "Newsletter Automation"
}
},
"credentials": {
"notionApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.2
},
{
"id": "eec35fc8-d211-44b2-8329-1d799f3de22e",
"name": "Transform Blocks Script",
"type": "n8n-nodes-base.code",
"position": [
540,
365
],
"parameters": {
"jsCode": "const src = JSON.stringify($('Newsletter Draft Agent').first().json.output);\nconst size = 1800; // safe chunk size for Notion text\nconst blocks = [];\nfor (let i = 0; i < src.length; i += size) {\n  blocks.push({\n    type: 'paragraph',\n    paragraph: {\n      // language: 'json',\n      rich_text: [{ type: 'text', text: { content: src.slice(i, i + size) } }]\n    }\n  });\n}\nreturn [{ children: blocks, title: \"AML JSON\" }];\n"
},
"typeVersion": 2
},
{
"id": "28dafa8b-a70a-4444-95f1-3abbf9ad0e92",
"name": "Patch Notion Blocks",
"type": "n8n-nodes-base.httpRequest",
"onError": "continueRegularOutput",
"position": [
260,
335
],
"parameters": {
"url": "=https://api.notion.com/v1/blocks/{{ $('Generate Notion Page').item.json.id }}/children",
"method": "PATCH",
"options": [],
"sendBody": true,
"authentication": "predefinedCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "children",
"value": "={{ $json.children }}"
}
]
},
"nodeCredentialType": "notionApi"
},
"credentials": {
"notionApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.2
},
{
"id": "a0ac31b3-3ca6-452f-8dbe-a97fa10bfea2",
"name": "Modify Sheet Row",
"type": "n8n-nodes-base.googleSheets",
"position": [
0,
525
],
"parameters": {
"columns": {
"value": {
"N8n Status": "Done",
"Newsletter Title": "={{ $('Iterate Batch Items').item.json['Newsletter Title'] }}"
},
"schema": [
{
"id": "id",
"type": "string",
"display": true,
"removed": true,
"required": false,
"displayName": "id",
"defaultMatch": true,
"canBeUsedToMatch": true
},
{
"id": "Newsletter Title",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "Newsletter Title",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "About the Newsletter",
"type": "string",
"display": true,
"removed": true,
"required": false,
"displayName": "About the Newsletter",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "N8n Status",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "N8n Status",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Manual Status",
"type": "string",
"display": true,
"removed": true,
"required": false,
"displayName": "Manual Status",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "row_number",
"type": "number",
"display": true,
"removed": true,
"readOnly": true,
"required": false,
"displayName": "row_number",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [
"Newsletter Title"
],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "update",
"sheetName": {
"__rl": true,
"mode": "list",
"value": 1587951649,
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]",
"cachedResultName": "newsletter"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/[YOUR_ID]",
"cachedResultName": "Newsletter Automation"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.6
},
{
"id": "d8f83230-6d9b-4c25-bf45-5e1914dd7b50",
"name": "OpenAI Chat Engine",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
860,
525
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-5-mini",
"cachedResultName": "gpt-5-mini"
},
"options": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Transform Blocks Script": {
"main": [
[
{
"node": "Patch Notion Blocks",
"type": "main",
"index": 0
}
]
]
},
"Newsletter Draft Agent": {
"main": [
[
{
"node": "Generate Notion Page",
"type": "main",
"index": 0
}
]
]
},
"Generate Notion Page": {
"main": [
[
{
"node": "Transform Blocks Script",
"type": "main",
"index": 0
}
]
]
},
"Iterate Batch Items": {
"main": [
[],
[
{
"node": "Newsletter Draft Agent",
"type": "main",
"index": 0
}
]
]
},
"OpenAI Chat Engine": {
"ai_languageModel": [
[
{
"node": "Newsletter Draft Agent",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Patch Notion Blocks": {
"main": [
[
{
"node": "Modify Sheet Row",
"type": "main",
"index": 0
}
]
]
},
"Fetch Sheet Records": {
"main": [
[
{
"node": "Iterate Batch Items",
"type": "main",
"index": 0
}
]
]
},
"Modify Sheet Row": {
"main": [
[
{
"node": "Iterate Batch Items",
"type": "main",
"index": 0
}
]
]
},
"Manual Run Trigger": {
"main": [
[
{
"node": "Fetch Sheet Records",
"type": "main",
"index": 0
}
]
]
}
}
}