LinkedIn to Gmail, newsletter drafts ready to send
You write a strong LinkedIn post, it performs well… then it disappears into the feed. And when it’s time to email your list, you’re back to copy-pasting, reformatting, and trying to rebuild momentum from scratch. That’s LinkedIn Gmail automation you can feel missing every single week.
Marketing managers lose time polishing “good enough” drafts. Creators end up skipping newsletters entirely. And founders who do their own content? They usually send late, or not at all. This workflow gives you a ready-to-review HTML newsletter draft in your Gmail inbox, based on your latest LinkedIn post.
Below you’ll see exactly how the workflow pulls your newest post, rewrites it in newsletter style, formats it as HTML, and delivers it to Gmail so you can tweak and send without starting from zero.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: LinkedIn to Gmail, newsletter drafts ready to send
flowchart LR
subgraph sg0["Weekly Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Weekly Schedule", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Run an Actor and Get All Lin..", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Pulls the First Post", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Convert LinkedIn Post to Ema..", pos: "b", h: 48 }
n4@{ icon: "mdi:robot", form: "rounded", label: "Convert Text to HTML Format", pos: "b", h: 48 }
n5@{ icon: "mdi:message-outline", form: "rounded", label: "Send a message", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Variable Mapping", pos: "b", h: 48 }
n0 --> n1
n6 --> n3
n2 --> n6
n4 --> n5
n1 --> n2
n3 --> n4
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n3,n4 ai
class n1 decision
The Problem: Turning LinkedIn Posts Into Newsletters Takes Too Long
Repurposing a LinkedIn post into an email newsletter sounds simple until you do it every week. You paste the post into a doc, rewrite the opening so it doesn’t feel like social media, add structure, add a call-to-action, then wrestle with formatting so the email doesn’t look broken in Gmail. Meanwhile, your best ideas are already written. The real cost is the mental load: you delay sending, your list gets cold, and consistency turns into a “maybe next week” habit.
It adds up fast. Here’s where it usually breaks down.
- You spend about an hour rewriting content you already published because email needs a different rhythm than LinkedIn.
- Formatting for email is fiddly, and a draft that looked fine in a doc can render weird once it’s in an inbox.
- When you miss a week, you don’t just lose that send. You lose the routine that makes newsletters work.
- Manual copy-paste invites small mistakes like broken links, missing paragraphs, or a CTA that gets forgotten.
The Solution: LinkedIn-to-Newsletter Drafts Sent to Gmail
This n8n workflow watches your LinkedIn profile on a schedule, pulls your most recent post, and turns it into a newsletter-style draft you can actually send. It uses an Apify actor to extract your LinkedIn posts, automatically isolates the latest one, then maps the fields into a clean input for AI. From there, OpenAI rewrites the post into newsletter language with better structure, clearer sections, and a more “inbox-friendly” flow. Finally, it renders the result as email-ready HTML and sends it straight into your Gmail inbox as a notice/draft you can review, tweak, and ship.
The workflow starts with a weekly schedule trigger. Then Apify retrieves posts and n8n limits the list to the newest entry. OpenAI drafts the newsletter copy first, then a second OpenAI step produces polished HTML, and Gmail delivers it where you already work.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish one LinkedIn post each week and want to email it to your list. Manually, you might spend about 45 minutes rewriting the post into newsletter form, plus another 30 minutes getting HTML formatting and spacing to look right in Gmail, so call it about 1.5 hours weekly. With this workflow, the “work” is basically reviewing: the schedule runs, Apify pulls the latest post, OpenAI drafts and formats it, and Gmail delivers it. Most weeks you’re down to about 10–15 minutes to edit and send.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Apify account to scrape LinkedIn posts on schedule
- OpenAI to rewrite and format as newsletter HTML
- Gmail API credentials (get it from Google Cloud Console)
Skill level: Intermediate. You’ll connect accounts, add API keys, and test a few runs to confirm the output matches your newsletter style.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A weekly schedule kicks it off. The workflow runs automatically on the cadence you choose (weekly by default), so you don’t have to remember to “do newsletter day.”
LinkedIn content gets pulled via Apify. An Apify actor retrieves posts from the LinkedIn profile URL you specify, then n8n immediately limits the dataset to the most recent post so you’re always working from the latest publish.
The post is cleaned up and rewritten. n8n maps the fields it needs (text, link, metadata), then OpenAI drafts newsletter copy that reads naturally in email instead of feeling like a reposted social caption. A second OpenAI step renders that copy into email-friendly HTML.
The finished draft lands in Gmail. Gmail sends you the HTML newsletter draft as a message/notice so you can skim it, adjust your CTA, and send it to subscribers using your normal email tool or workflow.
You can easily modify the prompt and formatting rules to match your brand voice and preferred newsletter layout. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the workflow to run weekly using the schedule trigger.
- Add the Weekly Automation Trigger node as the trigger.
- In Weekly Automation Trigger, keep the default rule with an interval field set to
weeks. - Connect Weekly Automation Trigger to Retrieve LinkedIn Posts.
Step 2: Connect Apify and Fetch LinkedIn Posts
Pull the latest LinkedIn post using Apify and limit the dataset to the first item.
- Open Retrieve LinkedIn Posts and set Operation to
Run actor and get dataset. - Set Custom Body to
{ "usernames": ["[YOUR_ID]"], "maxItems": 1, "maxResults": 1 }. - Credential Required: Connect your apifyOAuth2Api credentials.
- Connect Retrieve LinkedIn Posts to Limit to First Post.
- Connect Limit to First Post to Map Post Fields.
Step 3: Set Up the Post Mapping and AI Drafting
Map the LinkedIn text into a clean field and generate newsletter copy with AI.
- In Map Post Fields, add an assignment with Name
linkedin_postand Value={{ $json.text }}. - Connect Map Post Fields to Draft Newsletter Copy.
- In Draft Newsletter Copy, set Model to
chatgpt-4o-latest. - Confirm the prompt uses the LinkedIn post via
{{ $json.linkedin_post }}. - Credential Required: Connect your openAiApi credentials.
Step 4: Generate HTML and Send the Email
Convert the AI draft to HTML and deliver it via Gmail.
- Connect Draft Newsletter Copy to Render HTML Email.
- In Render HTML Email, set Model to
chatgpt-4o-latestand ensure the prompt references{{ $json.message.content }}. - Credential Required: Connect your openAiApi credentials.
- Connect Render HTML Email to Dispatch Email Notice.
- In Dispatch Email Notice, set Send To to
[YOUR_EMAIL]. - Set Subject to
Latest Newsletter Articleand Message to{{ $json.message.content }}. - Credential Required: Connect your gmailOAuth2 credentials.
Step 5: Test and Activate Your Workflow
Run a manual test to confirm the full execution chain before activating the weekly schedule.
- Click Execute Workflow and verify that Retrieve LinkedIn Posts returns a dataset item.
- Check that Draft Newsletter Copy outputs a complete newsletter with subject line and body.
- Confirm Render HTML Email produces valid HTML starting with
<html>tags. - Ensure Dispatch Email Notice sends an email to
[YOUR_EMAIL]with the HTML content. - Turn on the workflow using the Active toggle to enable weekly automation.
Common Gotchas
- Apify credentials can expire or need specific permissions. If things break, check your Apify token and actor run history in the Apify console 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 once your Apify and Gmail access are ready.
No. You will mostly paste API keys and connect accounts in n8n. The only “tweak” work is editing prompts if you want a specific style.
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 usage and your Apify plan if you exceed the free tier.
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 you should. Update the prompt in the “Draft Newsletter Copy” OpenAI node to match your voice (shorter intros, more opinion, more structure, whatever you prefer), then adjust the “Render HTML Email” node to enforce your layout. Common customizations include adding a “What I’m working on” section, inserting a standard footer, and changing the CTA to point at a booking link or new offer.
Usually it’s OAuth credentials or permissions in your Google Cloud project. Re-authenticate the Gmail node in n8n, confirm the correct Google account is connected, and check that the Gmail API is enabled for that project. If it fails only sometimes, you may also be hitting sending limits on the Gmail account you connected.
Plenty for a normal publishing schedule.
Often, yes, because this workflow mixes scraping, mapping, and multi-step AI formatting in one flow. Zapier and Make can do parts of it, but you may end up paying more once you add extra steps, branching, or higher task volume. n8n is also easier to self-host if you want more control over executions and data. If you only need a simple “new post → email me the text” bridge, those tools can be fine. Talk to an automation expert if you’re not sure which fits.
Once this is running, your newsletter draft shows up like clockwork. You stay consistent, and you stop burning an afternoon on formatting.
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.
