Google Sheets to social posts: a simple content queue with an approval column

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: A Google Sheet can be a content queue: one row per post, a Status column that blocks posting until a human sets Approved, and an automation that picks one approved row at a time, publishes it, and writes the result back. Blotato, a software subscription that publishes posts to 11 social networks, has a ready-made template for this in n8n and Make, two workflow automation tools. The part most guides skip is writing back the live post URL after checking that it really published.

Ranjit Bhinge

A spreadsheet is the friendliest content calendar there is. The risk is a row posting before anyone looked at it, or a row marked Posted that never went live.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

A sheet queue works because everyone already knows how to use a spreadsheet. The automation does three jobs: pick the next ready row, publish it, and report back. This guide gives you the sheet layout, the status rules, the steps in n8n and Make, the error handling and a 20 row test. It builds on the template Blotato publishes, called "Post Everywhere", and adds two things that template does not insist on: a human approval column, and a posted URL written back from a status check. The posting step is Blotato, a tool that publishes to 11 social networks.

This page may contain affiliate links from which Blur Studio earns commissions.

The sheet layout

One tab, one row per post per platform. Keep the header row exactly as you name it, because the automation looks columns up by name. If you import Blotato's template, keep its column names unchanged, as its help page says.

ColumnFilled byExample (made up)Notes
content_idYouCAFE-0007Unique. Your handle for the row.
statusHuman, then automationApprovedThe gate. See the rules below.
platformYouinstagramValues Blotato accepts: twitter, linkedin, facebook, instagram, pinterest, tiktok, threads, bluesky, youtube, slack, discord.
account_idYou11111From GET /v2/users/me/accounts. Never guess it.
destination_idYou333333Facebook pageId, Pinterest boardId, Slack or Discord channelId. Blank if not needed.
textYouFresh scones at 8 todayRespect each platform's length limit.
media_urlYouhttps://example.com/scones.jpgA public link that opens without a login.
scheduled_time_utcYou, optional2026-12-02T08:00:00ZBlank means publish at the next run.
approved_byHumanSamWho said yes.
submission_idAutomation(filled)From Blotato's create response.
posted_urlAutomation(filled)Written only after the status check says published.
error_messageAutomation(filled)From the status check, when failed.

Put a dropdown on status, so nobody types "aproved". Google Sheets lets you protect a range, so restrict the status column to the people allowed to approve, and make the automation's Google account the only other editor.

The status rules that make it safe

  • Draft: anyone writes here. The automation ignores it.
  • Approved: only a human sets this, after reading the text, media and destination. This is the only value the automation will pick up. (Blotato's template uses the label "Ready to Post" for the same gate and advises a human review before setting it. If you import the template, keep its label, or change the label in the workflow's query to match yours.)
  • Submitted: the automation sets this, and writes submission_id, immediately after Blotato accepts the request and before it checks anything. This stops the next run from picking the same row.
  • Scheduled: the status check returned scheduled. The post is queued, not live.
  • Posted: the status check returned published. Only now does it write posted_url.
  • Failed: the status check returned failed. The error text goes in error_message.

Two rules to keep: a row that is only scheduled must never be marked Posted, and a failed row must go back to a human, not retry by itself. Editing the text of an Approved row should reset it to Draft. A small script attached to the sheet can do that, or a rule that you never edit approved rows.

Step 1: the trigger

Blotato's template checks the sheet on a schedule, every 3 hours, and picks one row whose status is the ready value. Limiting the search to one row per run is deliberate: it keeps the queue slow and safe, and it matches Blotato's rate limit of 30 create-post requests a minute. In n8n use a Schedule Trigger followed by a Google Sheets node set to read rows, filtered by status, limited to 1 row. In Make use a scheduled scenario with a Google Sheets search module (limit 1). In Zapier there is no official Blotato app, so use Webhooks by Zapier for the post request, and a Google Sheets lookup for the row. Webhook actions are among Professional features on Zapier's pricing page.

If you want posts to go out at a particular time, put it in scheduled_time_utc. If you want them in your weekly slots, use the next free slot instead. See scheduling posts with an automation.

Step 2: the post request

Map the columns to Blotato's request. For an Instagram image from a row, the body is:

{
  "post": {
    "accountId": "11111",
    "content": {
      "text": "Fresh scones at 8 today",
      "mediaUrls": ["https://example.com/scones.jpg"],
      "platform": "instagram"
    },
    "target": {
      "targetType": "instagram"
    }
  },
  "scheduledTime": "2026-12-02T08:00:00Z"
}

Three things to check in this example. First, Instagram's mediaType is optional. Blotato's reference says it defaults to reel for videos and accepts story for a Story, so leave it out for a feed image, and test an image row and a video row separately. Second, scheduledTime sits at the top level, next to post. Nested inside, it is ignored and the post goes out at once. Third, leave out scheduledTime to publish immediately. The platform and target type must match. Each platform has its own required fields (Facebook needs pageId, Pinterest needs boardId, YouTube needs title, privacyStatus and shouldNotifySubscribers, TikTok needs a privacy level and disclosure flags, Slack and Discord need channelId), which is why the sheet has a destination column. For the n8n node, see the n8n setup guide, and for Make, Make modules and templates.

Media must be a public link. Google Drive and Dropbox share links often fail because of redirects or login pages. Blotato's template notes say Drive files over 60 MB do not work, so use Amazon S3 storage for big videos. The upload limit is 400 MB on Starter and 1 GB on Creator and Agency.

Step 3: write the status back

  1. Blotato answers with postSubmissionId. Immediately update the row: status = Submitted, submission_id filled in.
  2. Wait at least 10 seconds. Call GET /v2/posts/{postSubmissionId} (n8n: Post, Get).
  3. If in-progress, wait and repeat, up to a cap such as 12 checks.
  4. If published, set status = Posted and write publicUrl into posted_url.
  5. If scheduled, set status = Scheduled.
  6. If failed, set status = Failed and write errorMessage to error_message.
  7. If the cap is reached, leave it as Submitted and let the cleanup run (below) pick it up.

A more robust shape is a second small workflow that runs every 15 to 30 minutes, reads rows whose status is Submitted or Scheduled, and checks each by ID. That one also catches rows where the first workflow crashed after creating the post. Blotato has no webhook for post status, so checking is how you learn. See webhooks and Blotato and fix silent failures.

Step 4: errors

What you seeLikely causeWhat to do
HTTP 401Key copied without its trailing equals sign, or an old key.Recopy the key in the credential.
HTTP 422A field is wrong or missing, such as pageId.Fix the named field in the row.
HTTP 429Too many requests.Wait, and keep one row per run.
Status failed with a media messageLink needs login, expired, or file too large.Use a public link or S3.
Row stuck on SubmittedCap reached, or the ID was wrong.Look up the ID in Blotato's Posts page or Logs.
Two posts for one rowRun started twice or Submitted was not written first.Write Submitted before checking. Look for the existing post before any retry.

There is no idempotency header in Blotato's API (no way to mark a request as a repeat), so do not retry a create call without looking for the existing post. Use n8n's Error workflow or a Make error handler to message you when a run fails.

What it costs to run

A 3 hour schedule means 8 runs a day, about 240 a month, whether or not any row is ready. On n8n that is 240 executions a month, against 2,500 on Cloud Starter (20 EUR a month billed annually, as of November 2026). On Make, an empty run still uses about 2 credits (the trigger and the search), so about 480 credits a month, and each posted row adds the publish, update and check steps. Make's Free plan gives 1,000 credits a month and has a 15 minute minimum interval, which is no problem for a 3 hour schedule. Blotato Starter is $29 a month billed monthly (see Blotato's site). The API needs a paid plan, and the 7 day trial excludes it, because creating an API key starts paid billing. See the automation cost calculator.

Test plan: run 20 rows, publish only 3

Use a test account for each platform. Fill 20 rows, including 5 on purpose bad ones. Run the gate logic on all 20 with the publish step switched off (in n8n, deactivate the Blotato Publish node and pin its data; in Make, disable the route). Then switch publishing on for only the three good rows marked below. Do not post many real posts to test a queue.

RowsWhat they arePassFail
1 to 5Draft status, good content.The query never returns them.Any of them is picked up.
6 to 13Approved, good content. Publish off.Each is picked up one at a time, one per run.Two rows in one run, or a row picked twice.
14 to 16Approved, one text, one image, one video. Publish ON, test account.Each ends Posted with a URL that opens.Posted with no URL, or a URL that does not open.
17Approved, wrong account_id. Publish ON.Ends Failed, or is blocked, with an error.Posts somewhere.
18Approved, empty media_url on Instagram. Publish ON.Failed with an error.Marked Posted.
19Approved with a time in the future. Publish ON, test account (move it to drafts afterwards in Blotato's web app).Ends Scheduled, not Posted.Ends Posted.
20Edit the text after approval.Row returns to Draft.Old text goes forward.

Keep a log: row, expected outcome, actual outcome, Blotato Logs line, submission ID. If more than one result is a fail, fix before using real accounts.

Who should skip it

If you only want to schedule from a spreadsheet, check whether your scheduler has bulk import: Blotato has no native CSV import, which is why this page needs an automation tool. If you post fewer than 3 times a week, Blotato's own calendar or a free scheduler is easier than a sheet and a workflow. If several people edit the sheet and need comments and sign off, a tool with approval seats fits better. If you will not look at the Failed rows, the queue will quietly fill with them.

How this page was checked

The facts come from Blotato's template 1 page ("Post Everywhere"), its publish-post and get-post references, its limits page and pricing page, n8n's and Make's pricing pages and Zapier's pricing page. Last checked 21 November 2026, refreshed every 90 days. Blur Studio has not run this template or Blotato, so run the 20 row test with the 7 day trial for the web app and a paid month for the API.

How I'd approach this

Day 1: build the sheet with the status dropdown and 5 sample rows. Day 2: connect Blotato with a test account and send one row through by hand. Day 3: build the write back and the status check. Day 4: add the error alert. Day 5: run the 20 row test. Only then connect a real account, and keep a human on the Approved column. If you want help designing the sheet for your business, there is a free AI brainstorm call, and the free AI tools are open to anyone.

Questions people ask

Can I use a Google Sheet as a social media queue?

Yes. Blotato publishes a template that checks a sheet every 3 hours, takes one ready row, publishes it and writes Posted. Add an approval column and a status check, as described above.

How do I stop a row posting before it is approved?

Make the automation pick up only rows with the approval value in the status column, and restrict who can set it. Never use scheduling as a hold, because scheduled posts publish at their time.

Why is my row marked Posted but nothing appears?

A 201 reply only means received. Mark Posted only after the status call returns published. See post stuck on processing.

Does this work in Zapier?

Blotato has no official Zapier app, and the Post Everywhere template is marked n8n and Make only. In Zapier you can build it with Webhooks by Zapier and a Google Sheets lookup. See Blotato versus Zapier.

Why only one row per run?

It keeps the queue slow and safe and stays far below Blotato's limit of 30 create-post requests a minute. You can raise the frequency instead of the batch size.

Can Google Drive hold my videos?

Only with a public link, and Blotato's template notes say files over 60 MB do not work from Drive. Use Amazon S3 storage for large files.

What does it cost?

Blotato Starter is $29 a month billed monthly as of November 2026, plus your automation tool. n8n Cloud Starter is 20 EUR a month billed annually. See Blotato pricing explained.

More in this topic: Social media: automation with n8n, Make and Zapier (27 guides) →

Sources

Ready for the next step?

A free 15-minute AI brainstorm. We find 3 broad areas where AI could help your business.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.
Book a free AI brainstorm call

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…