How to build a content approval step in n8n or Make for Blotato (one that fails safe)

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

Short answer: Blotato, a software subscription that writes, schedules and publishes social media posts, has no approval step for outside automations, so you build the gate in your automation tool. In n8n (a visual workflow tool) send the draft to Slack, wait for a click, and publish only on an explicit approve. Set a wait limit so that silence, a reject or an error all end in no post. In Make (a similar tool) use a second scenario that the approve link triggers.

Ranjit Bhinge

You want an AI or an automation to draft your posts, but nothing should reach your feed until a person has seen the exact text and 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 "human in the loop" guides tell you to add a review step and stop. The part that matters is what happens when the human does not answer. If silence leads to a post, you do not have an approval step, you have a delay. This page builds a gate where every path except a clear yes ends with nothing published, shows the Slack and email patterns, and gives you a test that proves the timeout works. Treat it as a plan to test.

Prices are in US dollars as of November 2026 unless a line says euros. Blotato's pricing page shows Starter at $29 a month, billed monthly. Its API (the way other tools talk to it) needs a paid plan, and the 7 day free trial excludes it.

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

Why you must build the approval yourself

Blotato's documentation is plain about this. A create-post call from an outside agent, whether through the REST API, the MCP connection (MCP is the standard that lets AI assistants use tools) or an automation node, publishes straight away unless it carries a scheduled time. There is no draft-save call, no dry run and no "approve" tool. Scheduling is not a hold either: a scheduled post publishes at its time. Blotato's in-app Post editor can leave drafts for a person, but those are not reachable by an outside workflow. The documented advice is to build the gate in your own automation: generate, send to a reviewer, wait for an approval signal, then publish. The page Does Blotato have approval workflows covers the same point from the buyer's side.

Do not use scheduling as a pretend draft. If you schedule a post "to be safe", the post still goes out when the time arrives.

Five design rules for a gate that fails safe

  1. Only an explicit approve publishes. Build the publish step on the approve branch alone. Every other outcome (reject, no answer, a malformed answer, an error) goes to a stop-and-log branch.
  2. The reviewer sees the real payload. Compose the review message from the exact text, media link, platform, account and time that will be sent to Blotato, not from the AI's summary of them.
  3. An edit voids the approval. If the text changes after approval, approve again. Store a short fingerprint of the final text with the approval, and compare it at publish time.
  4. Silence means no. Set a wait limit and make the timeout branch end the run.
  5. Log everything. Draft ID, approver, answer, time and Blotato's submission ID.

Pattern A: n8n with Slack Send and Wait

n8n's Slack node has an operation called Send and Wait for Response. It posts a message to a channel or person, pauses the run, and resumes when the approver responds in Slack. Install and credential steps for the Blotato node are in the n8n node setup guide.

  1. Trigger and draft. A schedule, a sheet row or an AI step produces the final text, media link, platform and account ID.
  2. Fingerprint. Add a step that makes a short hash of the final text (n8n has a Crypto node for this, check its current options) and keep it in the data.
  3. Send and Wait. Slack node, Send and Wait for Response, to a private channel. Build the message from the final fields: "Post to X account NAME at 2026-12-02 09:00 UTC: TEXT. Media: LINK. Approve or reject." Set Response Type to Approval. Turn on Capture Who Responded and Restrict Who Can Approve in the Advanced Interactivity settings, or anyone who can see the message can answer. n8n's Slack approvals page also lists what the Slack app needs (Interactivity switched on, and your n8n address reachable from Slack over public HTTPS).
  4. Time limit. Check the node's options for a limit on how long it waits. If your version has none, use pattern B, where the Wait node has a documented Limit Wait Time.
  5. Decision. An If node checks that the answer equals approve. True goes to publish. False goes to the log-and-stop branch. Because only the true branch publishes, a timeout cannot post, so long as you confirm in the test below how your version behaves when it times out.
  6. Re-check the fingerprint. Before publish, hash the text again and compare. If it differs, stop.
  7. Publish. Blotato node, Post, Publish, or an HTTP Request node.
  8. Verify. Save the submission ID, wait at least 10 seconds, run Post, Get, and treat only published as done.

The publish body, if you use an HTTP Request node to POST https://backend.blotato.com/v2/posts with the header blotato-api-key, looks like this. Keep the key in an n8n credential, never in the text of the workflow:

{
  "post": {
    "accountId": "ACCOUNT_ID",
    "content": {
      "text": "APPROVED_TEXT",
      "mediaUrls": [],
      "platform": "linkedin"
    },
    "target": { "targetType": "linkedin" }
  },
  "scheduledTime": "2026-12-02T09:00:00Z"
}

The scheduled time sits beside the post, not inside it. Inside it, it is ignored and the post goes out at once.

Pattern B: n8n Wait node with a link or a form

Use this when you want email, a chat app other than Slack, or an exact timeout.

  1. Send the reviewer a message by email or any chat node. Include two links that call the workflow's resume address, one that sends approve and one that sends reject. n8n documents the resume address for the Wait node as the $execution.resumeUrl variable, generated for each run.
  2. Add a Wait node set to resume On Webhook Call (or On Form Submitted), and turn on Limit Wait Time, for example 24 hours. When the limit passes, n8n resumes the run on its own, so the run carries on without an answer. That is why the next steps must test for an explicit approve.
  3. The webhook can be restricted by IP allowlist, and n8n turns others away. Use it if your approvers are on a known network.
  4. After the Wait node, an If node tests for approve. Anything else, including a timeout with no answer, goes to Stop and Error with a message that says "not approved".

The Stop And Error node forces a failed run on purpose, which then triggers any error workflow you set, so you hear about the unapproved post in the same place you hear about failures.

Pattern C: Make with two scenarios

Make does not document a built-in approval module, so this is a common pattern rather than a built-in feature. Use two scenarios.

  1. Scenario 1 (draft and ask). Trigger, AI step, then a Slack or email module that sends the exact text with an Approve link and a Reject link. Each link points at the webhook address of scenario 2 (Make's Custom webhook), with the draft ID in the link. Write the draft, its fingerprint and the status Pending to a data store or sheet. Then end.
  2. Scenario 2 (publish on approve). Starts from the Custom webhook. It looks up the draft by ID, checks that the status is still Pending and the fingerprint matches, then calls the Blotato Create a Post module (Blotato's Make app has actions only, with no triggers), then sets the status to Published.
  3. The timeout comes free. Nobody clicks, scenario 2 never runs, nothing posts. Add a small scheduled scenario that finds Pending drafts older than 24 hours, marks them Expired and tells you.

Make bills in credits, where most module actions use 1. Make's error handler modules and the Router cost nothing. On monthly billing at 10,000 credits a month, Make Core was $10.59 a month and Pro $18.82, as of November 2026 on Make's pricing page. This flow costs a handful of credits per post, so volume is rarely the issue. Check Blotato's modules in the install before you build, because Make's listing for the Blotato app carries a notice that it is generated from Blotato's documentation. See the Make modules guide.

A note on Zapier

Blotato has no official Zapier app, and Blotato's own templates are not offered for Zapier. Zapier has a Human in the Loop tool with a Request Approval action, listed as in beta on its pricing comparison, and you would call Blotato with its Webhooks by Zapier action. That route is covered in the Zapier recipes page and the Blotato and Zapier comparison.

The log: one row per approval

A sheet or table with these columns is enough. Add one row when the review message is sent and update it on every outcome.

ColumnExample (made up)
Draft IDd-0142
Platform and accountlinkedin, Company Page
Text fingerprintfirst 8 characters of the hash
Sent for review at2026-12-01 09:00 UTC
Answerapprove, reject, timeout
Answered by and atsam, 2026-12-01 09:22 UTC
Blotato submission IDfrom the create reply
Final statuspublished, failed, expired

If the create call fails with no ID, do not retry blindly. Check Blotato's Posts and Logs first. Blotato has no idempotency key (a unique key that makes a repeat call harmless), so your log is the only protection against a double post.

Timeouts: how long to wait

  • Same-day posts: my suggestion is 2 to 4 hours. Longer, and the content is stale.
  • Next-day posts: 24 hours.
  • Weekly batch: 48 hours, and review the batch in one sitting.

n8n's plans limit how long a run can stay active, so a very long wait may hit a duration ceiling. n8n's pricing page lists a maximum execution time per plan (5 minutes on Cloud Starter as shown there). A paused wait is handled differently from running steps, but check how your plan treats long waits before you rely on a 24 hour pause. A safer pattern for long waits is the Make style: store the draft, end the run, and start a new run when the answer arrives.

When an approval-built tool is simpler

If approvals are the main job and not an add-on, a scheduler that has them built in saves you the build. Rella, a social media scheduler with client approvals, lists on its pricing page, as of November 2026, Pro at $24 a month, Premium at $48 and Premium Plus at $64 per seat, all billed annually, with a 14 day free trial. Its Premium tier adds one-click approvals and one assigned approver, and Premium Plus adds unlimited approvers. Rella says reviewers and clients do not need a seat. Its Monthly toggle shows $30, $59 and $79 per seat. Rella cannot do what Blotato's API-first design does for AI agents, and Blotato's flat price per account is cheaper at many accounts. See the three-way agency comparison and the guide to client approval without a built-in feature.

A test plan with pass and fail criteria

Use a throwaway social account. Set the timeout to 10 minutes for the test.

TestPassFail
Click approveOne post, one public URL, log row completeNo post, or two posts
Click rejectNo post, log says rejectAny post
Do nothing for the full timeoutNo post, log says timeout, you are toldAny post
Click approve twiceOne postTwo posts
Edit the text after sendingPublish stops on fingerprint mismatchEdited text posts
Send a wrong account IDFailed with Blotato's error, log says failedMarked published
Click an old approve link a day laterNothing happensPost goes out

The timeout test is the one that matters. Record what your n8n version does when the wait ends, because the output differs from a real answer. That is why the If node tests for an explicit approve and nothing else.

Who should skip this build

Skip it if you post by hand-written text only and use Blotato's calendar yourself: you are the approver already. Skip it if clients must approve and are not technical: a tool with built-in review links will serve them better. And skip any automation that writes about regulated claims such as health or finance without a human reading every post.

How this page was checked

The Blotato facts come from its pricing page and help centre pages on publishing, scheduling and agent workflows. The n8n facts come from n8n's documentation for the Wait node, the Slack node and error handling, and its pricing page. Make facts come from its pricing page. Rella's prices come from its pricing page. All were last checked on 21 November 2026 and are refreshed every 90 days. Blur Studio has not run Blotato or built this flow, so test with a throwaway account and Blotato's 7 day trial for the web app before relying on it.

How I'd approach this

I would build pattern A or B in n8n first, with the timeout test as the first thing I run, before the real publish step exists. If you are new to the tool, Blotato's site lists its plans and the trial. Week one: on day one draw the five design rules on paper, on day two build the Slack message with the real fields, on day three add the wait limit and the If node, on day four run all seven tests, and on day five send one real post to a test account. Only point it at your real accounts when the timeout test passes three times in a row. I would also glance at the free tools at /free, and the free AI brainstorm call at /ai-strategy is there if you want to talk it through. If the build feels heavy, compare Blotato with a scheduler that has approvals built in.

Questions people ask

Does Blotato have an approval step?

Not for outside automations. A create-post call publishes or schedules, and there is no draft save or dry run for the API or MCP. Build the gate in n8n or Make. See Does Blotato have approval workflows.

What happens if nobody clicks approve?

With the design above, nothing posts. Only an explicit approve reaches the publish step, and a timeout, a reject or an error all go to a log-and-stop branch. Run the timeout test to confirm your version does this.

Can I use scheduling as a safe draft?

No. A scheduled post publishes at its time. It is a queue, not a hold. Use your own status field and gate instead.

Can the AI approve its own posts?

It should not. Keep the approval answer on a channel the AI step cannot write to, and never let post text choose who approves or which account is used.

Is there an approval option in Zapier?

Zapier lists a Human in the Loop tool with a Request Approval action, shown as beta on its pricing comparison. Blotato has no Zapier app, so you would call Blotato with Webhooks by Zapier. See the Zapier recipes.

How long should the wait limit be?

2 to 4 hours for same-day posts, 24 hours for next-day posts and 48 hours for a weekly batch. Shorter is safer, because stale approvals post stale content.

Is there a scheduler with approvals built in?

Yes. Rella lists one-click approvals from its Premium tier, at $48 per seat billed annually as of November 2026. Compare it in this three-way comparison.

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…