Operations6 min readUpdated 2026-06-29
Monitor Sentry Workflows in n8n
Metrics, alerts and dashboards that tell you when Sentry workflows are unhealthy — before users notice.
Key takeaways
- Four dashboards, three alerts.
- Instrument at the workflow tail.
- Weekly retros beat quarterly panic.
- Kill dead workflows — clutter is a real cost.
Automation you can't see is automation you can't trust. This guide sets up the four dashboards and three alerts you need for Sentry workflows.
Four dashboards
Executions/day, error rate, p95 duration, cost per run. If any of these move, you want to know within minutes.
Three alerts
Error rate over threshold, p95 duration spike, and lag on any sync. Route to Slack; escalate to PagerDuty after 15 minutes.
Instrumentation
Emit metrics from n8n to Prometheus/Grafana or push to Datadog. A Function node at the tail of each workflow does the trick.
Retros
Weekly 20-minute review of the four dashboards. Kill dead workflows. Reinvest saved credits.
Frequently asked questions
- Grafana or Datadog?
- Either. Grafana is cheaper; Datadog is easier to bootstrap.
- Do I need APM?
- Only past a few thousand executions per day.
- SLA target?
- 99.5% is a reasonable start for internal workflows.
- Who owns the alerts?
- One named human. Rotate weekly.