January 22, 2026

Google Sheets to Gmail, drafts ready for approval

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your content process probably isn’t “hard.” It’s just annoyingly manual. Ideas live in a spreadsheet, drafts live in random docs, and approvals happen in messy email threads that you have to babysit.

This Sheets Gmail drafts automation hits marketing leads first, but founders and consultants feel it too. You will ship more consistently without repeating topics or rewriting “the same post” for the tenth time.

Below is the exact workflow logic: how it pulls your Google Sheets history, generates a structured draft through a multi-agent AI pipeline, and sends a clean Gmail draft for approval (with a built-in timeout and failure alerts).

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Sheets to Gmail, drafts ready for approval

Click to explore

flowchart LR

    subgraph sg0["Weekly Post Flow"]
        direction LR
        n0@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
        n1@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser1", pos: "b", h: 48 }
        n2@{ icon: "mdi:play-circle", form: "rounded", label: "Weekly Post Trigger", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "Structure & Logic Designer", pos: "b", h: 48 }
        n4@{ icon: "mdi:robot", form: "rounded", label: "Draft Copywriter", pos: "b", h: 48 }
        n5@{ icon: "mdi:message-outline", form: "rounded", label: "Human Approval (Gmail)", pos: "b", h: 48 }
        n6@{ icon: "mdi:database", form: "rounded", label: "Log Published Content", pos: "b", h: 48 }
        n7@{ icon: "mdi:database", form: "rounded", label: "Retrieve Post History & Ideas", pos: "b", h: 48 }
        n8@{ icon: "mdi:robot", form: "rounded", label: "Deduplication & Topic Selector", pos: "b", h: 48 }
        n9@{ icon: "mdi:robot", form: "rounded", label: "Style & Compliance Editor", pos: "b", h: 48 }
        n10@{ icon: "mdi:brain", form: "rounded", label: "Brain: Topic Analyst (GPT-4o..", pos: "b", h: 48 }
        n11@{ icon: "mdi:brain", form: "rounded", label: "Brain: Content Architect (GP..", pos: "b", h: 48 }
        n12@{ icon: "mdi:brain", form: "rounded", label: "Brain: Creative Writer (GPT-..", pos: "b", h: 48 }
        n13@{ icon: "mdi:brain", form: "rounded", label: "Brain: Formatting Police (GP..", pos: "b", h: 48 }
        n14@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
        n17@{ icon: "mdi:cog", form: "rounded", label: "Wait Timed Out (48h)", pos: "b", h: 48 }
        n14 --> n8
        n4 --> n9
        n2 --> n7
        n5 --> n6
        n5 --> n17
        n0 -.-> n8
        n1 -.-> n3
        n9 --> n5
        n3 --> n4
        n7 --> n14
        n8 --> n3
        n12 -.-> n4
        n11 -.-> n3
        n13 -.-> n9
        n10 -.-> n8
    end

    subgraph sg1["Error Flow"]
        direction LR
        n15@{ icon: "mdi:play-circle", form: "rounded", label: "Error Trigger", pos: "b", h: 48 }
        n16@{ icon: "mdi:message-outline", form: "rounded", label: "Send a message", pos: "b", h: 48 }
        n15 --> n16
    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 n2,n15 trigger
    class n0,n1,n3,n4,n8,n9 ai
    class n10,n11,n12,n13 aiModel
    class n6,n7 database

The Problem: Drafting technical posts becomes a repeatable slog

Publishing “technical authority” content sounds simple until you try to do it weekly. You spend time scanning past posts so you don’t repeat yourself, then you outline, then you write, then you rewrite because the tone feels too AI-ish. After that, approvals get stuck in email limbo, and your posting cadence quietly dies. The worst part is the context switching. You are doing creative work, admin work, and quality control all in the same sitting, which is honestly exhausting.

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

You re-pitch topics you already covered because there’s no reliable “memory” across weeks.
Drafts come out generic, so you lose another hour forcing a real voice back into the copy.
Approvals are scattered across threads, which means “waiting” becomes your default workflow.
When an automation fails, you notice days later, not minutes later.

The Solution: Google Sheets history + multi-agent drafting + Gmail approval

This workflow turns your Google Sheet into a lightweight content brain, then uses a structured AI pipeline to produce drafts that sound intentional, not robotic. It starts on a schedule, pulls your posting history from Google Sheets, and aggregates the records so the system can see what you have already said. From there, an AI “topic selector” avoids duplicates and picks a fresh angle based on your past topics, status, and difficulty. Next, a blueprint agent creates the logical structure (what to cover, in what order), and a separate drafting agent writes the post. Finally, a brand compliance editor cleans up tone and formatting, and the finished draft is sent to Gmail for human review and image pairing before you publish.

The workflow begins with a Scheduled Post Trigger. Google Sheets provides persistent memory and publishing state. Gmail becomes the approval gate, with a 48-hour timeout marker so the system does not hang forever if nobody reviews it.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

It scans your Google Sheets post history on a schedule and collects the rows into usable context.
It uses an AI topic de-duplication step to avoid repeating topics you already posted.
It splits outlining from writing, so the draft follows a clear technical structure.
It sends a Gmail review message and logs the “published” result back into Google Sheets after approval.

Most teams get about 2–4 hours back per week by removing research, outlining, and first-draft busywork.
You stop repeating yourself because the sheet acts like persistent topic memory.
Draft quality is steadier, since a compliance editor enforces your rules before you ever see it.
Approvals become a single, predictable checkpoint instead of a thread you chase.
Failures are easier to catch quickly thanks to a dedicated error trigger and alert email.

Example: What This Looks Like

Say you publish 3 technical posts per week. Manually, it’s common to spend about 45 minutes reviewing past topics, another hour outlining, and roughly 90 minutes writing and polishing, so you’re at around 3–4 hours per post. With this workflow, you update a Google Sheet once and let the scheduled run generate a draft automatically, then you spend about 15–20 minutes reviewing the Gmail draft and pairing an image. That’s roughly 2–3 hours back per post, without lowering the bar.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for topic memory and publishing log.
Gmail to route drafts into a human approval gate.
OpenAI API key (or Gemini) (get it from your provider’s developer console)

Skill level: Intermediate. You’ll connect credentials, update a Sheet ID and recipient email, and adjust a few prompts safely.

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

How It Works

A scheduled trigger kicks things off. The workflow runs on your chosen cadence (daily, weekly, whatever fits) so drafting becomes routine instead of “when I find time.”

Google Sheets provides memory. It fetches your post history and aggregates the records, so the AI steps can see your previous topics, statuses, and any tracking fields you keep.

Multiple AI roles do focused work. One agent selects a non-repetitive topic, another builds the logical blueprint, another writes the draft, and a final editor enforces brand rules like formatting and removing fluff.

Gmail becomes the approval gate. You get a clean draft in your inbox for final review and manual image pairing, and the workflow records the outcome back to Google Sheets. There’s also a 48-hour timeout marker so unattended reviews don’t tie up the run.

You can easily modify the topic rules to match your content pillars based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set the weekly schedule that kicks off the LinkedIn content pipeline.

Add and open Scheduled Post Trigger.
Set the schedule rule to weekly with Day set to 1, Hour to 10, and Minute to 15.
Confirm the trigger connects to Fetch Post History as the next node.

Step 2: Connect Google Sheets

Pull historical topics and log the finalized post back into your sheet.

Open Fetch Post History and set Document ID to REPLACE_WITH_YOUR_SHEET_ID and Sheet Name to REPLACE_WITH_YOUR_SHEET_ID.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Fetch Post History.
Open Record Published Entry, keep Operation set to append, and set Document ID and Sheet Name to REPLACE_WITH_YOUR_SHEET_ID.
Verify column mappings in Record Published Entry, including Date as {{ $now.toFormat("dd-MM-yyyy") }} and Topic as {{ $items("Topic De-dup Selector")[0].json.output.selected_topic.topic }}.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Record Published Entry.

Tip: Ensure your Google Sheet has columns that match Topic, Content, Date, Status, and Difficulty to avoid append errors.

Step 3: Set Up AI Topic Selection and Blueprinting

Use AI to pick a fresh topic and generate a teaching blueprint.

Open Collect Records and keep Aggregate set to aggregateAllItemData to bundle history for AI analysis.
Open Topic De-dup Selector and verify the prompt includes the JSON history mapping and selection instructions.
Confirm Parsed Output Mapper is connected to Topic De-dup Selector as the output parser and its schema matches the defined JSON example.
Open Blueprint Logic Composer and confirm the prompt uses the selected topic fields: {{ $json.output.selected_topic.topic }}, {{ $json.output.selected_topic.difficulty }}, and {{ $json.output.selected_topic.reason }}.
Ensure Structured Result Mapper is connected as the output parser for Blueprint Logic Composer with the provided schema.
Credential Required: Connect your openAiApi credentials in AI Topic Analyst Mini and confirm it is linked as the language model for Topic De-dup Selector.
Credential Required: Connect your openAiApi credentials in AI Content Architect and confirm it is linked as the language model for Blueprint Logic Composer.

⚠️ Common Pitfall: The output parsers (Parsed Output Mapper and Structured Result Mapper) do not hold credentials. Add OpenAI credentials to the parent model nodes instead.

Step 4: Configure Drafting, Formatting, and Review

Create the draft, enforce branding, and route it through Gmail approval.

Open Post Draft Generator and confirm the prompt includes the structured fields like {{ $json.output.problem }} and {{ $json.output.result }}.
Credential Required: Connect your openAiApi credentials in AI Creative Writer and confirm it is linked as the language model for Post Draft Generator.
Open Branding Compliance Editor and keep the branding rules in the system message intact.
Credential Required: Connect your openAiApi credentials in AI Format Guardian and confirm it is linked as the language model for Branding Compliance Editor.
Open Gmail Review Gate, set Send To to [YOUR_EMAIL], and verify Operation is sendAndWait.
Set the Subject to Ready for LinkedIn: {{ $('Topic De-dup Selector').item.json.output.selected_topic.topic }} and Message to <strong>Ready for LinkedIn: {{ $('Topic De-dup Selector').item.json.output.selected_topic.topic }}</strong> {{ $json.output }}.
Credential Required: Connect your gmailOAuth2 credentials in Gmail Review Gate.
Gmail Review Gate outputs to both Record Published Entry and Timeout Marker 48h in parallel.

Tip: The 48-hour wait window is controlled by the approval limit in Gmail Review Gate; Timeout Marker 48h is a no-op marker for visibility.

Step 5: Add Error Handling

Send a notification email if any node fails during execution.

Confirm Failure Trigger is connected to Send Alert Email.
Open Send Alert Email and set Send To to [YOUR_EMAIL].
Set the Subject to ⚠️ Workflow Error: LinkedIn Content Engine.
Set the Message to The LinkedIn engine failed at node: {{ $node["Failure Trigger"].json["node"]["name"] }}. Reason: {{ $node["Failure Trigger"].json["execution"]["error"]["message"] }}.
Credential Required: Connect your gmailOAuth2 credentials in Send Alert Email.

Step 6: Test and Activate Your Workflow

Validate the workflow end-to-end and turn on the weekly schedule.

Use Execute Workflow to run a manual test from Scheduled Post Trigger.
Verify data flows through Fetch Post History → Collect Records → Topic De-dup Selector → Blueprint Logic Composer → Post Draft Generator → Branding Compliance Editor.
Approve the email from Gmail Review Gate and confirm the row is appended by Record Published Entry.
If an error occurs, confirm Send Alert Email receives the failure details from Failure Trigger.
When satisfied, switch the workflow to Active to enable the weekly automation.

🔒

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 credential test and confirm the sheet is shared with the connected Google account 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

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

About 30–60 minutes if your accounts are already connected.

Do I need coding skills to automate Sheets Gmail drafts?

No. You’ll mostly connect accounts and replace a few IDs inside the workflow.

Is n8n free to use for this Sheets Gmail drafts 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 (or Gemini) API costs, which are usually a few cents per draft depending on length.

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 Gmail drafts workflow for LinkedIn versus newsletter drafts?

Yes, and it’s one of the best uses of this setup. You typically keep the Google Sheets “memory” and Gmail approval gate the same, then swap the writing rules in the Post Draft Generator and Branding Compliance Editor prompts to match each channel. Common customizations include different post length, different CTA style, and separate topic pools by adding a “Channel” column in your sheet. If you want stricter formatting, adjust the AI Format Guardian instructions so it enforces your exact structure every time.

Why is my Google Sheets connection failing in this workflow?

Usually it’s expired Google credentials or the sheet isn’t shared with the connected account. Reconnect the Google Sheets credential in n8n, then re-check the Sheet ID in the Fetch Post History and Record Published Entry steps. It can also fail if columns were renamed (for example, “Status” changed), because the agents rely on consistent fields. If failures happen only sometimes, check for Google API rate limiting when you run lots of rows at once.

How many drafts can this Sheets Gmail drafts automation handle?

On n8n Cloud Starter you’re typically fine for a small team running daily drafts, and higher tiers cover larger volumes. If you self-host, there’s no execution limit; it mostly depends on your server and your AI provider rate limits. Practically, this workflow handles one draft run smoothly in a few minutes, and you can queue more by scheduling runs or triggering multiple topics in batches. If your sheet has thousands of rows, consider filtering to “recent posts” so the history scan stays fast.

Is this Sheets Gmail drafts automation better than using Zapier or Make?

Often, yes. This workflow isn’t just “send a prompt and paste the result.” It uses multiple AI steps, persistent history, branching, and a human approval gate with error handling, which is easier to model in n8n without hitting pricing walls. Zapier or Make can work, but multi-step AI chains get expensive and harder to debug. If you only need a basic two-step draft generator, the simpler tools are fine. If you want help choosing, Talk to an automation expert.

You set this up once, and your drafting process stops depending on willpower. The workflow handles the repeatable parts so you can spend your time on the final call, not the first draft.

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.

{
"meta": {
"instanceId": "a9bafe21cba071d8d44dc0104808378b9045649062f1f875b007e012402d97c8",
"templateCredsSetupCompleted": null,
"templateId": null
},
"nodes": [
{
"id": "flowpast-topbar-12184",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1145,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "a6297e94-2aa2-4fb6-be81-c12d31fbac78",
"name": "Parsed Output Mapper",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
975,
155
],
"parameters": {
"jsonSchemaExample": "{\n  \"candidates\": [\n    {\n      \"topic\": \"\",\n      \"difficulty\": \"\",\n      \"why\": \"\"\n    }\n  ],\n  \"selected_topic\": {\n    \"topic\": \"\",\n    \"difficulty\": \"\",\n    \"reason\": \"\"\n  }\n}"
},
"typeVersion": 1.3
},
{
"id": "fc5fca93-031b-429d-9bee-71a37b2ac73b",
"name": "Structured Result Mapper",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
1045,
310
],
"parameters": {
"jsonSchemaExample": "{\n  \"problem\": \"\",\n  \"when_it_matters\": \"\",\n  \"core_idea\": \"\",\n  \"practical_approach\": [\n    \"\",\n    \"\",\n    \"\"\n  ],\n  \"common_mistake\": \"\",\n  \"result\": \"\"\n}"
},
"typeVersion": 1.3
},
{
"id": "47e8a5ed-57e1-4459-8e2e-f141d02f6ba6",
"name": "Scheduled Post Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
0,
210
],
"parameters": {
"rule": {
"interval": [
{
"field": "weeks",
"triggerAtDay": [
1
],
"triggerAtHour": 10,
"triggerAtMinute": 15
}
]
}
},
"typeVersion": 1.3
},
{
"id": "ed53ea93-89f3-4366-b7ed-f535e486e1d2",
"name": "Blueprint Logic Composer",
"type": "@n8n/n8n-nodes-langchain.agent",
"notes": "",
"position": [
735,
460
],
"parameters": {
"text": "=Topic: > {{ $json.output.selected_topic.topic }}\n\nTechnical Difficulty: > {{ $json.output.selected_topic.difficulty }}\n\nContext & Value: > {{ $json.output.selected_topic.reason }}\n\nInstruction: Generate the Structure Blueprint using the sections defined in your System Message. Ensure the depth matches the \"{{ $json.output.selected_topic.difficulty }}\" level.",
"options": {
"systemMessage": "Role: You are a Senior n8n Solutions Architect and Educator.\n\nTask: Create a technical \"Teaching Blueprint\" for a high-authority LinkedIn post based on the provided topic. You do NOT write the final copy; you define the logical skeleton that ensures the reader learns how to architect a solution, not just click buttons.\n\nRules:\n1. Focus on \"The Why\": Explain the logic behind the solution, not just the steps.\n2. Technical Depth: Identify 1-2 \"Advanced Nodes\" or features essential for this workflow (e.g., Error Trigger, Code Node, Merge [Wait for All], or Wait nodes for rate-limiting).\n3. Production-Ready Advice: Include a \"Resiliency Tip\" in the Common Mistake section (e.g., handling timeouts or schema drift).\n4. Expert Tone: Avoid marketing fluff (\"unlock,\" \"revolutionary\"). Use engineering terms: \"idempotency,\" \"scalability,\" \"state management,\" and \"error handling.\"\n5. Formatting: Write in Sentence Case. Only capitalize the first letter of sentences and proper nouns (n8n, API names).\n\nStructure Requirements: \n\u2022 The Problem: The specific pain point or technical bottleneck. \n\u2022 Real-World Context: When this specific architecture is mandatory (e.g., high-volume production). \n\u2022 Core Concept: The \"Mental Model\" the reader needs to understand the solution. \n\u2022 Architectural Approach: 3-4 high-level engineering steps. Mention the \"Advanced Nodes\" here. \n\u2022 The \"Silent Killer\": A common mistake that breaks this workflow in production. \n\u2022 The Result: The business or technical outcome of a resilient build."
},
"promptType": "define",
"hasOutputParser": true
},
"notesInFlow": true,
"typeVersion": 3
},
{
"id": "7b4b261f-a514-431a-8b78-9de33b507471",
"name": "Post Draft Generator",
"type": "@n8n/n8n-nodes-langchain.agent",
"notes": "",
"position": [
510,
405
],
"parameters": {
"text": "=Write a LinkedIn post using the following raw data. Follow the structure strictly:\n\nProblem: \n{{ $json.output.problem }}\n\nWhen it matters: \n{{ $json.output.when_it_matters }}\n\nCore idea: \n{{ $json.output.core_idea }}\n\nPractical approach: \n{{ Array.isArray($json.output.architectural_approach) ? $json.output.architectural_approach.join(\"\\n- \") : $json.output.architectural_approach }}\n\nCommon mistake: \n{{ $json.output.silent_killer }}\n\nResult: \n{{ $json.output.result }}\n\nFinal Instruction: End the post with a light open question CTA",
"options": {
"systemMessage": "You are a world-class n8n Automation Expert and LinkedIn Content Creator. Your goal is to turn technical data into high-engagement \"authority\" posts.\n\nSTRICT WRITING RULES:\n1. NO INTROS: Do not start with \"Here is your post\" or \"Sure thing.\" Start immediately with the Hook.\n2. HOOK: Create a punchy, 1-line opening that highlights a pain point or a controversial opinion about automation.\n3. SCANNABILITY: Use frequent line breaks. No paragraph should be longer than 2 sentences.\n4. TONE: Direct, professional, and helpful. Use \"Ambassador\" language: talk about \"production-ready,\" \"scalability,\" and \"resilient workflows.\"\n5. FORMATTING: Use bullet points (\u2022) for lists. Ensure there is a blank line between every section.\n6. NO EMOJI OVERLOAD: Use max 2-3 emojis in the entire post.\n7. When mentioning the Practical Approach, explicitly name the n8n nodes involved (e.g., 'Use the Webhook Node to...')."
},
"promptType": "define"
},
"notesInFlow": true,
"typeVersion": 3
},
{
"id": "f65da286-cea7-4721-8969-e9d3a49199de",
"name": "Gmail Review Gate",
"type": "n8n-nodes-base.gmail",
"onError": "continueErrorOutput",
"position": [
5,
465
],
"webhookId": "59142591-0c38-4c76-8ebd-b668fde07758",
"parameters": {
"sendTo": "[YOUR_EMAIL]",
"message": "=<strong>Ready for LinkedIn: {{ $('Topic De-dup Selector').item.json.output.selected_topic.topic }}</strong>\n\n{{ $json.output }}",
"options": {
"limitWaitTime": {
"values": {
"resumeAmount": 48
}
},
"appendAttribution": false
},
"subject": "=Ready for LinkedIn: {{ $('Topic De-dup Selector').item.json.output.selected_topic.topic }}",
"operation": "sendAndWait",
"approvalOptions": {
"values": {
"approvalType": "double"
}
}
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.2
},
{
"id": "6aa4c206-cc5a-4577-8f7b-78e87203012c",
"name": "Record Published Entry",
"type": "n8n-nodes-base.googleSheets",
"position": [
250,
580
],
"parameters": {
"columns": {
"value": {
"Date": "={{ $now.toFormat(\"dd-MM-yyyy\") }}",
"Topic": "={{ $items(\"Topic De-dup Selector\")[0].json.output.selected_topic.topic }}",
"Status": "Drafted",
"Content": "={{ $('Branding Compliance Editor').item.json.output }}",
"Difficulty": "={{ $items(\"Topic De-dup Selector\")[0].json.output.selected_topic.difficulty }}"
},
"schema": [
{
"id": "Topic",
"type": "string",
"display": true,
"required": false,
"displayName": "Topic",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Content",
"type": "string",
"display": true,
"required": false,
"displayName": "Content",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Date",
"type": "string",
"display": true,
"required": false,
"displayName": "Date",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "LinkedIn URL",
"type": "string",
"display": true,
"removed": true,
"required": false,
"displayName": "LinkedIn URL",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Status",
"type": "string",
"display": true,
"required": false,
"displayName": "Status",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Difficulty",
"type": "string",
"display": true,
"required": false,
"displayName": "Difficulty",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "REPLACE_WITH_YOUR_SHEET_ID"
},
"documentId": {
"__rl": true,
"mode": "id",
"value": "REPLACE_WITH_YOUR_SHEET_ID"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.7
},
{
"id": "cd4d2853-cee3-4b4b-8bec-1366b22058bc",
"name": "Fetch Post History",
"type": "n8n-nodes-base.googleSheets",
"position": [
270,
240
],
"parameters": {
"options": [],
"sheetName": {
"__rl": true,
"mode": "list",
"value": "REPLACE_WITH_YOUR_SHEET_ID"
},
"documentId": {
"__rl": true,
"mode": "id",
"value": "REPLACE_WITH_YOUR_SHEET_ID"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.7
},
{
"id": "fb548d41-52c5-4565-9098-8b13805091c3",
"name": "Topic De-dup Selector",
"type": "@n8n/n8n-nodes-langchain.agent",
"notes": "",
"position": [
795,
215
],
"parameters": {
"text": "=Here is my posting history in JSON format.\nEach item includes Topic, Status, and Difficulty.\n\n{{ JSON.stringify($input.all().map(item => ({\n  topic: item.json.Topic,\n  status: item.json.Status,\n  difficulty: item.json.Difficulty\n}))) }}\n\nBased on this history:\n1. Propose 3 new topic ideas that do not overlap with the history.\n2. Assign a difficulty to each.\n3. Briefly explain why each topic is valuable for an n8n user.\n4. Select the best ONE topic to post this week and explain your choice.",
"options": {
"systemMessage": "You are an n8n expert and educator.\n\nYour task is to propose ONE weekly LinkedIn \u201chow-to\u201d topic about n8n.\nThe goal is to build authority and attract n8n users.\n\nRules:\n- Do not repeat previously used topics.\n- Prefer practical, experience-based problems.\n- Focus on teaching how to think, not just which nodes to click.\n- Audience: beginner to intermediate n8n users.\n- Topics should be concrete and specific.\n- Avoid generic topics like \u201cWhat is n8n\u201d.\n- Write the following response in Sentence Case. Only capitalize the first letter of the sentence and proper nouns like names or places."
},
"promptType": "define",
"hasOutputParser": true
},
"notesInFlow": true,
"typeVersion": 3
},
{
"id": "c073dc0d-a408-4e37-93d9-0b741347a2d6",
"name": "Branding Compliance Editor",
"type": "@n8n/n8n-nodes-langchain.agent",
"notes": "",
"position": [
200,
450
],
"parameters": {
"text": "=Please review and edit the following LinkedIn post according to your strict branding and formatting rules:\n\n{{ $json.output }}",
"options": {
"systemMessage": "You are a Senior Technical Editor specializing in n8n and enterprise automation. Your role is to polish LinkedIn posts to ensure they sound like they were written by a top-tier industry expert (Ambassador level).\n\nSTRICT EDITING RULES:\n1. NO EM DASHES: You must never use an em dash (\u2014). \n2. DASH SPACING: Replace any em dashes or tight hyphens with a spaced hyphen: \"word - word\". This is a non-negotiable branding requirement.\n3. REMOVE \"FOLLOW\" CTAs: Delete any requests for the reader to follow, like, or subscribe. The value of the content should speak for itself.\n4. EXPERT SIGN-OFF: Replace the deleted CTA with a confident, technical closing statement that highlights the power of n8n.\n5. HASHTAGS: End every post with exactly these three hashtags: #n8n #automation #lowcode.\n6. NO INTRO/OUTRO: Output only the final edited post. Do not include phrases like \"Here is the revised version.\"\n7. KILL AI FLUFF: Eliminate these words/phrases: \"unlock,\" \"harness,\" \"revolutionary,\" \"dive deep,\" \"game changer,\" \"seamlessly,\" \"mastering,\" \"look no further.\"\n8. STRATEGIC ENGAGEMENT (OPTIONAL): Occasionally (about 50% of the time), end with a high-level question that invites technical discussion (e.g., about global error states or node-level handling).\n9. Remove all the styles (bold, italic, etc) from the post.\n10. Rule: If the text mentions 'Function Node,' replace it with 'Code Node' to stay aligned with the latest n8n versioning.\n\nTONE & VOICE:\n- Professional, direct, and slightly technical.\n- Use \"white space\" between every section to ensure mobile readability.\n- Use bullet points (\u2022) for practical steps.\n\nIf the input text already follows these rules, simply ensure the spacing and dashes are perfect and return it."
},
"promptType": "define"
},
"notesInFlow": true,
"typeVersion": 3
},
{
"id": "955e7dc4-bf76-4b23-a215-c9ab78de7114",
"name": "AI Topic Analyst Mini",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
610,
120
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4o-mini",
"cachedResultName": "gpt-4o-mini"
},
"options": {
"temperature": 0.4
},
"builtInTools": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "e2d3f21a-ae90-4e58-99a5-cd6359ddfaac",
"name": "AI Content Architect",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
785,
345
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4o",
"cachedResultName": "gpt-4o"
},
"options": {
"temperature": 0.3
},
"builtInTools": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "e72829f3-0f00-4387-a0bd-5d479a815308",
"name": "AI Creative Writer",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
575,
365
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4o",
"cachedResultName": "gpt-4o"
},
"options": {
"temperature": 0.5
},
"builtInTools": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "67c84921-9c50-43c4-b7b2-c4886c5958df",
"name": "AI Format Guardian",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
255,
315
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4o",
"cachedResultName": "gpt-4o"
},
"options": [],
"builtInTools": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.3
},
{
"id": "60d1c2f0-9672-46a5-8333-46e1346634f4",
"name": "Collect Records",
"type": "n8n-nodes-base.aggregate",
"position": [
465,
255
],
"parameters": {
"options": [],
"aggregate": "aggregateAllItemData"
},
"typeVersion": 1
},
{
"id": "08853664-48fa-4b43-ad71-4608ceded160",
"name": "Failure Trigger",
"type": "n8n-nodes-base.errorTrigger",
"position": [
0,
540
],
"parameters": [],
"typeVersion": 1
},
{
"id": "b8f289f0-7ad8-475f-ae17-9dacb75d20b7",
"name": "Send Alert Email",
"type": "n8n-nodes-base.gmail",
"position": [
220,
530
],
"webhookId": "3a0fe92e-bee9-4527-80fb-d3fad07d0fe5",
"parameters": {
"sendTo": "[YOUR_EMAIL]",
"message": "=The LinkedIn engine failed at node: {{ $node[\"Failure Trigger\"].json[\"node\"][\"name\"] }}. Reason: {{ $node[\"Failure Trigger\"].json[\"execution\"][\"error\"][\"message\"] }}",
"options": [],
"subject": "\u26a0\ufe0f Workflow Error: LinkedIn Content Engine"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.2
},
{
"id": "2be9e695-0dd6-4b9f-a516-69949d1307c5",
"name": "Timeout Marker 48h",
"type": "n8n-nodes-base.noOp",
"notes": "",
"position": [
595,
530
],
"parameters": [],
"notesInFlow": true,
"typeVersion": 1
}
],
"pinData": [],
"connections": {
"Collect Records": {
"main": [
[
{
"node": "Topic De-dup Selector",
"type": "main",
"index": 0
}
]
]
},
"Failure Trigger": {
"main": [
[
{
"node": "Send Alert Email",
"type": "main",
"index": 0
}
]
]
},
"Post Draft Generator": {
"main": [
[
{
"node": "Branding Compliance Editor",
"type": "main",
"index": 0
}
]
]
},
"Scheduled Post Trigger": {
"main": [
[
{
"node": "Fetch Post History",
"type": "main",
"index": 0
}
]
]
},
"Gmail Review Gate": {
"main": [
[
{
"node": "Record Published Entry",
"type": "main",
"index": 0
}
],
[
{
"node": "Timeout Marker 48h",
"type": "main",
"index": 0
}
]
]
},
"Parsed Output Mapper": {
"ai_outputParser": [
[
{
"node": "Topic De-dup Selector",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"Structured Result Mapper": {
"ai_outputParser": [
[
{
"node": "Blueprint Logic Composer",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"Branding Compliance Editor": {
"main": [
[
{
"node": "Gmail Review Gate",
"type": "main",
"index": 0
}
]
]
},
"Blueprint Logic Composer": {
"main": [
[
{
"node": "Post Draft Generator",
"type": "main",
"index": 0
}
]
]
},
"Fetch Post History": {
"main": [
[
{
"node": "Collect Records",
"type": "main",
"index": 0
}
]
]
},
"Topic De-dup Selector": {
"main": [
[
{
"node": "Blueprint Logic Composer",
"type": "main",
"index": 0
}
]
]
},
"AI Creative Writer": {
"ai_languageModel": [
[
{
"node": "Post Draft Generator",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"AI Content Architect": {
"ai_languageModel": [
[
{
"node": "Blueprint Logic Composer",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"AI Format Guardian": {
"ai_languageModel": [
[
{
"node": "Branding Compliance Editor",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"AI Topic Analyst Mini": {
"ai_languageModel": [
[
{
"node": "Topic De-dup Selector",
"type": "ai_languageModel",
"index": 0
}
]
]
}
},
"id": null,
"versionId": null,
"name": "Automated LinkedIn Content Pipeline"
}