Perplexity to Gmail, LinkedIn drafts ready to post
You sit down to “post on LinkedIn” and somehow end up with 12 tabs open, half-finished notes, and a draft that sounds like everyone else. Then you skip a day. Then a week. It’s not lack of ideas. It’s the friction.
This Perplexity Gmail drafts automation hits consultants and founders hard, because your credibility is tied to showing up. Marketing leads feel it too when they’re trying to keep a personal brand active without turning it into a second job.
This workflow turns current, research-backed topics into LinkedIn-ready drafts, then sends them to you in Gmail for approval (with an optional Google Sheets log). You’ll see what it does, where the human review happens, and how to adapt it to your voice.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Perplexity to Gmail, LinkedIn drafts ready to post
flowchart LR
subgraph sg0["Click to start Flow"]
direction LR
n0@{ icon: "mdi:robot", form: "rounded", label: "🖼️ Image Prompt Generator", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code"]
n2@{ icon: "mdi:robot", form: "rounded", label: "Generate an image", pos: "b", h: 48 }
n4@{ icon: "mdi:play-circle", form: "rounded", label: "Click to start", 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/perplexity.dark.svg' width='40' height='40' /></div><br/>🔍 Research the Trends"]
n6@{ icon: "mdi:message-outline", form: "rounded", label: "Select the Best Topic", pos: "b", h: 48 }
n7@{ icon: "mdi:robot", form: "rounded", label: "✍️ Content Creator", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Content Aggregator", pos: "b", h: 48 }
n9@{ icon: "mdi:message-outline", form: "rounded", label: "Content Review & Approval", pos: "b", h: 48 }
n10@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF – Content Approval Routing", pos: "b", h: 48 }
n11@{ icon: "mdi:robot", form: "rounded", label: "✍️ Content Reviewer", pos: "b", h: 48 }
n12@{ icon: "mdi:message-outline", form: "rounded", label: "Final Content Delivery", pos: "b", h: 48 }
n1 --> n2
n4 --> n5
n2 --> n12
n8 --> n9
n6 --> n7
n7 --> n8
n11 --> n8
n5 --> n6
n9 --> n10
n0 --> n1
n10 --> n0
n10 --> n11
end
subgraph sg1["Schedule Flow"]
direction LR
n3@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
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 n4,n3 trigger
class n0,n2,n7,n11 ai
class n10 decision
class n1 code
classDef customIcon fill:none,stroke:none
class n1,n5 customIcon
The Challenge: Consistent LinkedIn Content Without Sounding Generic
Creating LinkedIn posts that feel timely and personal is annoying in a very specific way. The research part is scattered (newsletters, X, random articles), and by the time you’ve found something credible, you’ve lost the energy to write. So you reach for AI, get a draft, and it reads like a press release. Then you’re stuck editing, second-guessing sources, and trying to find an image that doesn’t look like stock art. It’s a lot of context switching for one post.
The friction compounds. Here’s where it breaks down.
- You waste about an hour bouncing between research, writing, and polishing for a single post.
- AI drafts come out “clean” but forget your lived experience, which means extra edits or you don’t post at all.
- Without an approval loop, you either over-automate and cringe later, or you keep everything manual and never scale.
- Visuals become a last-minute scramble, so you default to no image or something that doesn’t match the point.
The Fix: Research-to-Draft Emails With a Human Approval Loop
This workflow starts by pulling three recent, verifiable AI-related topics from Perplexity on a schedule (or whenever you run it manually). It emails those topics to you in Gmail so you can pick the one you actually want to talk about, which keeps you in control from the start. Once you choose, OpenAI generates a LinkedIn draft that blends the research with a more personal storytelling angle, then sends it back for review. If you reply with changes, the workflow routes your feedback through a revision assistant and rebuilds the draft. After approval, it generates a conceptual image using DALL·E 3 and emails you the final post text plus the image, ready to copy-paste into LinkedIn.
The workflow begins with Perplexity topic research, then moves into a Gmail-based selection step. Next, OpenAI writes (and if needed, rewrites) the draft, and DALL·E 3 creates a matching image. Finally, Gmail delivers the finished package to you so publishing stays a deliberate decision.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you aim for 4 LinkedIn posts a week. Manually, a typical cycle is about 30 minutes of research, 30 minutes to draft, and another 20 minutes polishing and finding an image. Call it about 5 hours a week. With this workflow, you spend maybe 5 minutes picking a topic from Gmail and 5 minutes reviewing the draft; DALL·E runs in the background and the final email shows up ready to post. That’s roughly 4 hours back every week, without lowering the bar.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Perplexity for topic research and sources.
- Gmail to send topics, drafts, and approvals.
- OpenAI API key (get it from your OpenAI dashboard).
Skill level: Intermediate. You’ll connect accounts, paste API keys, and tweak a few prompts safely.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Topic research kicks it off. On a schedule (or manual run), Perplexity finds three current topics that are meant to be verifiable, not hot takes with no sources.
You pick the angle inside Gmail. A “choose your favorite topic” email lands in your inbox, so the workflow doesn’t guess what you want to talk about. Quick reply, quick decision.
Draft creation and revision happens next. OpenAI writes the LinkedIn post, then Gmail sends it to you for review. If you reply with edits, an approval split routes that message into the revision assistant so the next draft is based on your actual notes.
Visual generation and delivery finishes the loop. Once approved, the workflow builds a clean image prompt, runs it through DALL·E 3, and sends the final post text plus the image via Gmail (and it can optionally log the run in Google Sheets).
You can easily modify the topic niche to match your industry 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 launches the content generation workflow.
- Add or open Scheduled Automation Trigger and set the weekly interval rule to run on Monday (field weeks with triggerAtDay =
1). - Keep Manual Execution Start in the workflow for ad-hoc testing and one-off runs without waiting for the schedule.
Step 2: Connect Research and Topic Selection
Configure the research call and the email-based topic selection flow.
- Open 🔍 Trend Insight Research and keep Model set to
sonar. Confirm the prompt pulls topic and context using{{ $json.body.Topic }}and{{ $json.body.Additional_Context }}. - Credential Required: Connect your perplexityApi credentials in 🔍 Trend Insight Research.
- Open Choose Preferred Topic and verify Operation is
sendAndWaitwith Response Type =customForm. - Set the email Subject to
Perplexity Research – Trends & Use Casesand keep the message body using the expressions{{ $json.search_results[0].title }},{{ $json.search_results[1].title }}, and{{ $json.search_results[2].title }}. - Credential Required: Connect your gmailOAuth2 credentials in Choose Preferred Topic.
Step 3: Set Up Draft Composition and Compilation
Create the draft content and store the final message for downstream nodes.
- Open ✍️ Post Draft Composer and keep the model set to
chatgpt-4o-latest. - Ensure the prompt references the selected topic via
{{ $json.data['Quale vuoi approfondire? '] }}and research insights via{{ $('🔍 Trend Insight Research').item.json.choices[0].message.content }}. - Keep the language selection expression as
{{ $json.data['Language'] || 'Italiano' }}. - Credential Required: Connect your openAiApi credentials in ✍️ Post Draft Composer.
- Open Content Compile Step and set message.content to
{{ $json.message.content }}so it can be reused in later email and visual steps.
Step 4: Configure Review, Approval, and Revision Routing
Send the draft for approval and route the flow based on feedback.
- Open Draft Review & Approval and confirm Operation is
sendAndWaitwith Response Type =customForm. - Keep the message body using
{{ $json.message.content }}for the draft preview and ensure the dropdown field hasYesandTo review. - Credential Required: Connect your gmailOAuth2 credentials in Draft Review & Approval.
- In Approval Decision Split, set the condition to compare
{{ $json.data['Ti piace?'] }}equalsYes. - If feedback is required, verify ✍️ Revision Assistant uses the original draft via
{{ $('✍️ Post Draft Composer').item.json.message.content }}and the feedback via{{ $json.data['Proposta di miglioramento'] }}. - Credential Required: Connect your openAiApi credentials in ✍️ Revision Assistant.
Step 5: Build the Visual Asset and Send the Final Email
Create a visual prompt, generate the image, and dispatch the final post.
- Open 🖼️ Visual Prompt Builder and confirm it references the compiled post content using
{{ $('Content Compile Step').item.json.message.content }}. - Credential Required: Connect your openAiApi credentials in 🖼️ Visual Prompt Builder.
- In Prompt Cleanup Script, keep the JavaScript as-is to clean and output
clean_prompt. - Open Create Visual Asset and set Model to
gpt-image-1with Resource =imageand Prompt ={{ $json.clean_prompt }}. - Credential Required: Connect your openAiApi credentials in Create Visual Asset.
- Open Final Post Dispatch and keep the message body referencing the compiled draft via
{{ $('Content Compile Step').item.json.message.content }}. - Credential Required: Connect your gmailOAuth2 credentials in Final Post Dispatch.
Step 6: Test and Activate Your Workflow
Validate the end-to-end flow before switching to scheduled production runs.
- Click Execute Workflow and trigger Manual Execution Start to run through research, topic selection, drafting, approval, and visual generation.
- Confirm you receive the Choose Preferred Topic email and submit the dropdown response.
- Verify that Draft Review & Approval sends the draft and that Approval Decision Split routes correctly based on your response.
- Check that Final Post Dispatch delivers the finalized post email and the workflow completes without errors.
- Once verified, toggle the workflow to Active so Scheduled Automation Trigger runs weekly.
Watch Out For
- Gmail permissions can be picky if you’re using a workspace account. If emails stop sending, check the connected Gmail credential in n8n first and confirm the right Google account is authorized.
- 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.
Common Questions
About 30 minutes if your Gmail and OpenAI keys are ready.
Yes, but you should expect a little setup work. You’ll connect Gmail, paste an OpenAI API key, and tweak the prompts to match your tone.
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 and Perplexity usage costs, plus DALL·E image generation.
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.
You can swap the Perplexity prompt in the “Trend Insight Research” step to focus on your niche (HR tech, cybersecurity, e-commerce, whatever you sell). Then tighten the “Post Draft Composer” prompt so it follows your structure, like hook → story → takeaway → soft CTA. Common customizations include adding a “for my audience” persona line, enforcing a word limit, and inserting your preferred sign-off.
Most of the time it’s expired Google authorization or the wrong account connected. Reconnect Gmail in n8n and confirm the sender mailbox matches the one you expect. If you’re on Google Workspace, admin policies can block certain scopes, so the OAuth consent screen will look “fine” but messages still won’t send.
On a typical n8n setup, it’s comfortable running daily or even multiple times per day. If you self-host, executions are mainly limited by your server and your API rate limits; Gmail and OpenAI are the usual bottlenecks. Practically, most small teams run this for a few drafts per day without thinking about capacity.
Often, yes, because this workflow needs branching (approve vs. revise), prompt clean-up, and multi-step AI generation with a clean handoff. n8n handles that kind of logic without turning every “if” into another paid task. Zapier or Make can still work if you simplify the flow and skip revisions or image generation. If your goal is “topic email only,” they’re fine. For the full research → draft → feedback → final package loop, n8n is usually the calmer experience. Talk to an automation expert if you want help deciding.
Once this is running, LinkedIn posting stops being a multi-tab project and turns into a simple approval habit. The workflow handles the repetitive parts so your attention goes to the perspective only you can add.
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.