Skip to main content
Each Devin Bot can have its own Slack app with its own handle. Your team messages the Bot directly or mentions it in a channel, and the Bot replies in the thread:
A Slack thread in #frontend. Sam writes: @frontend-bot anything on checkout waiting on me? The Bot replies twice in the thread: One thing. The mobile layout fix is ready to review. Then: Merged. Checkout is centered on mobile now.

Before you start

Connect Slack to your organization first. See the Slack integration. Until a Bot has its own Slack app, it uses the shared Devin app as a fallback.

Set up the Bot’s Slack app

Open the Slack page of the Bot’s settings. A new Bot’s chat offers the same setup in its Connect your chat app card.
1

Authorize

Allow the requested permissions in Slack. This is a one-time authorization for your Slack account that lets Devin create and install the Bot’s app on your behalf.
2

Add to Slack

Pick the handle people use to @-mention the Bot.
3

Select channels

Choose the public channels where the Bot should work. For a private channel, run /invite @handle in Slack.
4

Choose who can message the Bot

Only the people the Bot is shared with can use it in Slack. To widen that, change Who can message under Slack permissions.
Adding the Bot to a channel gives it write access there. Otherwise, it can still read public channels the shared Devin app is in. In the Bot’s chat in Devin, type # to mention a Slack channel, for example to ask the Bot to post a summary there.

Slack admin approval

If your workspace requires admin approval for apps, a Slack admin has to install the Bot’s app. The Slack page shows where the request stands and gives you a link to send your admin. Devin creates a Slack app for each Bot. To approve these apps automatically, a Slack admin can:
  1. In Slack’s admin settings, go to Integrations → Installed apps and open Devin.
  2. Click Manage → Manage permissions.
  3. Check Allow this app to install managed agent apps, then click Save.
Slack's Manage permissions dialog for the Devin app, with the Allow this app to install managed agent apps checkbox above the Cancel and Save buttons.

Slack permissions

Two settings control how the Bot behaves in Slack: Each Who can message level includes the ones before it: A few rules apply:
  • Every level above People with access needs direct messages turned on in your organization’s Slack Default Access settings. While they’re off, only People with access can be picked, and the setting says why.
  • Anyone in Slack, including Slack Connect is offered only in organizations where external Slack users are enabled for automations, and Devin asks you to confirm the choice.
  • A person can always add the Bot to a channel with /invite, whatever Allowed channels is set to.
A Bot that responds to untrusted messages is at risk of prompt injection. Be very cautious when allowing messages from people outside your organization.
The Who can message setting also appears under Message sources on the Bot’s Sharing page. See Message sources.

Rename, reinstall, or delete the app

Members who can configure the Bot can manage its app from the Slack page:
  • Rename in Slack changes the app’s name and @-mention in Slack. The Bot’s name in Devin stays the same.
  • Reinstall app installs the app again. A reinstall can also wait for a Slack admin’s approval.
  • Delete app removes the Bot’s app from Slack. You can create a new one afterward.
Renaming the Bot in Devin also renames its Slack app, unless you gave the app a different handle with Rename in Slack. If the app is uninstalled from Slack, or its Slack workspace is disconnected from Devin, the Slack page says so and offers to install it again.