Airtable or Notion to social posts: when a database beats a sheet, and how to stop duplicate runs

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

Short answer: A database such as Airtable (a spreadsheet-style database with linked records and views) or Notion (a notes and database workspace) beats a plain sheet when your posts belong to campaigns, clients or approvals. Add an Approved checkbox and a Do not post flag, let the automation pick up only rows that pass both, and write a status before and after every publish so a second run never posts the same row twice. Tools like Blotato, a software subscription that schedules and publishes social media posts, do not remove duplicates for you.

Ranjit Bhinge

You keep your content plan in Airtable or Notion and you want it to publish by itself, without a row ever going out twice or going out before someone said yes.

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.

Most guides on this topic show one trigger and one publish step and stop. That works on the first day. It breaks on the day an automation runs twice, a network call times out after the post was created, or someone types a half-finished caption into a row that happens to match your filter. This page gives a field layout, a status flow, a duplicate-run guard and a 20-row test you can run before you trust it. The publishing side uses Blotato's API (the door other software uses to talk to Blotato). Everything below is a build plan based on the vendors' own documentation, checked on 21 November 2026.

Prices are in US dollars as of November 2026. Blotato's Starter plan is $29 a month, billed monthly, per its pricing page. Its 7 day free trial does not include the API, and Blotato says creating an API key during the trial ends the trial and starts the paid plan.

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

When a database beats a sheet

A Google Sheet is the simplest queue, and Blotato's own first template is built on one (see the nine templates explained). Stay on a sheet if you post one brand, one person edits, and the whole plan is one flat list.

Move to Airtable or Notion when at least two of these are true:

  • Posts belong to something else: a campaign, a client, a product launch or a blog article.
  • More than one person touches a post, and you need views such as "waiting for my review".
  • You need a field that only accepts set choices (a status list, a platform list), so a typo cannot slip into an automation filter.

The price of that power is more moving parts and your own limits to respect. Airtable's API allows 5 requests per second per base, and if you go over you get a 429 error (the standard "too many requests" reply) and must wait 30 seconds, per Airtable's rate limit page. Notion's API averages 3 requests per second per connection on most plans and 10 per second on Business and Enterprise workspaces, and it sends a Retry-After header telling you how long to wait, per Notion's request limits page. A one-row-per-run posting flow never comes close to these limits. A flow that updates 200 rows in a loop can.

The layout: fields that make the automation safe

Build one table (Airtable) or one database (Notion) called Posts. For a first build, use one row per post per platform.

FieldTypeWhy it exists
Content IDShort text, uniqueYour own stable key. Never reused.
StatusSingle selectDraft, Needs review, Approved, Submitting, Submitted, Posted, Failed
ApprovedCheckboxA person ticks it. The automation never does.
Do not postCheckboxA kill switch per row. Wins over everything.
PlatformSingle selectMust match Blotato's platform names: twitter, linkedin, facebook, instagram, pinterest, tiktok, threads, bluesky, youtube, slack, discord.
Account IDShort textThe Blotato account ID for the destination, copied from the account list.
Page, board or channel IDShort textNeeded for Facebook Pages, Pinterest boards, Slack and Discord channels.
TextLong textThe caption.
Media URLURLA public link. Blotato accepts any publicly reachable URL, with no upload step.
Publish time (UTC)Date with timeOptional. Blank means "next run".
Run IDShort textWritten by the automation before it publishes.
Submission IDShort textBlotato's postSubmissionId, saved straight after the create call.
Public URLURLFilled after Blotato reports published.
Error messageLong textFilled when a post fails.

Two choices matter more than the rest. First, Approved is a checkbox that only a human changes, and the Status "Approved" is also set by a person, never by the AI step. Second, Do not post is separate from Status. A status can be changed by accident while a flag stays where you put it.

The automation, step by step

The steps below use n8n, a workflow tool that joins apps on a visual canvas, with Blotato's official n8n node. The same logic works in Make (a similar visual workflow tool) or any tool that can read rows and call an API. See the Blotato n8n node setup guide for the install and credential steps, and the Make guide if you prefer Make.

  1. Trigger on a schedule, not on every edit. A Schedule Trigger every 3 hours matches Blotato's own sheet template, which checks every 3 hours and handles one row per run. A change trigger fires on every keystroke-level edit and invites double runs.
  2. Read only rows that pass the gate. Limit the read to one row. In Airtable, a filter formula such as AND({Approved}, NOT({Do not post}), {Status} = 'Approved', {Submission ID} = '') does it. In Notion, a database filter with the same four conditions does it. The empty Submission ID condition is your first duplicate guard.
  3. Claim the row. Immediately write Status = Submitting and a Run ID (the n8n execution ID is fine) back to the row. Do this before any call to Blotato. A second overlapping run now cannot select the row, because its Status is no longer Approved.
  4. Publish. Use the Blotato node's Post, Publish operation (or an HTTP Request node to POST https://backend.blotato.com/v2/posts with the header blotato-api-key). If you want a set time, the scheduled time is a root-level field next to the post, not inside it, or the post goes out at once. The body looks like this:
    {
      "post": {
        "accountId": "ACCOUNT_ID_FROM_ROW",
        "content": {
          "text": "CAPTION_FROM_ROW",
          "mediaUrls": ["https://example.com/image-from-row.jpg"],
          "platform": "twitter"
        },
        "target": { "targetType": "twitter" }
      },
      "scheduledTime": "2026-12-01T14:00:00Z"
    }
    The platform value in content must equal the target type. A 201 reply returns a postSubmissionId.
  5. Save the submission ID first. Write the postSubmissionId to the row and set Status = Submitted before you do anything else.
  6. Check the result. Wait at least 10 seconds, then call Post, Get (GET /v2/posts/{id}). Blotato reports in-progress, published, scheduled or failed. Write Posted plus the public URL on published. Write Failed plus the error message on failed. If you scheduled a future time, the honest status is "scheduled", not Posted, so add a Scheduled status or leave it at Submitted until the time passes.

The Approved field and the Do not post flag

Blotato has no draft state for outside agents and no dry run: a create call either publishes or schedules, and a scheduled post will publish at its time. That means your database is the only place a hold can live. Treat it that way.

  • Approved is the entry ticket. A row without it is invisible to the automation.
  • Do not post is the brake. Use it for a post that is paused, legally unclear or waiting on a fact check. Put it in the filter and also in a red view so it stays visible.
  • Edits cancel approval. Add a "Last edited" field and an "Approved at" field. If Last edited is later than Approved at, treat the row as unapproved. In Airtable a formula field can show this. In Notion a formula property can do the same.
  • Who approves. Add an Approved by field. Blotato has no approval feature, as this page on Blotato approvals explains.

How to stop a duplicate run

Blotato documents that it does not guarantee duplicate protection when you retry, change a payload or change the time, and it has no idempotency header (a unique key you send so a repeat call is ignored). So the guard has to be yours. Use four layers.

  1. Claim before you call. Status = Submitting before the publish step (step 3 above).
  2. Filter on empty Submission ID. A row that has a submission ID is never selected again.
  3. One row per run, one active run. In n8n, keep the workflow's concurrency low and the read limit at 1. In Make, keep the scenario to one run at a time.
  4. Treat Submitting as an alarm. If a row sits at Submitting for more than 30 minutes, the create call may have succeeded without your workflow hearing back. Do not reset it and retry. Open Blotato's Posts list or call List Posts (GET /v2/posts, filters for status and platform, 60 requests a minute) and look for the caption first. Only if it is not there, set the row back to Approved.

Blotato's rule for an uncertain write is the same: after a timeout with no ID, look at existing work before you create again. Fix a failed post's error before you resubmit it, because an unchanged retry usually fails the same way. For more on retries see the rate limits and retries guide.

Errors and what to write in the row

What you seeMeaningWhat the row should say
401 from BlotatoAPI key missing or copied without the trailing equals signStop the run. Do not mark rows Failed.
422A field is wrong (for example a missing page ID)Failed, with the field name in Error message.
429Too many requests; create post allows 30 requests a minuteLeave the row at Approved, wait, run later.
Network error after createUnknown outcomeLeave at Submitting and alert a human.
Status failed on GetBlotato or the platform rejected itFailed, with Blotato's error message.

Set an error workflow in n8n (a second workflow that starts with the Error Trigger node) to send you the failed row's Content ID. For the full list of Blotato and n8n codes see this error codes page.

Limits to know

Blotato's Starter plan queues up to 200 scheduled posts (posts published at once do not count) and connects 20 accounts, as of November 2026. Per-platform daily caps are separate and change, see Blotato's posting limits page. n8n Cloud Starter is 20 euros a month billed annually for 2,500 workflow runs, and one run every 3 hours is about 240 a month.

A worked example with made-up numbers

You plan 20 posts for one campaign, each going to 3 platforms, so 60 platform posts. You run one row per 3-hour run, 8 runs a day.

  • If each row is one platform post, 60 rows take 60 runs, which is 7.5 days.
  • If each row fans out to 3 platforms in one run, 20 rows take 20 runs, which is 2.5 days, and each run makes 3 create calls.
  • If you instead schedule every post for its future time, the 60 posts sit in Blotato's queue, which is 60 of your 200 on Starter, and the flow only needs to run as fast as you approve.

Let only one place control time: your database or Blotato's calendar. Two places is how duplicates start.

A 20-row test plan with pass and fail criteria

Run this against a test destination, not your live accounts. Blotato's 7 day trial covers the web app but not the API, so you need a paid plan to run it end to end.

  1. Point the rows at a private Slack channel (Slack is a team chat tool, and one of Blotato's 11 supported destinations) so nothing reaches an audience. Create 20 rows. Make 14 good, and add 6 deliberate traps: one with Do not post ticked, one with Approved unticked, one with a bad account ID, one with a missing channel ID, one with a media URL that returns an error, one with a caption far over the length limit.
  2. Run the flow until the queue is empty. Do not touch rows by hand.
  3. Open Blotato's Logs and Posts pages and compare with your table.
CheckPassFail
Good rows14 appear once each, 14 Public URLs savedAny row posted twice or missing
Do not post and unapprovedZero postsAny post at all
Bad account, missing channel ID, bad media, long textFour rows Failed with a readable errorAny marked Posted
OverlapStart the flow twice within a minute: still no duplicatesAny duplicate
TimeoutCut the network during a publish: row stays Submitting and alerts youRow reset and re-posted

Who should skip this

Skip the database build if you post fewer than 10 times a week to one or two accounts. A scheduler's own calendar is faster, and a two-hour weekly routine will do. If your priority is client approval with no build at all, look at schedulers that ship approvals, such as the ones compared in this alternatives guide.

How this page was checked

The Blotato facts come from Blotato's pricing page, its help centre pages on publishing, listing posts, rate limits and the Post Everywhere template, and its n8n node page. The Airtable and Notion limits come from their own developer pages. All were last checked on 21 November 2026 and are refreshed every 90 days. Blur Studio has not run Blotato, Airtable or Notion with this workflow, so test with the 20-row plan above before you rely on it.

How I'd approach this

I would start with a plain table, the four-field gate (Approved, Do not post, Status, Submission ID) and one platform. If a sheet does the job, I would stop there and not move to a database at all. If you want Blotato for the publishing side, you can try it through this Blotato link and compare it with the options in the API scheduler comparison. Week one: build the table on day one, wire the flow to one test account on day two, run the 20-row test on day three, fix what failed on day four, and go live with one row a day on day five. Add platforms only after a full week with no duplicates. If you would like to talk it through, the free AI tools at /free and the free AI brainstorm call at /ai-strategy are open to you. The Blotato site also lists what each plan includes, so check it before you pay.

Questions people ask

Is Airtable or Notion better for a social media content calendar?

Airtable is stronger when you want strict fields, linked records and a clear API for reading and updating rows. Notion is stronger when the posts live next to notes and documents. For automation, the strict fields usually make Airtable the easier one, but either works with the same four-field gate.

Can Blotato read my Airtable or Notion directly?

Blotato's documentation does not describe a direct Airtable or Notion connection. You connect them through an automation tool such as n8n or Make, which reads your rows and then calls Blotato's API. See the n8n node guide.

Does Blotato stop duplicate posts if my automation runs twice?

No. Blotato says its internal duplicate detection is not a guarantee when you retry or change a payload, and it has no idempotency key. Use your own status and submission ID fields as described above.

What is the Do not post flag for?

It is a per-row brake that the automation filter always checks. Use it when a post is paused for a fact check, a legal question or a change of plan. It is separate from Status so an accidental status change cannot override it.

How often should the automation run?

Blotato's own Google Sheet template checks every 3 hours and publishes one row per run. That pace keeps you far under the 30 create-post requests a minute limit and under both Airtable's and Notion's limits.

Do I need a paid Blotato plan?

Yes for this build. The API is on every paid plan, from $29 a month billed monthly on Starter as of November 2026, and the free trial excludes it. Generating an API key during the trial starts the paid plan.

What should the row say if a post is only scheduled?

Not Posted. A scheduled post has not published yet, and a queued post still publishes at its time. Use a Scheduled status, or keep Submitted until Blotato reports published.

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…