Webhook and Slack: Sentry Issue Triage Alert Template

When Sentry detects a new issue it posts the event to a Spojit Webhook trigger, an Agent-mode Connector node grades the severity, and Slack receives only the issues that clear your triage bar.

What It Builds

Sentry sends new-issue events to a Spojit Webhook trigger. An Agent-mode Connector node reads the payload (error title, culprit, level, event count, environment) and scores severity against your rules, returning a structured result via a Response Schema. A Condition node drops low-priority noise, and a Slack Connector node posts a formatted alert to your on-call channel for anything that passes.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that triggers on a webhook when Sentry reports a new issue. Read the issue payload and grade its severity as critical, high, medium, or low based on the error level, the environment, and how many events it has seen. Only when the severity is high or critical, post a message to the #on-call Slack channel with the issue title, environment, event count, and a link to the Sentry issue.

Connectors Used

Webhook trigger - receives the new-issue event Sentry posts to your Spojit endpoint.
Sentry - no native tile; Miraxa reads the issue payload directly and connects to the Sentry API for any extra lookups.
Slack - posts the triaged alert to your chosen channel.

Customize It

Change the triage bar in the prompt: swap #on-call for your team channel, raise or lower which severities get posted, or add fields like release or culprit to the Slack message. You can also tell Miraxa to weight production errors higher than staging.

Tips

Set the Webhook trigger to verify Sentry's signing secret so only genuine alerts run.
The severity grading needs an Agent-mode Connector node; a Direct-mode node runs one fixed tool with no scoring.
Add a Response Schema so severity comes back as clean JSON for the Condition node to branch on.