Sentry error fires.
Runframe incident exists.
Paste one webhook URL in Sentry. Application errors become structured incidents with severity, service, and error context attached. Setup takes 2 minutes.
How it works
Three steps. Nothing to install or maintain.
Copy your Sentry webhook URL
Open Sentry in the Runframe integrations hub. Link one service, then copy the service-specific webhook endpoint.
Paste it in Sentry
In Sentry, add Runframe as a webhook integration and paste the URL. No custom payload template or agent required.
Errors create incidents
When a Sentry issue event arrives, Runframe creates an incident with severity, service, and Sentry context. No manual triage.
What the integration does
Runframe turns high-signal application errors into incidents.
Configurable severity mapping
Sentry fatal and error events map to Runframe severities by default. Tune the mapping per linked service so routine errors do not page the wrong people.
Service-specific routing
Sentry uses one linked Runframe service URL. Incoming issue events route directly to that service and its on-call team.
Error context attached
Issue title, project, environment, culprit, event URL, and Sentry metadata are captured on the incident at creation.
Built-in deduplication
Runframe derives a stable key from the Sentry issue or event, so repeated events update the same open incident instead of creating noise.
What gets mapped
Sentry levels map to Runframe severity actions.
Severity mapping is configurable per linked service in Runframe.
Frequently asked questions
Connect Sentry in under 2 minutes.
Free plan available. No credit card required.