Slack
Connect a Slack workspace, start routines from events, and continue conversations in threads.
Connect Slack to let agents read and write through a workspace bot, and to run routines from mentions, messages and other Slack events. The bot's credential stays on the server; it is never added to an agent's environment.
Connect a workspace
Open Slack on the Connectors page (sidebar) and choose For the workspace, then approve the Slack workspace. The install requests the bot permissions needed by the integration. Each agent's Tools controls which of those capabilities it may use.
Connections and workspace pickers show the Slack workspace name when Slack makes it available. Existing connections pick up the name without reinstalling. If Slack cannot return the name, the workspace ID remains available as a fallback.
| Access | Available tools |
|---|---|
| Read Slack | slack_read reads recent messages or a thread; slack_find finds people and channels; slack_download_file imports an accessible Slack file. |
| Write to Slack | slack_send sends messages, thread replies and files; slack_react adds reactions. |
slack_find searches people by name or email and channels by name; it is not full-text message search. slack_send can post a card instead of text: titles, text, fields, tables, charts and links, plus Standards records the agent points at. Records are filled in with what the person the agent works for may see, and only for objects the agent itself may read, so a private record or an object either of them cannot read never shows in the channel. Everyone in the channel reads the card, and a mention in its text pings nobody. Files sent through slack_send come from the conversation's sandbox or authorized Drive files. Downloaded files go into its sandbox when one is available. Slack access also works with Claude Code and Codex environments.
Start a routine from Slack
Add a Slack trigger in the routine's Triggers section. Select the workspace, event, channels, sender and conditions. Events cover mentions, channel messages, direct messages, reactions and people joining a channel. Same conversation is on by default, so related replies can continue the same work.
Adding a trigger adds Read Slack and Write to Slack to the routine's tools. Grant changes for unattended runs require permission to manage agents. The routine uses its author's Standards permissions; a Slack sender does not acquire that authority.
Selecting a public channel joins the bot when you save. For a private channel, invite it with /invite @Standards, then choose Refresh in the picker. A private channel the bot cannot access cannot be made accessible by reconnecting OAuth. Channel and member choices are read from Slack, so a newly invited channel or renamed person can be refreshed without reinstalling.
See GitHub and Slack triggers for sender filters, conditions and continuation limits.
Continue a conversation from either place
What the agent sends the person with send is posted into a trigger's Slack thread, each message as it is sent, never its narration or reasoning. A routine started from a thread knows the thread is read by everyone in the channel: it answers the person who wrote, and stays silent on a message it skips, such as a greeting. A record it names is linked to Standards. A top-level Slack message sent from an app conversation can also link that thread to the existing conversation. Human replies return there; the posting turn's authority stays pinned. Bot messages are ignored to avoid response loops.
You can continue in Standards and have each message the agent sends you posted to linked Slack threads, once each. slack_send does not post into the conversation's own linked thread: it answers that the agent should use send. Each post is exactly the message the agent sent, with no link appended. This bridge delivers those messages even without a separate Write to Slack grant; that grant controls the agent's explicit write tools. While a turn runs, the thread shows the agent as working. Details are in Agent conversations.
Messages the agent posts to Slack are written in Markdown and converted to Slack's own formatting: bold, strikethrough, links and bullets keep their meaning, a heading becomes a bold line, and a table becomes a code block. Slack has a single emphasis marker, so a Markdown *italic* shows as bold.
Decisions in a Slack thread
In a conversation started from Slack, a decision it raises (a question, an approval, a review or a setup step) appears in its thread as a card, and in the Decisions feed in Standards. A conversation started in Standards asks in the app, even when it has linked a Slack thread. Both show the same decision: the first answer wins and the card updates to show it. A closed card has no buttons and reads who answered, or that the decision expired or was withdrawn.
A card is written in French, whatever the workspace's language, and so are the private notices a click receives. It shows the sender, the kind of decision, its title, the summary, why it is asked and what it unblocks, up to three earlier decisions of the same thread, and links to Standards. A question with one choice has one button per option. A free-text answer or several single-choice questions open a form from the card's Répondre (reply) button. A question with multiple choice has no buttons or form in Slack, because Slack forms have no multi-select: the card points to Ouvrir dans Standards (open in Standards), where it is answered. Passer (skip) sits beside the buttons or the form. An approval shows the tool's name and its measured impact, never its arguments, and offers Approuver or Refuser (approve, refuse), the refusal with an optional reason. A review offers Valider or Demander des changements (approve, request changes). A setup step opens Standards with Connecter dans Standards, then Continuer or Passer (continue, skip).
Because everyone in the channel reads the card, it never shows attachments, tool arguments or the values of a record draft. Ouvrir dans Standards reaches them for the people who may see them.
Who can answer
Only the person the decision is asked of can answer, as in the app. In a conversation started from Slack, a question goes to the person whose message the agent is answering. Their Slack account counts as their Standards user when it belongs to the connected workspace, is not an external guest, and has a confirmed email equal to their Standards email. Anyone else who clicks is told, privately, who may answer, to link their account with the same email, or that the decision is already settled.
A reply in the thread works too, from a Slack account whose confirmed email is a Standards user's: it answers the question addressed to that person, as them. Someone who may not open the conversation in Standards answers only the questions addressed to them. A reply from anyone else, or from an account linked to no one, reaches the agent as a message but answers nothing. An approval is never settled by a reply in the thread, only with its card's Approuver or Refuser, or in Standards.
A decision answered on its card or in its form reads Settled from Slack in the app, once its line is opened in a later decision's history of the same thread. A text reply goes through the conversation and carries no such mark.
Limits and reconnection
Slack sets the rate limits and access rules for each API method. Recent-history reads use pages of up to 15 messages and may return a cursor for more. Some app distributions cannot read all public or private channel-thread replies with a bot token. A provider refusal is surfaced instead of silently using a person's token. Rate-limited mirror deliveries wait for Slack's retry delay; delivery is not necessarily immediate.
Uninstalling the App or revoking its bot token disconnects the installation while retaining its grants and triggers. Revoking only a Slack user token does not disconnect this bot integration. Reconnect from integrations to restore access. Deleting the connection in Standards removes dependent grants and triggers. Existing conversation history follows its normal visibility rules.
Next steps
Configure agents and routines, or connect GitHub for repository work.