Deliverd for Slack
Your agent asks.
You answer in Slack.
When an AI agent needs a person to approve what it is about to do, Deliverd sends the request to the people who can say yes, as a direct message with Approve and Decline. The agent gets the answer, and Deliverd keeps the record of who decided what.
Direct messages only · Reads no channels · On every plan, including Free
How it works
One approval, from the agent to Slack and back
- 1
An agent asks
An AI agent your organisation runs asks Deliverd for a person's approval before it acts, over MCP, the REST API, an SDK or the CLI, naming who should decide.
- 2
The approver gets a direct message
Each person named on the request who is a member of a connected workspace gets it as a direct message from the Deliverd app, with what the agent wants to do, Approve, Decline and a link to the full request.
- 3
They decide in Slack
Pressing a button decides the request as that person, under every rule the request carries: only people it names, never the person who raised it, and never twice. The agent gets the answer and carries on.
- 4
Every copy catches up
Once the request is decided, expires or is withdrawn — in Slack, on the web, by email or through the API — every message showing it is rewritten to say how it ended, so nobody presses a button on a settled question.
Install
Add the app to your workspace
- 1
An administrator of your Deliverd organisation presses Add to Slack, here or in Admin → Integrations, and signs in if they are not already.
- 2
Slack asks them which workspace, and to allow the permissions listed below. Installing may need a Slack workspace administrator's approval, depending on your workspace's settings.
- 3
That is the whole setup. Nobody needs to invite the app to a channel: requests go to approvers as direct messages, and each approver is matched to their Deliverd account by the email address they use in Slack.
No Deliverd account yet? Start free, then come back and add the app. The step-by-step guide for administrators is in the integrations guide.
Permissions
What the app may do, and why
4 permissions, each for one job. None of them lets the app read a message, a channel or a file.
| Slack permission | What it is for |
|---|---|
| chat:write | Send an approval request, and update it once it has been decided. |
| im:write | Open a direct message with an approver, so a request reaches only the person it is for. |
| users:read | Look up the member who pressed a button, from Slack's record rather than anything in the message. |
| users:read.email | Find an approver by the email address on their Deliverd account, and confirm that the person pressing a button is them. |
The app also listens for 3 events, which need no permission:
app_home_opened: Show the Home tab, which explains what the app is for, when somebody opens it.app_uninstalled: Delete the workspace's token and everything kept to use it, the moment the app is removed.tokens_revoked: The same deletion, when an administrator revokes the app's token without removing it.
Your data
What the app keeps, and what removing it deletes
The workspace's id and name, and the app's token for it
To send messages in that workspace. The token is encrypted at rest.
Each approver's Slack member id, once they first press a button
To link their Slack account to their Deliverd account, so a press is attributed to the right person.
Where each request was sent: the direct message and the message's timestamp
To rewrite the message once the request is decided.
Remove the app in Slack — in your workspace's app management (Tools & settings → Manage apps), open Deliverd and choose Remove App — and Slack tells us straight away. We delete the workspace's token, the links between its members and their accounts, and the record of which messages showed which request. The decisions people made stay in your organisation's audit trail, because they are its record of who approved what.
The rest is in the privacy policy, the terms and the security overview.
Questions
Slack and Deliverd.
Does the app read our messages or channels?
No. It asks for no permission to read a message, a channel or a file, and it does not join channels. It sends its own messages and answers presses on its own buttons.
What does it cost?
The Slack app is part of Deliverd on every plan, including Free. You pay for Deliverd, not for the app.
What if our organisation requires single sign-on?
Then approvers decide on the web after signing in, and get requests by email rather than in Slack. Slack proves a person's email address, and a sign-in requirement asks for more than that, so Deliverd does not let a Slack button stand in for it.
Can I stop getting requests in Slack?
Yes. Each person can turn Slack off under Settings in Deliverd. Requests addressed to them still arrive by email and in Deliverd, because somebody is waiting on the answer.
Can someone decide a request that was not sent to them?
No. The buttons carry only which request they belong to. Who pressed is taken from Slack's signed request, checked against the people the request names, and refused for anyone else, including whoever raised it.
Can we connect more than one workspace?
Yes. An administrator adds each workspace from Deliverd, and an approver in any of them gets the request there.
Where do I get help?
Write to support@deliverd.dev. A person reads and answers every message.
Support: support@deliverd.dev or the contact form.
Put a person in front of what your agents do.
Add the app, connect one agent, and send its first request to someone who can say yes.