Slack Connector
Connect your agent to Slack so users can interact with it from channels and direct messages
The Slack connector lets users interact with your deployed agent directly from Slack channels and direct messages. This connector requires manual webhook setup after deployment.
This page covers the Slack connector — routing user messages from Slack to your agent. For the Slack integration (API tools your agent can call during execution), see Slack Integration.
Prerequisites
You need a Slack App configured for your workspace:
- Go to api.slack.com/apps and create a new app (or use an existing one)
- Under OAuth & Permissions, add the required bot scopes:
app_mentions:read— Receive messages when the bot is mentionedchat:write— Send messages back to userschannels:history— Read messages in public channelsim:history— Read direct messagesgroups:history— Read messages in private channels (if needed)
- Install the app to your workspace
- Copy the Bot User OAuth Token (
xoxb-...) and the Signing Secret (found under Basic Information)
Setup
Step 1: Create the Connector
- Open your agent in Agent Studio
- In the Connectors panel, click Add Connector
- Select Slack as the provider
- Enter a Connector Name (lowercase with underscores, e.g.,
production_slack_bot) - Fill in the connector parameters:
- Signing Secret — The signing secret from your Slack App's Basic Information page
- Bot Token — Your
xoxb-bot token
- Configure access:
- Toggle Onboarding on to require approval for new users, or leave it off for open access
- If onboarding is enabled, set an Onboarding Message
- Use the Test button to validate your credentials
Step 2: Configure the Inbound Route
The inbound route filters which Slack messages reach your agent. All parameters are optional — leave them empty to accept all messages.
| Parameter | Description |
|---|---|
| Team ID | Limit to a specific Slack workspace |
| Channel ID | Limit to a specific channel |
| User ID | Limit to messages from a specific user |
Step 3: Configure the Outbound Route
The outbound route controls where your agent sends responses.
- Enable use sender as receiver to reply in the same channel/thread that triggered the message (recommended)
- If disabled, specify a Channel ID as the explicit response target
Step 4: Save
Save the agent revision to persist the connector configuration.
Deploy and Webhook Setup
Slack requires manual webhook setup after deployment.
- Click Deploy to publish the agent revision
- The connector status will show Manual Setup — this is expected
- Copy the Webhook URL provided by Fruxon
- In your Slack App dashboard, go to Event Subscriptions
- Enable events and paste the webhook URL as the Request URL
- Subscribe to bot events:
message.channels— Messages in public channelsmessage.groups— Messages in private channelsmessage.im— Direct messagesapp_mention— When someone mentions your bot
- Save the Slack App event subscription settings
- Once the webhook is verified, the connector status changes to Connected
How Users Interact
Once the connector is connected, Slack users can interact with your agent:
- Mention the bot — Type
@YourBotNamefollowed by a message in any channel the bot is added to - Direct message — Send a message directly to the bot
- Thread replies — Continue a conversation in a Slack thread for multi-turn interactions
The agent processes each message and responds in the same channel or thread.
Viewing Conversations
All Slack conversations are tracked in your agent's Conversations tab:
- Filter by Slack provider to see only Slack conversations
- View full message history including user messages and agent responses
- Each message links back to its execution record for debugging
Next Steps
- Access Control — Manage who can interact with your agent
- Microsoft Teams Connector — Connect to another platform
- Conversations — Browse all conversations