Agents in Slack

A published agent can live where the team already works: Slack. Conversations run in threads, and tool approvals arrive as interactive cards.

How it works

• The agent gets per-agent Slack settings (which workspace, channels, and users can reach it) configured from the agent’s settings in the app.
• A conversation started from Slack is a normal Live conversation — latest published version, live workflow releases, the owner’s connections — with Slack as its source. It shows up in the agent’s conversation list like any other.
• Approval-gated tools post approval cards. Per-tool Slack approval routes can also send a specific tool’s approvals to a chosen channel — useful when the person who approves isn’t the person chatting.

The one rule that surprises people

A Slack-bound conversation resolves its approvals only from the Slack thread. The web app shows those pending approvals read-only, and the server rejects app-side responses — by design, so the approval happens in front of the same audience as the conversation. If a card seems stuck, answer it in Slack, not the app.

Approval cards follow the same lifecycle as all approvals (tools and approvals): they block the turn, and they expire when the session ends or the agent is published — an expired card in Slack is a publish or timeout, not a bug.

Example prompts

Set up this agent for our #support channel, route the delete-record tool's approvals to #support-leads, and walk me through one gated call end to end.