Connect Slack in the console

Open the agent's Slack tab to see its app status. New agents reach the same component at Connect channels, after name, job, release and activation. Connecting Slack is optional.

The Slack tab uses the same sections as Settings > Workspace > Integrations > Slack. The Slack card at the top shows the connection, bot ID, home channel and whether DMs are received; once the app is installed, Connected channels and Basic follow. Agent managers then see the integrations screen's sections under the same names and in the same order: Slack app creation (the state of the workspace token this agent's app is made with), Addresses for a Slack app (this agent's Events Request URL), Slack apps made here (a one-row table of this agent's app), and Danger zone last. Choose a section in the list on the left to jump to it. On narrow screens the list folds into one button above the content that names the section you are in; pick a section from it and the list folds again.

Turn on the agent and choose Create and install Slack app. A workspace administrator must configure app creation (the App Configuration Token) first. When it is missing or Slack no longer accepts it, the button is off and the reason shows below it: owners and admins get a Go to workspace Slack settings link, and other agent admins are told to ask an owner or admin.
Install the app on Slack's consent screen. The callback completes installation, returns to the Slack tab and shows the result in a notice at the bottom of the screen. If consent is declined or the link expires, a notice says so; start a new installation from that tab. Used links are never retried automatically. Before making the link, the server asks Slack, with the token of the Slack user who made the app, whether the app still exists. If Slack no longer has it (deleted in Slack, for example), the tab says so instead of opening the consent screen; delete the app under Danger zone and install again to create a new one. When the App Configuration Token now belongs to another Slack user, the link is made without that check and the Slack tab warns ahead of time: that token may fail to install the app, so register the original user's token again or add the new user as a collaborator on the app. When permissions or event settings change, choose Reinstall on the app's row in Slack apps made here. The row's ⋯ menu has Open in Slack, which opens the app's Slack settings page in a new tab, and Refresh.
Once installed, an agent with no home channel shows only the Set a home channel step in the Slack tab (the app sections managers see and Danger zone stay). Pick a channel under Choose home channel: it is saved in use and as the home, and the other sections appear. A private channel in the list carries the /invite hint.
In the Channels section choose Add channel, search by name prefix and choose Connect. A notice at the bottom of the screen shows the result. Each connected channel has a Use in this channel switch and a Respond only when mentioned switch. With use off the agent does not respond there; with mention-only off it also responds to messages posted in the channel without a mention. A channel you add, or invite the agent to, is connected in use. The Default response for new channels switch in Basic decides whether new channels respond only when mentioned and is saved to the server as soon as you change it. Channels already connected do not change. It starts on (only when mentioned). Receive DMs saves the DM binding separately.
A channel you switch back into use comes back responding only when mentioned. Failed saves show an error and retain the stored setting. Choose Set home to change the home channel.

The server adds the bot to a public channel when you connect it with its response on, or turn the response on later; it does not join a channel whose response is off. The bot cannot join a private channel by itself, so invite it with /invite. A private channel the bot is not in yet carries a /invite required tag and a copy button, which copies /invite @<agent slug> to the clipboard. If the browser blocks the clipboard, a field with the command selected appears so you can copy it yourself. Search includes public channels and private channels the bot has joined. Load more reads the next page. The screen warns when Slack rate limits leave old results or the list is truncated.

In the Danger zone, Disconnect on the Disconnect Slack row revokes the agent's Slack identity and channel bindings; the Slack app stays and can be installed again. Delete app on the Delete the Slack app row deletes the Slack app and stored credentials. This can't be undone, and connecting again makes a new app. Both actions explain their consequences before confirmation.

Press Enter on a section link to move focus to that section, Tab to reach switches, and Space to change a response. Results and errors are announced to assistive technology.

If event registration is unfinished, the callback shows a verification notice. The Events Request URL row under Addresses for a Slack app shows whether Slack has checked the address (checked, waiting, registration failed, not sent yet), and Recheck sends the address to Slack again. Once the address has been sent and Slack has not checked it yet, a notice under the Slack card links to the Event Subscriptions page of the Slack app's settings. Before the address is sent, no notice appears. Actual Slack mentions and event handling after revocation require separate human verification.

On the All tab of the Agents list, a card or table row gets a Slack needs attention: <reason> link only when that agent's Slack tab asks a person to do something. The link opens the agent's Slack tab. It shows one reason: the first thing the Slack tab shows. Before an install it is app not installed; after the bot was disconnected or the app uninstalled, reinstall needed. Once installed, the first that applies in this order: events URL not verified yet (after it was sent), pick a home channel, events URL failed. Agents with no app, or with one that is set up, get no link. The API field is summary.slack_action in GET /v1/agents?include=summary. The Agents I manage tab's list has no summaries, so it shows no link.

On an owner's or admin's Home, To do now appears above Getting started only while such agents exist. Each row shows Slack: <reason>, the agent's name and what it causes; the button opens that agent's Slack tab and names what to do there (Install app, Reinstall app, Verify events URL, Recheck events URL, Choose home channel). Up to three rows show; with more, View all N goes to the agents list. Home reads the first 100 agents only, so with more agents than that the count ends in "+". When only agents beyond those 100 need attention, To do now does not appear.

The Slack apps made here section of Settings > Workspace > Integrations > Slack lists the Slack apps this console made: the account linking app first, then agent apps by agent name. Each row shows the app's name and Slack app ID, its agent, its status and when it last changed. The status is Connected (for the account linking app, its client secret is stored so Sign in with Slack works; for an agent app, the bot @slug is installed), Not installed, No secret (an account linking app without a client secret), Creating or Deleting. Details opens that agent's Slack tab. The section only reads: an agent app is installed, disconnected and deleted in that agent's Slack tab. No screen deletes or remakes the account linking app yet. Apps made by hand, and ones that failed or were deleted, are left out. Only owners and admins can see it; the API is GET /v1/workspaces/{id}/slack/apps. On narrow screens the agent and time fold under the app.