// team chat

Agentbot for
Discord.

Notify your community Discord when a chat needs attention. Webhook in, message out.

Why Discord + Agentbot

Lots of dev tools, open-source projects, and creator-led brands run their support in Discord rather than Slack. Same pattern works: Agentbot's webhooks feed a Discord channel webhook, and a chat ping lands in your team channel the moment a visitor needs a human. Two minutes to set up, no Discord bot required.

Install in 3 steps

  1. Step 1

    Create a Discord channel webhook

    In Discord, right-click the channel → Edit Channel → Integrations → Webhooks → New Webhook. Name it (e.g. "Agentbot") and copy the webhook URL.

  2. Step 2

    Register the webhook in Agentbot

    Agentbot dashboard → Settings → Webhooks → New endpoint. Paste the Discord webhook URL. Subscribe to the events you want pinged (conversation.created with needs_human, ticket.created).

  3. Step 3

    Transform the payload (optional)

    Discord expects { "content": "..." } or { "embeds": [...] }. Agentbot's default payload won't match exactly — route through a transformer (Zapier, n8n, Make, or a one-line Cloudflare Worker) to shape the message before it hits Discord.

Full install docs →

What you get

  • Channel pings when a chat needs a human
  • Native Discord webhook — no bot, no OAuth, no listed app
  • HMAC-signed Agentbot events — verifiable in the transformer step
  • Works in any Discord server you can create webhooks in

Common flows users automate

  • AI hands off → ping #support-chat with visitor name + first message
  • Visitor flags "this is a bug" → ping #bug-reports with the transcript link
  • Ticket filed → ping #moderation with the ticket subject
  • Community-question chat closes successfully → log to #ai-wins for visibility

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 Discord bot to receive Agentbot notifications?

No. Discord's built-in channel webhooks are exactly what you need. They're a per-channel feature you create from the channel settings — no bot creation, no OAuth, no application listing in the Discord Developer Portal.

Can I send messages back into Agentbot from Discord?

Write-side API (post a message into a conversation from outside) is on the roadmap. For now, Discord notifications are one-way — the team gets pinged, clicks through to /dashboard/inbox/<id>, replies there.

Why do I need a transformer step (Zapier / n8n)?

Discord's webhook expects a specific JSON shape (`content` or `embeds`). Agentbot's webhook ships a richer JSON with conversation context. The transformer maps one to the other — a 5-line script. If you don't want the transformer, you can post a minimal `content: "new chat from X"` directly from Agentbot's webhook config, but you lose the conversation link.

Can I rate-limit pings so we don't spam the channel?

Subscribe only to high-signal events (conversation.created with needs_human, ticket.created) — not every message. If volume is still too high, route through a rate-limiter (Cloudflare Worker, Vercel Edge Function) that drops pings within N seconds of the previous one.

Will an official Agentbot Discord app ship?

Not on the immediate roadmap. The native channel webhook approach covers the common pattern (one-way notifications) — the place a Discord app would help is two-way conversations (reply from a Discord thread), which is gated on the Agentbot write API landing first.

Try Agentbot in Discord — free.

One snippet, no credit card. See pricing · webhook docs.

Get Agentbot — Free →

Also installs in: Webflow · WordPress