Connect an agent to Slack

Connect Slack when an agent should join team conversations or when an Automation should post an agent-generated message to a channel.

Before you begin

You need organization-admin access, at least one non-retired agent, and permission in Slack to install or authorize the Infra One app. A binding may point to a disabled agent, but messages to that binding receive no agent reply until the agent is Enabled. The agent must also be enabled before you can select it in an Agent message Automation. For an Automation action, the destination channel must be enabled and paired to that same agent.

Connect a workspace

1. Open the organization on agents.infra.one.
2. Find Slack.
3. Select Connect Slack workspace.
4. Complete Slack’s authorization flow and return to Infra One.
5. Confirm the card shows Connected to followed by the workspace name.

For an existing connection, the card shows the workspace name and exposes Direct messages, enabled channel rows, and the channel-enablement controls inline. Change those assignments on the same card instead of connecting another app.

This real documentation-safe crop shows the connected workspace and synthetic channel binding without exposing Slack messages.

Assign direct messages

One agent is the default for direct messages in the workspace. The workspace default affects not-yet-adopted DM channels only. Under Direct messages, choose the agent that should answer a Slack DM channel when Infra One first adopts that channel. Adoption happens on the first handled message and permanently records the agent on that Slack conversation. Choose No DM agent… to stop not-yet-adopted DMs from being handled without removing the workspace.

Selecting another agent affects only DM channels that Infra One has not adopted yet. Existing direct-message conversations keep the agent recorded at first adoption. Slack gives a person and an app one persistent one-to-one DM channel, so that person cannot open a second DM to pick up the new default. The reviewed Agents surface does not expose a way to rebind an adopted DM conversation.

Enable a channel

1. For a private channel, invite the bot in Slack first. Private channels are never joined automatically and appear only after Slack makes them visible to the bot.
2. In the Slack card, choose the Channel.
3. Choose the Agent that serves it.
4. Select Enable. For a public channel, Infra One now attempts to join automatically. If that join fails, the binding remains and you can invite the bot in Slack.
5. Set the channel mode:
   • Mentions for conversational participation;
   • Off to retain the pairing without responses.

After pairing, Automations can select that channel only when their Agent field uses the same enabled agent.

To repoint an enabled channel to another agent, use its Agent selector. Infra One reuses the existing binding and mirrored room; you do not need to delete and re-enable the channel.

Retiring an agent does not clear its Slack bindings, but the retained binding cannot produce an agent reply after the configuration is disabled. Repoint a retained channel before or immediately after retirement. Change the workspace default for not-yet-adopted DM channels when needed. An already-adopted DM cannot be rebound on the reviewed Agents surface and remains silent after its recorded agent is retired; use a channel bound to an enabled agent in Mentions mode instead.

Disconnect or delete

Disconnect stops agents participating in the workspace but keeps the direct-message assignment, channel setup, and mirrored history. Reconnecting the same workspace reuses that setup. Connecting a different workspace drops workspace-local direct-message and channel assignments while retaining mirrored history.

Delete the Slack integration removes the connection, channel assignments, and mirrored rooms and messages. It leaves the organization’s agents intact. Deletion requires a typed workspace-name challenge and cannot be undone.

Success check

The Slack card shows the connected workspace, the destination channel appears with the intended agent and Mentions mode, and a controlled mention produces a response. For a private channel, the bot is already a member; for a public channel, confirm that the automatic join succeeded or invite it manually. For Automation use, open a new Automation, choose Agent message, select the agent, and confirm the channel appears in Slack channel.

Troubleshooting

• If a private channel is absent from the picker, invite the Infra One bot in Slack first, then reload the Agents page.
• If a public-channel binding exists but the agent is silent, invite the bot manually; the automatic join may have failed without removing the binding.
• Confirm that the agent is Enabled, the channel is bound to that agent, and the mode is Mentions, not Off.
• After changing Direct messages, test with a Slack DM channel that Infra One has not adopted before. An existing one-to-one DM keeps its original agent and cannot be switched by starting another conversation with the same app.
• If a retired agent still owns a channel, repoint that retained channel to a non-retired agent. For direct messages, changing the workspace default affects not-yet-adopted DM channels only; an already-adopted DM remains bound and silent.
• If an Automation cannot select a channel, enable the agent and channel and confirm that the channel is bound to the same agent selected in the action.

Related pages

• Agents overview
• Agent message
• Troubleshoot agents