Google Sheets to LinkedIn, posts published consistently
Your LinkedIn plan usually breaks in the same place. You have ideas scattered across notes, a half-finished draft in a doc, and then Monday shows up and you post… nothing.
Marketing managers feel it when “consistent posting” turns into a weekly scramble. Founders hit the wall when content competes with everything else. And consultants trying to stay visible end up repeating topics because they can’t remember what’s already gone out. This LinkedIn post automation fixes that.
You’ll use one Google Sheet as a content queue, let AI write the post and generate an image, then publish to LinkedIn on a schedule. Add a row. Stay on track.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Sheets to LinkedIn, posts published consistently
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Get row(s) in sheet1", pos: "b", h: 48 }
n2@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", 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/merge.svg' width='40' height='40' /></div><br/>Merge"]
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/linkedin.svg' width='40' height='40' /></div><br/>Create a post"]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Row", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "Generate Image", pos: "b", h: 48 }
n7@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n9@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger1", pos: "b", h: 48 }
n10@{ icon: "mdi:database", form: "rounded", label: "Mark as Published", pos: "b", h: 48 }
n3 --> n4
n8 --> n3
n5 --> n6
n5 --> n8
n4 --> n10
n2 -.-> n8
n6 --> n3
n7 -.-> n8
n9 --> n1
n1 --> n5
n0 -.-> n8
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 n9 trigger
class n0,n6,n8 ai
class n7 aiModel
class n2 ai
class n1,n10 database
classDef customIcon fill:none,stroke:none
class n3,n4 customIcon
Why This Matters: Consistent Posting Without the Daily Grind
Posting on LinkedIn sounds simple until you try to do it every week, for months. Ideas come in bursts, but publishing needs rhythm. So you end up doing the same annoying cycle: pick a topic, write something “good enough,” hunt for an image, rewrite the hook twice, then post at whatever time you remembered. Next week you either repeat yourself or avoid a topic you should have owned, because you can’t tell what you already published. Honestly, the mental load is the killer more than the writing.
The friction compounds. Here’s where it breaks down in real life.
- You lose about 30 minutes per post just deciding what to write because your “idea backlog” isn’t in one place.
- Teams accidentally reuse the same topic, which makes your content feel stale even when the advice is solid.
- Finding or creating a usable image turns into another mini-project, so posts get delayed or skipped.
- Manual posting has no built-in accountability, so missed days become missed weeks.
What You’ll Build: Google Sheets → AI Content → LinkedIn Publishing
This workflow turns a simple Google Sheet into a reliable LinkedIn publishing engine. It runs on a schedule (for example, every weekday morning). When it fires, it looks in your sheet for the first topic marked “Unpublished,” pulls that row, and hands the topic to an AI agent to generate a post in the style you want. In parallel, the workflow creates a matching image asset that visually includes the topic title so your post doesn’t look like another plain text update. Then it merges the text and image into one payload, publishes directly to LinkedIn through the API, and updates the same sheet row to “Published” so it doesn’t get reused.
The workflow starts with scheduled retrieval from Google Sheets. AI generates the post and image from the selected topic, then everything is combined and sent to LinkedIn. Finally, the sheet is updated so your queue stays clean and you can scale without losing track.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you publish 5 times a week. Manually, a typical post takes about 30 minutes to write plus maybe 15 minutes to find or create an image, so you’re at roughly 4 hours a week (and that’s on a “good” week). With this workflow, you spend around 10 minutes on Monday adding five rows to your Google Sheet, then the scheduled run handles the writing, image creation, publishing, and status updates. You get most of that time back, and your posting stops depending on your calendar mood.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store topics and statuses.
- LinkedIn to publish posts via the API.
- OpenAI API key (get it from your OpenAI API dashboard).
Skill level: Intermediate. You’ll connect OAuth credentials and tweak an AI prompt, but you won’t be writing code.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A scheduled run checks your content queue. The Schedule Trigger fires at your chosen time (daily, weekdays only, or any cadence that fits). It kicks off a Google Sheets lookup for topics that are still marked “Unpublished.”
Your next topic is selected and prepared. The workflow splits out the first eligible row, so you’re publishing one post per run instead of blasting your whole backlog. That’s what keeps it steady.
AI generates the post and the image. The AI agent writes the LinkedIn copy from the topic, and a separate OpenAI image node creates a matching image asset. A Merge node combines the text and image data into one package ready for publishing.
LinkedIn publishes, then Google Sheets is updated. The LinkedIn node posts to your profile, and the final Google Sheets step flags that topic as “Published.” Next run, it moves on automatically.
You can easily modify the posting cadence to fit your schedule, or adjust the AI prompt to match your brand voice. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Automation Trigger
Start the workflow on a schedule so content is checked and published automatically.
- Add and open Scheduled Automation Trigger.
- Set your preferred schedule (e.g., hourly or daily) in the trigger settings.
- Connect Scheduled Automation Trigger to Retrieve Sheet Rows.
Step 2: Connect Google Sheets
Pull content rows for publishing and update their status after posting.
- Open Retrieve Sheet Rows and select the spreadsheet and worksheet that contain your content queue.
- Credential Required: Connect your Google Sheets credentials.
- Open Flag as Published and configure the same spreadsheet to update the publish status column.
- Credential Required: Connect your Google Sheets credentials.
⚠️ Common Pitfall: Both Google Sheets nodes must point to the same file and use consistent column names to avoid updates failing.
Step 3: Set Up Record Processing and Parallel AI Generation
Split each row into an individual job, then generate content and an image in parallel.
- Configure Split Record to output one item per sheet row.
- Ensure Split Record outputs to both Create Image Asset and Autonomous AI Agent in parallel.
- Open Create Image Asset and set your image prompt fields based on the sheet data.
- Credential Required: Connect your OpenAI credentials in Create Image Asset.
- Open Autonomous AI Agent and define the instructions for generating the LinkedIn post content.
Step 4: Configure the AI Engine and Parsers
Wire up the AI model and output structure for consistent results.
- Open OpenAI Chat Engine and select your model configuration for the agent.
- Credential Required: Connect your OpenAI credentials in OpenAI Chat Engine.
- Verify Structured Result Parser is connected to Autonomous AI Agent as the output parser.
- Verify Compact Memory Buffer is connected to Autonomous AI Agent as memory.
Credential Required: For AI sub-nodes Structured Result Parser and Compact Memory Buffer, add credentials on the parent OpenAI Chat Engine and Autonomous AI Agent connections (not on the sub-nodes themselves).
Step 5: Combine Results and Publish to LinkedIn
Merge the generated text and image into a single payload, then publish it.
- Open Combine Streams and make sure it receives inputs from both Create Image Asset and Autonomous AI Agent.
- Confirm Combine Streams outputs to Publish LinkedIn Post.
- Open Publish LinkedIn Post and map the merged content fields to the LinkedIn post body and image.
- Credential Required: Connect your LinkedIn credentials in Publish LinkedIn Post.
- Connect Publish LinkedIn Post to Flag as Published to update the sheet after a successful post.
Step 6: Test and Activate Your Workflow
Run a full test to validate content generation, merging, and publishing.
- Click Execute Workflow to run the automation manually from Scheduled Automation Trigger.
- Confirm that Split Record creates a single item per row and that both AI branches complete.
- Verify a LinkedIn post is created by Publish LinkedIn Post and the row is updated by Flag as Published.
- Turn on the workflow using the Active toggle once the test succeeds.
Troubleshooting Tips
- Google Sheets credentials can expire or need specific permissions. If things break, check the credential in n8n’s Credentials tab first, then confirm the spreadsheet is shared with the right Google account.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- LinkedIn API access is picky and scopes matter. If publishing fails, verify your LinkedIn app is approved for posting and that your OAuth token in n8n includes the correct permissions for content publishing.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About an hour if you already have your LinkedIn app and Sheet ready.
No. You’ll connect Google Sheets and LinkedIn in n8n, then adjust a prompt and a couple of fields.
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 (often a few cents per post, depending on your prompt and image settings).
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. You can change the Schedule Trigger to post daily, weekly, or only on weekdays, then rewrite the AI prompt inside the OpenAI Chat Engine/Autonomous AI Agent to match your voice. If you don’t want images, you can remove the Create Image Asset node and publish text-only. Another common tweak is adding an approval step (Telegram, email, or Slack) between the AI output and the LinkedIn publish node.
Usually it’s an OAuth scope or an app permissions issue. Reconnect your LinkedIn OAuth2 credential in n8n, double-check the app is allowed to publish on behalf of your account, and confirm you’re not hitting API limits if you’re testing repeatedly in a short window.
If you’re posting once per day, it will barely register on most setups.
Often, yes for this specific use case. You’re combining scheduled logic, row-by-row queue handling, AI generation, image creation, and then a publish + “mark as published” update, which is where simpler tools start to get clunky or expensive. n8n also gives you more control over branching (like “only post when there’s an Unpublished row”) and it’s easier to self-host if you want unlimited runs. Zapier or Make can still work if you keep it simple and skip the image generation. Talk to an automation expert if you want help choosing.
Once this is running, consistency stops being a willpower test. The workflow handles the repetitive parts so you can focus on having something worth saying.
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.
