Slack approvals let your team review and approve generated content right inside a channel, with the same interactive buttons Telegram uses.
Why Slack setup is more involved than Telegram
Slack approvals need a real Slack App, not just an Incoming Webhook. Receiving button clicks back requires Slack’s Interactivity feature, which only works from a full app with its own Bot Token – a plain webhook can only send messages one-way, it can’t tell SynaPost when someone clicks Approve.
What you’ll need from Slack
Creating a Slack App for your workspace (from Slack’s own developer settings) gives you two credentials SynaPost needs:
- A Bot Token, so SynaPost can post approval requests into your workspace.
- A Signing Secret, so SynaPost can verify that a button click genuinely came from your Slack workspace before acting on it.
You’ll also need to point Slack’s Interactivity settings at the request URL SynaPost shows you under Settings → Approvals, so button clicks have somewhere to report back to.
Connecting it to SynaPost
Under Settings → Approvals, paste in your Bot Token and Signing Secret, choose which channel approval requests should post to, and enable Slack approvals.
Why the Signing Secret matters
Every interaction Slack sends back is checked against your Signing Secret using HMAC-SHA256 before SynaPost trusts it – the same principle behind Telegram’s own secret webhook path. This stops anyone from forging a fake “Approve” click that didn’t actually come from your Slack workspace.
Using it alongside other channels
Slack works together with Telegram, Email, and the in-dashboard Approval Center – every enabled channel gets the same request at once, and approving in any one of them resolves it everywhere else automatically.