How to use Discord for support team alerts
ReplyRabbit doesn't have a Discord integration. Its built-in notifications go to Slack through an incoming webhook, and that's the only chat tool it posts to directly. If your support team lives in Discord, you have two practical routes: use Workflow Tags so ReplyRabbit marks conversations with FreeScout tags, and let a FreeScout Workflows recipe or your own automation carry the alert to Discord; or accept a Slack channel for the two events ReplyRabbit posts. This page is honest about what each route gives you.
What ReplyRabbit can alert on at all
Before choosing a route, it helps to know the raw material.
| Signal | Where it appears | Plan |
|---|---|---|
| Issue created in Linear, GitHub or Jira | Slack webhook post; rr_linear_issue_created tag for Linear | Pro (manual), Team (automatic) |
| Follow-up draft ready after an issue is done | Slack webhook post | Pro, Team |
| Priority, sentiment, intent, human review, sales opportunity | AI Signals chips; Workflow Tags such as rr_priority_critical, rr_needs_human | Pro, Team |
| No reply needed, draft ready | Workflow Tags rr_no_reply_needed, rr_ai_draft_ready | Pro, Team |
Slack gets the first two directly. Everything else is expressed as a FreeScout tag, which is the hook for any other tool.
Route one: tags into your own Discord automation
- In the mailbox's ReplyRabbit settings, turn on AI Signals and, in Workflow Tags, Enable workflow sync and Apply FreeScout tags.
- Confirm tags like
rr_priority_criticalappear on recent conversations. - In the FreeScout Workflows module, write a recipe that reacts to the tag. What the recipe can do depends on your Workflows install; if it can call a URL or send a notification, point that at a Discord webhook you've created for the channel.
- If Workflows can't reach Discord, any automation that can read FreeScout tags (a scheduled script against the FreeScout API, for example) can post to Discord's webhook instead. That part is your own code, not ReplyRabbit.
This route gives you alerts on every signal, not just issue creation, at the cost of building the last hop yourself.
Route two: a Slack channel for the two built-in events
If the alerts you want are "engineering has a new issue" and "a fix is ready to announce", ReplyRabbit already posts those to Slack. Some teams that run Discord for everything else keep a free Slack workspace for exactly this, because it takes five minutes and needs no code. Setup is in Slack integration.
What not to do
Don't paste a Discord webhook into ReplyRabbit's Slack Webhook URL field. The payload format is Slack's, and Discord will reject it. Don't copy full customer threads into Discord either; an alert should carry the conversation link and a one-line summary, and the detail stays in FreeScout where access is controlled.
Where the alerts come from
Whatever tool displays them, the events originate in the tracker and tagging features. Linear setup is in Linear integration, the tag reference in FreeScout Workflows integration, and the mailbox basics in How to set up ReplyRabbit. If tags aren't being applied, Troubleshooting ReplyRabbit has the checklist.