Documentation / Slack Channel

Slack Channel

Updated July 18, 2026

Agent Builder Connectors and Channels screen showing Slack configuration
Configure the Slack channel in Connectors & Channels

The Slack channel puts your AI agents inside your Slack workspace. Mention the bot or send it a direct message and an agent answers in-thread — with the same conversation history it keeps for visitors on your website chat. Route different topics to different agents with @keywords: @support can go to your Support Triage agent, @seo to your SEO Optimizer. The Slack channel is part of Agent Builder Pro.

Prerequisites

  • Agent Builder Pro installed and activated
  • Permission to install apps in your Slack workspace
  • Your site reachable over HTTPS (Slack requires it for event webhooks)

Setup

1. Create a Slack app

  1. Visit api.slack.com/apps and click Create New App → From scratch.
  2. Under OAuth & Permissions, add the bot scopes: app_mentions:read, chat:write, im:history, im:read, im:write.
  3. Click Install to Workspace and copy the Bot User OAuth Token (starts with xoxb-).
  4. Under Basic Information, copy the Signing Secret.

2. Enter the credentials in Agent Builder

  1. In your WordPress admin go to Agent Builder Pro → Connectors & Channels → Channels and open the Slack section.
  2. Paste the Bot Token and Signing Secret (both stored encrypted).
  3. Pick the Default Agent that answers when no @keyword matches.
  4. Optionally restrict the bot to a specific Channel ID.
  5. Save.

3. Enable Slack events

  1. Back in your Slack app, open Event Subscriptions and switch them on.
  2. Set the Request URL to https://your-site.com/wp-json/agentic/v1/slack/events — Slack verifies it instantly.
  3. Subscribe to the bot events app_mention and message.im, then save.

Expected result

Type @YourBot hello in a channel the bot has been invited to (or open a DM with it). Your default agent replies in a thread within seconds. Start a message with an agent’s keyword to reach a specific agent. Replies are threaded, history is shared with the website chat, and each Slack user is rate-limited to 10 messages per minute per agent to keep costs predictable.

Troubleshooting

  • Request URL verification fails — the site must be publicly reachable over HTTPS; coming-soon or maintenance plugins will block Slack’s handshake.
  • Bot stays silent — confirm the app_mention and message.im events are subscribed, the bot was invited to the channel (/invite @YourBot), and a Default Agent is selected.
  • Errors after credential changes — the Signing Secret validates every request; recopy it from Basic Information if you regenerated it.

Related

Browse all documentation →