• Customers
  • Docs
  • Pricing
Log inLGet startedS
Slack

Platform

Start here

  • Get started
  • Use the API
  • CLI reference

Concepts

  • Sandboxes
  • Commands
  • Model providers
  • Files
  • Images and registries
  • Volumes
  • Secrets
  • Endpoints
  • Connections

Reference

  • SSO and SCIM
  • Organizations and access
  • API reference

Company agent

Start here

  • Get started
  • Core concepts

Set up

  • Models
  • Sandboxes
  • Knowledge
  • Integrations
  • Secrets
  • Instructions and skills
  • Members and roles

Use Adapt

  • Agents
  • Chats and tool activity
  • Automations

Surfaces

  • Slack
  • GitHub
  • Email
  • iMessage and SMS
  • Webhooks

Run Adapt

  • Self-host
  • Security and privacy

Platform

Start here

  • Get started
  • Use the API
  • CLI reference

Concepts

  • Sandboxes
  • Commands
  • Model providers
  • Files
  • Images and registries
  • Volumes
  • Secrets
  • Endpoints
  • Connections

Reference

  • SSO and SCIM
  • Organizations and access
  • API reference

Company agent

Start here

  • Get started
  • Core concepts

Set up

  • Models
  • Sandboxes
  • Knowledge
  • Integrations
  • Secrets
  • Instructions and skills
  • Members and roles

Use Adapt

  • Agents
  • Chats and tool activity
  • Automations

Surfaces

  • Slack
  • GitHub
  • Email
  • iMessage and SMS
  • Webhooks

Run Adapt

  • Self-host
  • Security and privacy

The open platform for company agents. Use the whole platform or build with individual components.

Products

Company agentAI Transformation ServicesSandboxesStorageModel gatewayPricing

Solutions

EnterpriseFor CEOsEngineeringOperationsSalesAll solutions

Resources

DocumentationDeveloper guideChangelogBlogCustomer storiesIntegrations

Company

AboutCareersTrust centerSupportTalk to usGet started

Social

XLinkedInGitHubYouTube
© 2026 AdaptMade with ♥ in Adapt teammates walking outside the Presidio officeAn Adapt engineer at their desk at dusk, the Golden Gate through the windowAn Adapt teammate pointing to the Adapt sign at the office doorTermsPrivacy

Surfaces

Slack

On this page
  1. Add Slack to an agent
  2. Check the connection
  3. Who the agent answers
  4. Choose when it replies in channels
  5. What the agent can do in Slack
  6. Replies and files
  7. Read Slack threads in Adapt

The Slack surface lets people mention an agent in a Slack channel or send it a direct message, and get the answer in the same thread.

Each Slack thread is one conversation with the agent. A message from Slack becomes an ordinary run, with the same model, tools, and limits as a web chat; the final answer is posted back to the thread by the agent's Slack app.

Add Slack to an agent

Only owners and admins can add a surface. Go to Agents, open the agent, then Settings → Where it answers → Add surface → Slack. First setup offers the same step.

Setup has four steps:

  1. Make its Slack app. Create app in Slack opens Slack with the app's manifest filled in, named after the agent. Pick your Slack workspace, create the app, and install it.
  2. Add its credentials. Paste the app's App ID and Signing secret (Basic Information → App Credentials) and its Bot token, the Bot User OAuth Token under OAuth & Permissions (starts with xoxb-). To connect a Slack app you already have, skip step 1 and paste its credentials here.
  3. Answer as the agent. The app answers as the agent you're setting it up for.
  4. Send events to Adapt. Slack sends events to the connection's Request URL, <your Adapt URL>/api/surfaces/<connection ID>. For an app made from the manifest, Slack doesn't verify that URL by itself: under Event Subscriptions, click Retry, then Save Changes, and do the same under Interactivity & Shortcuts. For an existing app, paste the URL in both places.

The Request URL must be a public HTTPS address. A self-hosted install on localhost or plain HTTP can't receive Slack events; see Self-host.

During setup, Adapt sends you a direct message in Slack. Mention the app or reply to it, and confirm the message is yours: that links your Slack account to your Adapt account.

Scopes and events

The manifest requests every scope the agent's Slack tools use and subscribes to app_mention, message.im, message.channels, message.groups, and app_home_opened. Apps made by Adapt also get channels:join and chat:write.customize. For an older or hand-made app, the connection's setup check lists only the scopes Slack reports as missing; add them under OAuth & Permissions and reinstall the app.

Inviting the app to a channel is still up to you: the bot reads and posts only where Slack lets it.

Check the connection

Open the agent's Slack row under Where it answers to see its status and Setup check. Adapt checks that its Request URL is reachable over public HTTPS, then uses the app's own credentials to check the bot token and its scopes. Some checks, such as event delivery and direct messages, can only pass once Slack has sent real traffic, so they stay unchecked until someone messages the app.

A connection that's on is permitted to run, not verified healthy. Pausing a connection keeps its settings; while paused it neither receives nor sends messages.

Who the agent answers

The agent answers workspace members by default. When a Slack message arrives, Adapt looks the sender up with Slack's users.info and matches their Slack email to a member's Adapt email. A match is linked to that member and the run acts as them, with their role and access. People who leave the workspace stop matching.

Each surface comes with an automation, Respond to Slack messages, on the agent's Automations tab. Its events can widen who gets answers:

  • Allow responses to non-workspace members: off by default. When on, Slack users who aren't members get answers too. Their runs are anonymous: no Adapt user and no workspace role.
  • Allow responses to bots: off by default. Other bots then run anonymously. The agent's own messages are always ignored.

Slack Connect senders from another Slack workspace are always ignored, whatever these settings say. The sender Adapt verified is stated in the agent's instructions, so message text can't claim to be someone else. History search and Adapt administration tools are never available in Slack threads.

Choose when it replies in channels

In channels, the agent replies only when mentioned. Direct messages always reach it.

To have it join in without a mention, open the Slack row and add a Reply rule for a channel. Choose Smart, then say When to reply (for example, "Someone posts a bug report") and What to do ("File a GitHub issue and reply with the link"). A decision model reads each new channel message against the rule and starts a run only when it fits. Mentions only keeps the default.

A rule needs a decision model for the agent (set in Agent defaults or the agent's model settings) and the decision tool turned on for the workspace. Until then, the rule shows what's missing and the agent replies there only when mentioned. A rule for a private channel is visible only to members of that channel.

What the agent can do in Slack

In a Slack thread, the agent reads the thread and its files. When it was mentioned partway through a thread, it also gets the messages since it was last asked, up to 200, as untrusted context. It can edit only replies it posted itself.

Its Slack tools:

  • slack_search: searches public workspace content. It works only in the run started by a Slack mention or direct message, for at most 15 minutes, because it uses that message's search session.
  • slack_list_channels and slack_read: list channels and read messages, threads, and canvases by name, ID, or link.
  • slack_post_message, slack_add_reaction, and slack_update_channel: post to another channel or thread, or DM a user; react; and change a channel's name, topic, or purpose.

Reads check the person asking as well as the bot: private channels, DMs, and guests need that person to be in the channel. These tools also appear in the agent's web chats, acting for the signed-in member. Anonymous runs keep only the thread tools.

Every tool call runs as soon as the model makes it. Check the activity on the thread's conversation in Adapt to see what it did.

Replies and files

While a run works, the thread shows the app as is working.... The answer is posted as a reply in the thread, and a failed or interrupted run posts a short error instead. Replies to one thread go out in order, and a new message waits until the previous answer is delivered.

  • Files in: attachments on the message, and on the earlier thread messages it catches up on, become the run's files. A file Slack won't let apps download becomes a note.
  • Files out: up to 10 files and 25 MB per reply. If a file can't be sent, the answer goes without it and names what's missing.

If Slack fails after Adapt has started posting, the delivery is marked uncertain and is never sent again, so a reply is never posted twice. Check the thread before asking again.

Read Slack threads in Adapt

The member who started a Slack thread sees it in their chat sidebar. Any member who can view the agent and can read that Slack channel can open the thread in Adapt, read-only, with each message labeled by its author or as anonymous. To continue it, reply in Slack.

The thread's owner and admins can rename or delete it. Deleting hides the conversation; the next message in that Slack thread starts a fresh one.

PreviousAutomationsNextGitHub

On this page

  1. Add Slack to an agent
  2. Check the connection
  3. Who the agent answers
  4. Choose when it replies in channels
  5. What the agent can do in Slack
  6. Replies and files
  7. Read Slack threads in Adapt