Google Sheets + LinkedIn: approved posts, published
Your LinkedIn posting process probably looks “fine” until it suddenly doesn’t. A draft lives in a doc, feedback lands in DMs, someone approves “the wrong version,” and you still have no reliable record of what actually went out.
Marketing managers feel this when approvals drag. Agency owners feel it when clients ask for “the final copy” again. And founders doing it all themselves get stuck in the worst loop of all: writing, revising, rewriting. This Google Sheets LinkedIn automation gets you to approved posts faster, with a clean audit trail.
Below, you’ll see how the workflow turns a simple row in Google Sheets into an approved post, then publishes to LinkedIn automatically (and logs the proof).
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Google Sheets + LinkedIn: approved posts, published
flowchart LR
subgraph sg0["Schedule 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/linkedin.svg' width='40' height='40' /></div><br/>Create a post"]
n4@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger2", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items2", pos: "b", h: 48 }
n10@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Switch According Platform", pos: "b", h: 48 }
n14["<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/>Create Tweet"]
n15@{ icon: "mdi:database", form: "rounded", label: "Append Linkedin Post Url", pos: "b", h: 48 }
n16@{ icon: "mdi:database", form: "rounded", label: "Append Twitter Post Url", pos: "b", h: 48 }
n17["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Download Image"]
n18["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Upload Image"]
n19["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Download Img"]
n20@{ icon: "mdi:database", form: "rounded", label: "Get Post Data", pos: "b", h: 48 }
n26@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Image & Caption", pos: "b", h: 48 }
n27["<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/>Creating Container ID"]
n28["<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/>Facebook Graph API"]
n29@{ icon: "mdi:database", form: "rounded", label: "Append instagram Post Url", pos: "b", h: 48 }
n31["<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/>Split Data"]
n32["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Collect Instagram Post URL"]
n31 --> n9
n14 --> n16
n19 --> n0
n18 --> n14
n0 --> n15
n20 --> n31
n17 --> n18
n9 --> n10
n4 --> n20
n28 --> n32
n26 --> n27
n27 --> n28
n16 --> n9
n15 --> n9
n29 --> n9
n10 --> n19
n10 --> n17
n10 --> n26
n32 --> n29
end
subgraph sg1["Schedule Flow"]
direction LR
n1@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger1", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Platform", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "Append Likedin Data", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Append Twitter Data", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop", pos: "b", h: 48 }
n11["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Image Generate"]
n12@{ icon: "mdi:robot", form: "rounded", label: "Content for Twitter", pos: "b", h: 48 }
n13@{ icon: "mdi:robot", form: "rounded", label: "Content For Likedin", pos: "b", h: 48 }
n21@{ icon: "mdi:database", form: "rounded", label: "Get Content + Image Prompt", pos: "b", h: 48 }
n24@{ icon: "mdi:robot", form: "rounded", label: "Content for Instagram", pos: "b", h: 48 }
n25@{ icon: "mdi:database", form: "rounded", label: "Append instagram Data", pos: "b", h: 48 }
n30["<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/>Split Items"]
n8 --> n11
n30 --> n8
n5 --> n13
n5 --> n12
n5 --> n24
n11 --> n5
n2 --> n30
n1 --> n21
n6 --> n8
n7 --> n8
n13 --> n6
n12 --> n7
n25 --> n8
n24 --> n25
n21 --> n2
end
subgraph sg2["Schedule Flow"]
direction LR
n3@{ icon: "mdi:robot", form: "rounded", label: "Prompt Generate", pos: "b", h: 48 }
n22@{ icon: "mdi:database", form: "rounded", label: "Append Content + Img Prompt", pos: "b", h: 48 }
n23@{ icon: "mdi:database", form: "rounded", label: "Get Topic + Img Desc", pos: "b", h: 48 }
n33@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n3 --> n22
n33 --> n23
n23 --> n3
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,n1,n33 trigger
class n12,n13,n24,n3 ai
class n10,n5 decision
class n15,n16,n20,n29,n6,n7,n21,n25,n22,n23 database
class n17,n18,n19,n27,n28,n32,n11 api
class n31,n30 code
classDef customIcon fill:none,stroke:none
class n0,n14,n17,n18,n19,n27,n28,n31,n32,n11,n30 customIcon
The Challenge: Approvals that live everywhere
LinkedIn content isn’t usually hard because of writing. It’s hard because of coordination. A post starts as a quick draft, then feedback comes in from three places, the “approved” version gets lost, and publishing happens when someone remembers. Meanwhile you’re trying to stay consistent, keep the tone on-brand, and avoid posting something that never got a real sign-off. It’s exhausting, and frankly it’s easy to miss small details like links, images, or compliance notes when you’re copying and pasting under pressure.
It adds up fast. Here’s where it breaks down in real teams.
- You end up reviewing the same post multiple times because comments aren’t tied to a single “source of truth.”
- Publishing becomes manual busywork, so the schedule slips the moment your week gets messy.
- It’s hard to prove what was approved, when it was approved, and who approved it once the post is live.
- Small formatting changes happen at the last minute, which is how broken links and mismatched images sneak in.
The Fix: Google Sheets-driven approvals that publish to LinkedIn
This workflow treats Google Sheets as your control room. You add a topic (and a short description) to a row, and on a schedule the automation turns that row into a ready-to-review LinkedIn post using AI. The draft is written, optional images can be generated with your preferred image model, and everything gets logged back to the sheet so reviewers aren’t hunting across tools. Then the workflow pauses for human approval at key moments (first for the prompt, later for the final post). Once you mark it approved, n8n publishes the post to LinkedIn via the API and writes the result back to the same row, including a status and post URL for easy tracking.
The workflow begins with a scheduled check of your Google Sheet. AI generates the prompt and the draft content, then waits for approval. After the final approval, LinkedIn publishing happens automatically and the sheet becomes your permanent log.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you publish 5 LinkedIn posts a week. Manually, it’s easy to spend about 20 minutes per post coordinating reviews, cleaning up the latest version, and logging what was approved, which is roughly 2 hours weekly. With this workflow, you add topics to Google Sheets once, reviewers approve in the sheet, and publishing is automatic after sign-off. You still review, but the admin part drops to a few minutes per post, so you get most of that time back.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store topics, approvals, and logs.
- LinkedIn API access to publish posts automatically.
- OpenAI API key (get it from the OpenAI dashboard).
Skill level: Intermediate. You’ll connect accounts, set sheet columns, and paste API credentials.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Scheduled check against your content sheet. The Schedule Trigger runs on the cadence you choose and pulls rows from Google Sheets that are ready for drafting or review.
AI generates prompts, then drafts. Using OpenAI, the workflow creates platform-appropriate LinkedIn prompt text and a full post draft, then writes those fields back into the same row for visibility.
Approvals gate the workflow. If nodes read your approval columns. If a reviewer hasn’t approved yet, the workflow pauses (or safely does nothing) so nothing publishes early.
Publishing and logging happen together. Once the final approval flag is true, n8n publishes to LinkedIn via HTTP request/API, then updates Google Sheets with status, timestamps, and the final URL.
You can easily modify the approval stages to match your process, like adding a second reviewer or requiring an image check before posting. See the full implementation guide below for customization options.
Watch Out For
- Google Sheets permissions are the silent killer. If rows aren’t updating, check the connected Google account and the spreadsheet sharing settings first.
- If you’re using Wait nodes or external image rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- LinkedIn API access can be picky about scopes and app review. If publishing fails, it’s usually missing permissions or an expired token, not the workflow logic.
Common Questions
About an hour if your APIs are already set up.
Yes, but someone needs to handle the initial API credentials. After that, the day-to-day work is just updating rows and approvals in 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 (often a few dollars a month at typical posting volume) and any image generation API costs if you enable images.
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 change the approval logic by editing the If nodes that read your “Approved” columns in Google Sheets. Many teams add a second approval column for compliance, swap the image generator behind the HTTP Request node, or adjust the OpenAI prompt so it matches brand voice and avoids banned phrases. If you also publish to other platforms, you can keep LinkedIn as-is and extend the workflow with additional publishing branches after the Merge node.
Usually it’s an expired token or missing LinkedIn API permissions on your app. Reconnect the account in n8n, confirm the correct scopes are granted, then re-test publishing with a single approved row. If it still fails, check the HTTP response body in the execution logs because LinkedIn error messages are often specific about what field is invalid.
Plenty for most small teams.
Often, yes. The big win is control: approvals and branching logic are easier to model in n8n without turning every extra step into a paid “task.” You also get a real self-hosting option, which matters if you want unlimited runs or stricter data handling. On the other hand, Zapier or Make can be quicker for a basic “row added → post to LinkedIn” setup with no approvals. If your process involves two-stage approvals and logging, n8n is usually the calmer choice. Talk to an automation expert if you want help choosing.
Once this is in place, approvals stop being a scavenger hunt and LinkedIn publishing becomes a non-event. Set it up, keep your sheet tidy, and let the workflow handle the repeatable parts.
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.
