WordPress to LinkedIn, posts published and logged
Publishing the blog post is the easy part. The annoying part is turning it into social content, rewriting the caption three different ways, posting to LinkedIn and Facebook, then tracking what you posted so you can reuse the winners later.
This WordPress social automation hits marketing managers hardest, but agency owners and busy solo founders feel it too. You get posts drafted, published, and logged automatically, which usually saves a few hours every week and removes the “did we already share this?” guesswork.
Below is what the workflow does, how it moves from new content to scheduled distribution, and how you can adapt it to your own channels and spreadsheet.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: WordPress to LinkedIn, posts published and logged
flowchart LR
subgraph sg0["RSS Intake Flow"]
direction LR
n0["<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/webhook.dark.svg' width='40' height='40' /></div><br/>WP Webhook Entry"]
n1@{ icon: "mdi:robot", form: "rounded", label: "AI Content Review", pos: "b", h: 48 }
n2@{ icon: "mdi:play-circle", form: "rounded", label: "RSS Intake Trigger", pos: "b", h: 48 }
n3["<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/>Interpret AI Result"]
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/x.dark.svg' width='40' height='40' /></div><br/>Publish Twitter Update"]
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/linkedin.svg' width='40' height='40' /></div><br/>Post LinkedIn Update"]
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/facebook.svg' width='40' height='40' /></div><br/>Publish Facebook Post"]
n7["<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/merge.svg' width='40' height='40' /></div><br/>Combine Social Streams"]
n8["<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/merge.svg' width='40' height='40' /></div><br/>Join Source Inputs"]
n9@{ icon: "mdi:database", form: "rounded", label: "Log Content Archive", pos: "b", h: 48 }
n7 --> n9
n8 --> n1
n4 --> n7
n5 --> n7
n3 --> n4
n3 --> n5
n3 --> n6
n1 --> n3
n2 --> n8
n0 --> n8
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 n2 trigger
class n1 ai
class n9 database
class n0,n6 api
class n3 code
classDef customIcon fill:none,stroke:none
class n0,n3,n4,n5,n6,n7,n8 customIcon
The Problem: Social posting turns into copy-paste chaos
If you publish content weekly (or daily), social promotion quietly becomes a second job. You open WordPress, grab the link, write a LinkedIn version, rewrite it again for Facebook, then decide if you should also tweet it. Next week you do it again, except you can’t remember what angle you used last time, so you start from scratch. And because tracking is an afterthought, your “content spreadsheet” is either empty or full of half-updated rows that nobody trusts. Honestly, the mental load is worse than the typing.
It adds up fast. Here’s where it breaks down in real teams.
- Every post becomes 3–4 separate writing tasks, and each one steals focus from higher-value work like planning campaigns.
- Manual posting is easy to delay, so promotion slips a day or two and the content never gets its best chance.
- Captions get inconsistent because whoever is available writes them, which means your voice drifts over time.
- Without a reliable log, you lose track of what shipped, what to repurpose, and which hooks are actually working.
The Solution: Auto-generate, publish, and archive every promo post
This n8n workflow acts like a lightweight content manager that never forgets the follow-through. It starts when new content arrives from WordPress (via webhook) or from an RSS feed (for example, if your “source of truth” is a channel feed). That content is sent to OpenAI (GPT-4) for a quick review that creates a summary, pulls out keywords, checks sentiment, and drafts platform-specific captions. After that, n8n interprets the AI output and routes each caption to the right destination, publishing updates to LinkedIn and Facebook (and Twitter/X if you keep that node enabled). Finally, it merges the publishing results and logs the link, captions, and useful metadata into Google Sheets so you always have a clean archive.
The workflow begins with “new content detected.” Then AI turns that content into ready-to-post drafts with your preferred structure. Publishing happens next through connected social nodes, and Google Sheets becomes the record you can actually rely on.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish 3 WordPress posts per week and promote each one on LinkedIn and Facebook. Manually, you typically spend about 15 minutes crafting each caption and another 10 minutes posting and double-checking links, so that’s roughly 50 minutes per article, or about 2–3 hours weekly. With this workflow, your “work” is basically publishing the post (or letting the RSS feed update), then waiting for the automation to run and log the results in Sheets. That’s usually a few minutes of oversight instead of an ongoing task list.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- WordPress as the content source (webhook trigger).
- RSS Feed to ingest content from another source.
- OpenAI API key (get it from the OpenAI dashboard).
- LinkedIn to publish the update from n8n.
- Facebook to publish the post via Graph API.
- Google Sheets for the content log and archive.
Skill level: Intermediate. You’ll connect accounts, set permissions, and map a few fields into your spreadsheet.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
New content triggers the workflow. A WordPress webhook catches newly published posts, and an RSS intake trigger can bring in updates from feeds you care about.
AI reviews the content and drafts posts. The OpenAI node generates a summary, keyword list, sentiment notes, and separate drafts for each platform so you’re not forcing one caption everywhere.
n8n shapes the output and routes it. A small interpretation step converts the AI response into clean fields, then each social node publishes its version (LinkedIn update, Facebook post, and optionally Twitter/X).
Everything is merged and logged. Publishing responses are combined and written into Google Sheets, giving you a durable record of what went out and what it said.
You can easily modify the AI prompt to match your tone, or switch the destinations based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the inbound webhook so WordPress or other systems can push content into the workflow.
- Add the WP Webhook Entry node and open its settings.
- Copy the Webhook URL from WP Webhook Entry and paste it into your WordPress webhook sender.
- Connect WP Webhook Entry to Join Source Inputs as shown in the workflow.
Step 2: Configure the RSS Trigger and Source Merge
Bring in RSS content and merge it with webhook inputs before AI processing.
- Open RSS Intake Trigger and set the RSS feed URL in its configuration.
- Connect RSS Intake Trigger to Join Source Inputs.
- Ensure Join Source Inputs has two inputs (from WP Webhook Entry and RSS Intake Trigger) and outputs to AI Content Review.
Step 3: Set Up the AI Review Stage
Use AI to review or transform incoming content before publishing.
- Open AI Content Review and configure the model/prompt settings as needed for your content checks.
- Credential Required: Connect your OpenAI credentials in AI Content Review.
- Confirm the output of AI Content Review connects to Interpret AI Result.
Step 4: Configure Publishing Actions and Parallel Routing
Parse AI output and publish to social channels in parallel.
- In Interpret AI Result, add code to map AI output fields into the expected social post structures.
- Connect Interpret AI Result to Publish Twitter Update, Post LinkedIn Update, and Publish Facebook Post so they run in parallel.
- Credential Required: Connect your Twitter credentials in Publish Twitter Update.
- Credential Required: Connect your LinkedIn credentials in Post LinkedIn Update.
- Credential Required: Connect your Facebook Graph API credentials in Publish Facebook Post.
- Publish Twitter Update, Post LinkedIn Update, and Publish Facebook Post all feed into Combine Social Streams to aggregate results.
Step 5: Log Results to Google Sheets
Archive the combined social publishing results for reporting and auditing.
- Open Log Content Archive and select the target spreadsheet and worksheet.
- Credential Required: Connect your Google Sheets credentials in Log Content Archive.
- Confirm Combine Social Streams connects to Log Content Archive as the final step.
Step 6: Test and Activate Your Workflow
Validate each path and then enable the workflow for production use.
- Click Execute Workflow and send a test payload to WP Webhook Entry or wait for RSS Intake Trigger to fire.
- Verify that Interpret AI Result routes outputs to Publish Twitter Update, Post LinkedIn Update, and Publish Facebook Post in parallel.
- Confirm that Log Content Archive receives a new row with publishing results.
- When satisfied, toggle the workflow to Active to run continuously.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google connection in n8n’s Credentials and confirm the spreadsheet is shared to the right Google account.
- If you’re using RSS feeds that update in bursts, processing times vary and you can hit rate limits downstream. Slow it down or add a longer wait if social nodes fail because the data wasn’t ready yet.
- Default prompts in the OpenAI node are generic. Bake in your brand voice (tone, CTA style, and what to avoid) early or you’ll be editing outputs forever.
Frequently Asked Questions
About an hour if your accounts and permissions are ready.
No. You will mostly connect credentials and map fields into Google Sheets.
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 typically a few cents per run depending on prompt size.
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 inside the “AI Content Review” node to include your voice, banned phrases, CTA style, and formatting rules (like line breaks for LinkedIn). Common tweaks include generating two LinkedIn variants, adding hashtags from the keyword list, and changing the routing so some posts are “draft-only” and sent to Slack for approval.
Usually it’s expired credentials or missing permissions for the LinkedIn app connection inside n8n. Reconnect your LinkedIn credential, then verify the account has posting access to the profile or company page you selected. If it fails only during busy periods, it can also be rate limiting, so slow down how many items you publish per run.
A lot.
Often, yes, because this is not just “send link to LinkedIn.” You’re doing AI content generation, conditional routing, and merging results into a clean archive, which can get expensive or awkward in Zapier/Make once you add branching and multiple destinations. n8n also gives you the self-host option, so you are not paying per tiny step forever. The trade-off is that n8n feels a bit more “builder” than “wizard,” so the first setup takes longer. If you want someone to sanity-check the approach before you invest time, Talk to an automation expert.
You publish. The workflow promotes and logs. And your Google Sheet becomes a real archive instead of a guilt project.
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.
