// team chat
Agentbot for
Slack.
Pipe Agentbot events into a Slack channel via signed webhooks. No Slack App approval needed.
Why Slack + Agentbot
Most support teams already live in Slack — the inbox is where they go to act, but the notification belongs where they already are. Agentbot's webhooks feed straight into a Slack Incoming Webhook URL: when a chat needs a human, the right channel pings. No Slack App listing, no OAuth dance, no approval workflow.
Install in 3 steps
- Step 1
Create a Slack Incoming Webhook
In your Slack workspace → Settings & administration → Manage apps → search "Incoming Webhooks" → Add to Slack. Pick the channel (e.g. #support), copy the generated webhook URL.
- Step 2
Register the webhook in Agentbot
Agentbot dashboard → Settings → Webhooks → New endpoint. Paste the Slack webhook URL. Subscribe to the events you want pinged (typically conversation.created with needs_human, ticket.created).
- Step 3
Format the Slack message (optional)
Slack expects a JSON body shaped a specific way ({"text": "..."}). For pretty rich messages with the visitor name, conversation link, and message preview, route through Zapier or a small serverless function to transform Agentbot's payload into Slack's block-kit format.
What you get
- Channel pings the moment a chat needs a human
- Direct webhook → Slack — no Slack App approval cycle
- HMAC-signed events from Agentbot — verify upstream if you route through a transformer
- Multiple endpoints supported — different channels for different event types
Common flows users automate
- AI hands off → ping #support with visitor name + first message
- New ticket filed → ping #engineering-tickets with the ticket subject
- Conversation auto-closed by AI → log to #support-archive for retro
- High-priority ticket → @here in #on-call
Troubleshooting
Hit a snag? The FAQ & troubleshooting docs cover the common gotchas (widget not appearing, snippet not loading, theme conflicts).
FAQ
Do I need a Slack App or OAuth?
No. Slack Incoming Webhooks are the simplest delivery mechanism — they give you a one-off URL that posts to a specific channel. No app installation, no OAuth flow, no approval. This works for 95% of team-notification use cases.
Can the message include a link back to the Agentbot conversation?
Yes, but you need a transformer in between. Agentbot's webhook payload contains the conversation ID; Slack's Incoming Webhook expects a `text` field. Route through Zapier / Make / a serverless function to build a Slack message body like `New chat from {{visitor_name}}: <https://agentbot.com/dashboard/inbox/{{conversation_id}}|view>`.
Can I post replies into Agentbot FROM Slack?
Read-side direction (Agentbot → Slack) is solid today. Write-side (Slack → Agentbot, e.g. reply from a Slack thread) requires the Agentbot write API, which is on the roadmap. For now, the Slack ping is a notification — agents click through to the dashboard to reply.
Will it flood our Slack channel?
Only if you subscribe every event to Slack. The recommended pattern: subscribe only conversation.created (with the needs_human filter) and ticket.created. Skip message.created — that fires on every message and turns into noise quickly.
Will an official Agentbot Slack App ship?
On the roadmap, mainly so we can support two-way conversation (reply to a chat from a Slack thread). Until then, the Incoming Webhook route is the recommended path — it covers the common case (get notified, click through to reply) without the OAuth ceremony.
Try Agentbot in Slack — free.
One snippet, no credit card. See pricing · webhook docs.
Get Agentbot — Free →