Skip to main content

Connect a Coworker Agent to Slack

Give an agent its own Slack identity so anyone on the team can hand it work by @-mentioning it in a channel.

Each agent gets its own Slack app — its own name, avatar, and bot identity — rather than sharing one workspace-wide bot. That keeps conversations unambiguous (you mention the specific agent you want) and lets you remove one agent's Slack access without touching the others.

Create the Slack app​

  1. On the agent's detail page, open the Connectors tab and find the Slack Event Subscription card.
  2. Click Create New Slack App. This opens Slack's app-creation page with a manifest pre-filled by MintMCP — the bot scopes and event subscription are already configured, so you just confirm and create.
  3. Copy the new app's Client ID, Client Secret, and Signing Secret from Slack's app settings and paste them into MintMCP.
  4. Click Add to Slack to install the app to your workspace.

If your Slack workspace restricts app creation, use the Manual Setup path on the same card instead: create the app yourself, paste its signing secret and bot token into MintMCP, then copy MintMCP's event subscription and interactivity URLs into your Slack app's configuration.

Invite the agent to a channel​

The app only receives mentions from channels it's in, so invite it with /invite @agent-name in each channel where people will use it.

Talk to the agent​

Mention the agent with a request:

@bella-billing-agent can you pull the overdue invoices for June and post a summary here?

The agent acknowledges with an eyes reaction right away to confirm it saw the message, then starts a run. It reads the full thread for context, posts progress updates as it works, and replies in the same thread when it finishes. Mentioning the agent again in the same thread reaches the same conversation rather than starting an unrelated run, so follow-ups and corrections work naturally.

The agent can also upload files to the thread and react to messages, so it can deliver reports or artifacts directly in Slack.

Security notes​

  • The Slack app's scopes are limited to what the agent needs: reading mentions and channel history, posting messages, uploading files, adding reactions, and looking up user names.
  • MintMCP verifies Slack's request signature before dispatching any run, so forged webhook calls are rejected.
  • Messages from other bots don't trigger the agent unless you explicitly allowlist those bot IDs in the agent's configuration, which prevents two agents from triggering each other in a loop.

Troubleshooting​

  • The agent doesn't respond to mentions — check it's been invited to the channel, and that the Slack Event Subscription card shows the app as installed.
  • The OAuth popup was blocked — use the Copy this link option on the install step and open it in a new tab.
  • The install shows "Pending" — retry the install from the Slack Event Subscription card.

Next steps​