Slack Integration

This guide walks you through connecting an Aigentic agent to a Slack workspace.

Prerequisites

• An Aigentic agent already created
• A Slack workspace where you have permission to install apps

Step 1: Create a Slack App

1. Go to the Slack API portal.
2. Click Create New App.
3. Choose From scratch.
4. Enter an App Name (e.g., “My AI Agent”) and select your workspace.
5. Click Create App.

Step 2: Configure OAuth and Permissions

1. In your app settings, go to OAuth & Permissions.
2. Under Bot Token Scopes, add at minimum:

Scope	Purpose
chat:write	Send messages
channels:history	Read messages in public channels
channels:read	View public channel info

You may also want these optional scopes for richer functionality:

Scope	Purpose
groups:history	Read messages in private channels
im:history	Read direct messages
app_mentions:read	Receive @mention events
users:read	View user info
files:write	Upload files
reactions:write	Add emoji reactions

3. Click Install to Workspace.
4. Review the permissions and click Allow.
5. Copy the Bot User OAuth Token (starts with xoxb-).

Step 3: Enable Events

For the bot to receive messages, enable events:

1. Go to Event Subscriptions in your app settings.
2. Toggle Enable Events to on.

Socket Mode (Recommended)

Socket Mode does not require a public URL. It uses a WebSocket connection.

1. Go to Socket Mode in your app settings.

2. Toggle it On.

3. Generate an App-Level Token with the connections:write scope.

4. Copy the token (starts with xapp-).

5. Under Subscribe to Bot Events, add:

Event	Description
message.channels	Messages in public channels
message.groups	Messages in private channels
message.im	Direct messages
app_mention	When someone @mentions the bot

5. Click Save Changes.

Step 4: Configure in Aigentic

1. Open Channels from the sidebar.
2. Click Configure on the Slack card.
3. Enter the Bot Token (xoxb- token from Step 2).
4. Enter the Channel ID where the bot should operate (right-click the channel in Slack → View channel details → copy the Channel ID, starts with C).
5. Select the responding agent from the dropdown.
6. Choose the Reply Mode:
   • Reply to all messages (in threads) — The bot replies to every message in the channel, using threads.
   • Don’t auto-reply — The bot only responds when explicitly triggered.
7. Optionally click Test Connection to verify the token and channel access.
8. Click Save Configuration.

Tokens are encrypted and stored in the credential vault.

Tip

Enable Server-Side Polling for Slack (toggle in the Server-Side Polling section at the bottom of the Channels page) to keep the bot running even when your browser tab is closed.

Step 5: Add the Bot to Channels

The bot needs to be added to each Slack channel where it should be active:

1. In Slack, go to the channel.
2. Type /invite @YourBotName.
3. Repeat for each channel.

Step 6: Test the Connection

1. Go to a channel where the bot is added.
2. Send a message mentioning the bot:

   @MyAIAgent What can you help me with?

3. The bot should respond in a thread or inline, depending on configuration.

Slack Features

Thread Conversations

The bot can reply in threads to keep channels organized. Follow-up messages in the thread maintain conversation context.

Rich Formatting

Slack uses its own markup format (mrkdwn). Aigentic automatically converts agent responses with bold, italic, code, and code blocks.

Emoji Reactions

The bot can react to messages with emoji to acknowledge receipt while processing.

Troubleshooting

Bot not responding to messages

• Verify the bot is added to the channel (/invite @YourBotName).
• Check that Event Subscriptions are enabled and the correct events are subscribed.
• Verify the xapp- token is correct.

”not_in_channel” error

The bot has not been invited to the channel. Use /invite @YourBotName.

”missing_scope” error

The bot token lacks a required OAuth scope. Go to OAuth & Permissions, add the missing scope, and reinstall the app to the workspace.

Bot responds multiple times

• Check that only one connection is using this bot token.
• Verify the event subscription is not duplicated.