Sentry Integration Reference

Shipfox receives issue events through a Sentry App. Connect Sentry creates the integration connection used here.

Integration connection identity

A Sentry integration connection slug defaults to sentry_<organization>, such as sentry_acme. Use the actual workspace integration connection slug as a trigger's source.

This trigger fragment belongs under an existing workflow's triggers map:

triggers:
  on_issue:
    source: sentry_acme # Replace with your Sentry integration connection slug.
    event: issue.created

Events

Shipfox records these Sentry issue events:

• issue.created
• issue.resolved
• issue.assigned
• issue.archived
• issue.unresolved

Sentry owns the lifecycle meaning and original webhook payload:

Normalized event payload

The run gets an event object. It can hold action, issueId, title, culprit, level, status, platform, projectUrl, issueUrl, and webUrl. A field is present when Sentry sends its value.

Filtering by project

The integration connection receives issue events for its Sentry organization. This fragment accepts issues whose project URL contains /backend:

triggers:
  on_backend_issue:
    source: sentry_acme # Replace with your Sentry integration connection slug.
    event: issue.created
    filter: event.projectUrl.contains("/backend")

The issue payload has no normalized team field. Filter a team's events by the projects it owns. See Expressions for filter behavior and Triage Sentry issues for a complete workflow.