Route New Sentry Issues Straight Into Discord

Every new Sentry issue or error is enriched with its key details and pushed to Discord so the right people see it immediately — no more issues sitting unnoticed until someone checks the dashboard.

difficulty Intermediatesetup 30 minresult New Sentry issues appear in Discord within seconds, labelled and linked, so response time drops.
  1. 1

    Step 1 — Trigger on new issue

    Add the Sentry trigger (or webhook) for new issues/events. For Sentry, filter to the labels or severity you care about.

  2. 2

    Step 2 — Extract the essentials

    Add a Set node capturing title, severity, a short description and the link back to Sentry.

  3. 3

    Step 3 — Prioritise (optional)

    Add an If/Switch on severity so critical items page a channel while the rest go to the normal queue.

  4. 4

    Step 4 — Post to Discord

    Add a Discord node. Point it at a channel webhook and paste the title, severity and link into the content field. Discord webhooks need no OAuth — just the webhook URL from the channel settings.

Frequently asked questions

Can I avoid duplicate pings?

De-duplicate on the Sentry issue ID before Step 4, and for recurring errors set a cooldown so a flapping issue doesn't spam Discord.

Two-way sync possible?

This is one-way by default. For two-way, add a second workflow that listens to Discord changes and writes status back to Sentry.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.