Integration
Automate with Sentry.io
Sentry surfaces every error in your application before your customers notice. NVS connects Sentry alerts to your issue tracker, on-call system, and team channels so nothing falls through.
Use Cases
When Sentry detects a new unhandled exception above the alert threshold, a Jira bug ticket is created and the responsible engineering team is alerted in Slack.
Trigger
New Issue
sentryio.trigger
Fires when Sentry captures a new issue above the configured threshold.
Classify Error Severity
nvs.set
Error type, affected users, and frequency analyzed to determine priority.
IF
Severity P1 or P2?
nvs.condition
High-severity errors get immediate escalation.
NO
Output
Log to Backlog
jira-software.issue
P3 Jira bug created. Added to backlog with low priority.
YES
Create P1/P2 Jira Bug
jira-software.issue
Jira bug created with stack trace, affected users, and Sentry link.
Output
Alert On-Call in Slack
slack.message
Slack alert: error title, affected users, severity, and Jira ticket link.
When Sentry detects an error rate spike — more than 10x normal frequency in 5 minutes — a PagerDuty incident is created and the on-call engineer is paged.
Trigger
Error Rate Spike
sentryio.trigger
Fires when error frequency crosses the spike threshold.
Fetch Error Context
sentryio.api
Error title, stack trace, affected users, and occurrence count fetched.
Create PagerDuty Incident
pagerduty.incident
P1 incident created with error details and Sentry project link.
Output
Alert #incidents
slack.message
Slack critical alert: error name, spike count, affected users, and PagerDuty link.
When a Sentry issue is marked as resolved, the linked Jira bug ticket is automatically closed and the engineering team receives a Slack notification.
Trigger
Issue Resolved
sentryio.trigger
Fires when a Sentry issue status changes to resolved.
Find Linked Jira Ticket
jira-software.issue
Jira ticket matching the Sentry issue ID fetched.
IF
Linked Ticket Found?
nvs.condition
Only issues with a linked Jira ticket trigger automatic closure.
NO
Output
Done
nvs.end
No linked Jira ticket. Resolution logged only in Sentry.
YES
Output
Close Jira Ticket
jira-software.issue
Jira bug moved to Done. Resolution note and Sentry link added.
Ready to automate Sentry.io?
We'll map your workflow, connect your tools, and build it in days, not months.
Book a Free Strategy Call →