An n8n Slack approval gate that genuinely pauses before a draft posts

Most "AI content factory" templates draft a post and publish it straight away. This one stops and waits for a human tap on Approve or Reject, wired with n8n's own Wait node, not a placeholder step you have to build.

$39

Buy on Gumroad

The problem

Most free content-automation templates draft a post and publish it straight away. No human ever looks at it before it goes out. That is fine until the draft is wrong, off brand, or just bad, and now it is live.

What this workflow does

Watches a feed and drafts a social post from each new item.
Posts the draft to Slack with two links built into the message: Approve and Reject.
Genuinely pauses. The workflow uses n8n's own Wait node with a webhook resume. Nothing after this point runs until someone taps a link.
Resumes on the tap and branches: approved drafts continue to your publish step, rejected drafts stop.

Before and after

A placeholder approval step

A NoOp node labeled "add your approval step here" that you have to build yourself.
Slack app review, because the template uses Block Kit interactive buttons.
No proof it was ever run, just JSON that looks right.

With this workflow

The pause, the Slack message, and the resume are real, wired logic, tested end to end on a live n8n instance.
No Slack app review: the Approve/Reject links are plain URLs that hit your resume webhook directly, a two-minute bot token.
A setup guide and troubleshooting table travel with it, so the next person does not start from zero.

What you get

The workflow JSON: feed trigger, draft formatter, Slack approval request, wait-for-decision, approve/reject branch, and a publish-step slot for you to connect.
A setup guide covering the Slack bot token, public webhook reachability, and a troubleshooting table.
A test checklist showing exactly what was run against a live n8n instance, and what only your own Slack workspace can confirm.

Who it's for

Ops people and small agencies who already run a content pipeline and got burned by, or are wary of, letting it publish unattended. If you want a human to see the draft before it goes out and are tired of building the approval step yourself, this is that step, already wired.

FAQ

Does the resume link need a public n8n instance?

Yes. Slack has to be able to reach your resume webhook when you tap Approve or Reject, so your n8n instance needs a public URL, a reverse proxy, or a tunnel. A purely localhost instance cannot receive the click. Covered in the setup guide.

Do I need to build a Slack app with Interactivity endpoints?

No. The Approve/Reject links are plain URLs, not Block Kit interactive elements, so a bot token with chat:write is the whole Slack-side setup.

What was actually tested, and what wasn't?

The pause, the Slack message send, and the branch logic were confirmed running on a live n8n instance. Resuming from a live Slack click is standard n8n webhook behavior and is the one step a one-shot automated test cannot itself trigger, so treat that as a two-minute check on your own first run.

What n8n version was this tested on?

n8n 2.35.5. The pinned version and update policy ship in the setup guide.