Slack

Your users' chatbots, answering questions directly inside Slack.

The Slack extension connects an existing trained chatbot to a Slack workspace. The user supplies a workspace name and bot token — plus an optional signing secret for installations that require request verification — and the token is checked against Slack before anything is saved, returning the workspace identity so the user can confirm they connected the right one. If the token is wrong they find out immediately rather than after a week of silence.

Once connected, messages arrive through the Slack Events API and are answered by the bot in place, using the same knowledge base the user already built for their website. That makes this the natural internal counterpart to a customer-facing chatbot: the same trained content that answers prospects on the marketing site can answer staff questions in a channel, with no second training pass. A standalone test-configuration action lets the user re-verify at any time, and channel quotas are enforced per plan with a separate global limit for free users.

Key features

• Verified before save — the bot token is checked against Slack and the workspace identity confirmed.
• Events API integration — messages are received on a webhook and answered in place.
• Optional signing secret — supported for installations that require request verification.
• Reuses trained bots — the same knowledge base serves both the website and Slack.
• Standalone test action — re-verify the connection at any time.
• Quota control — a bot limit for the free tier and a separate allowance per plan.

Powered by

Delivery runs on the Slack Web and Events APIs. Slack transports the messages; the answers come from whichever model powers the connected chatbot.

Ideal for

• Internal knowledge bots answering policy, process and onboarding questions.
• Teams whose documentation exists but nobody reads it.
• Agencies deploying assistants into client workspaces.
• Operators targeting B2B customers who live in Slack all day.