What do you need?
- A Slack app you can install in your workspace, with an incoming webhook and interactivity turned on (or just an approver's email address)
- A nofeb key with the policy:manage scope
- An inbox whose sends are held: send_with_approval, or a tier, list or cap that holds
Steps
-
1. Prepare the Slack app
In Slack's app settings, add an incoming webhook for the channel where approvals should appear and copy its URL. Under Basic Information, copy the app's signing secret. nofeb posts through the webhook and uses the secret to prove that each button click came from Slack and not from someone replaying a request.
-
2. Register the approver
Give it a scope (organization, pod or inbox): it receives the sends held in that scope and can decide only those. List the Slack user ids allowed to decide if the channel holds more people than your approvers.
A Slack approver for one inbox curl -X POST https://api.nofeb.com/v1/approvers -H "Authorization: Bearer $NOFEB_ADMIN_KEY" -H 'content-type: application/json' \ -d '{"kind": "slack", "scope": "inbox", "inbox_id": "inb_…", "webhook_url": "https://hooks.slack.com/services/…", "signing_secret": "…", "allowed_user_ids": ["U04ABCDEF"]}' { "id": "apv_…", "kind": "slack", "interactivity_url": "https://api.nofeb.com/v1/approvals/slack/apv_…", … } -
3. Point Slack's interactivity at nofeb
Paste the returned
interactivity_urlas the Request URL under Interactivity & Shortcuts. Each click is checked against the signing secret with a five-minute replay window, and the message is updated in place to show who decided and what the send became. -
4. Or approve by email
An email approver receives a link to a page that shows the held send with Approve and Reject buttons. Opening the page never decides; only pressing a button does, so the security scanners that fetch every link in incoming mail cannot approve anything. A link decides once and expires after
link_ttl_hours(72 by default, at most 168).An email approver for a pod curl -X POST https://api.nofeb.com/v1/approvers -H "Authorization: Bearer $NOFEB_ADMIN_KEY" -H 'content-type: application/json' \ -d '{"kind": "email", "email": "lead@example.com", "link_ttl_hours": 24, "scope": "pod", "pod_id": "pod_…"}' -
5. Watch the outcome
Approved mail goes out exactly as held, and approval.decided is emitted to your webhooks and the event feed. The audit log records the decision with an actor of kind slack or email_link, so you can tell a button click from an API call.
What does the approver see?
The Slack message has a header, the sending inbox, the recipients, the subject and a preview of the text, and a line saying why the send was held: the inbox's tier, a recipient outside the allowlist, an exhausted cap, a thread a person has taken over, or the questions a send_when_confident check failed. Reject asks for confirmation first, because a rejected send is cancelled.
The same reasons are on the approval.requested event and in the approval queue at GET /v1/sends?status=held, so a reviewer working from the API or the webmail sees exactly what the Slack channel sees.
Why not let the agent post to Slack itself?
An approval the agent can reach is an approval the agent can fake. Here the agent's key holds message:send and nothing more; the approver is configured with a key that holds policy:manage, and decisions arrive at nofeb signed by Slack or carried by a link only the approver received. Removing the approver makes its outstanding links stop working at once.
Frequently asked questions
Can I approve AI agent emails in Slack?
Yes. Register a Slack approver with your app's incoming webhook and signing secret, set the interactivity URL, and every held send in its scope arrives with Approve and Reject buttons.
Are email approval links safe from link scanners?
Yes. Viewing the page changes nothing; only a button press, sent as a form post, decides. The link is signed, single use and expires.
What happens if nobody answers?
Nothing is sent. The send stays in the approval queue until someone decides it, from Slack, a link, the API or the webmail.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Approvals in Slack and by email link | Approve or reject a held send from a Slack message with Approve and Reject buttons, or from a signed, single-use, expiring link in an email. Slack requests are verified with your app's signing secret and can be limited to named people; the email link decides only on an explicit click, so link scanners cannot approve. | Shipped |
| Human approval of held sends | A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. | Shipped |
| Append-only audit log | Every change made through the API, MCP or the console, and every hold, denial, rejection and approval the server makes on its own, recorded with the actor, key, operation, target, outcome and request id. Query it with filters and cursors, or export it as JSON Lines. | Shipped |
| Autonomy tiers enforced by the server | Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. | Shipped |
| Recipient and sender allowlists and blocklists | Lists of addresses, domains or wildcards per organization, pod or inbox: who an agent may write to, and whose mail it reads. A blocked recipient is refused on every autonomy tier, a blocked sender's mail is rejected or quarantined, and you choose whether a send outside the allowlist is held for approval or refused. A check call predicts what a send or an inbound message would meet before it happens. | Shipped |
| Per-agent rate and recipient caps | Limits per inbox and per API key on sends per hour and per day, distinct recipients per day, recipients per message and new recipients per day, checked and charged in one step so concurrent sends cannot overshoot. A usage call shows the budget left, and you choose whether an exhausted cap holds a send for approval or refuses it. | Shipped |