Production-ready slack, on day one.
The boring infrastructure — signing, retries, suppressions, webhook verification, audit — is done. Your code is one POST.
- Slack OAuth installation flow
- Send text to channel IDs or user IDs
- Optional Block Kit mode configured per connection
- Inbound Slack events streamed into Logs
- Provider failures classified for safe retries
- Per-recipient suppression handling
- Agent-tagged sends visible in dashboard
Senddio Slack vs. building with the Slack SDK
What changes once you ship Slack on Senddio.
Slack — FAQ
Go to Channels, then Slack, then Install in your Senddio dashboard. You are redirected to Slack's standard authorisation screen, which asks for the minimum permissions Senddio needs to read channel names and post messages. Tokens are encrypted at rest and only shown as masked secrets.
Yes, after the Senddio bot is invited to the private channel — that is a Slack rule, not a Senddio limitation. Public channels work the moment your workspace is connected.
A Slack connection can enable Block Kit mode. In that mode, body must contain a JSON-encoded blocks array; the public request still uses the body field rather than a top-level blocks field.
Slack's Events API delivers events to a Senddio webhook. Senddio verifies the signing secret and stores supported inbound messages in Logs for your application to consume.
Yes, and it is one of the most popular patterns Senddio sees. Give the agent its own key, restrict it to Slack, and it can post the same way a human would. Every send is labelled with the agent name so you can audit AI traffic separately.