Sentry events

Look up every Sentry issue event Shipfox delivers and the normalized event fields available to workflows.

This reference lists the Sentry issue events that Shipfox delivers to a Sentry integration connection. See the Sentry overview for availability and setup.

Payload

Shipfox normalizes the Sentry issue webhook payload before it is available as event. Sentry owns the original webhook schema. See Sentry issue webhooks for that schema.

Shipfox maps Sentry's ignored action to archived, which produces the issue.archived event.

Field	Type	Description
`action`	`created`, `resolved`, `assigned`, `archived`, or `unresolved`	Sentry issue action.
`issueId`	string	Sentry issue ID.
`shortId`	string or `null`	Short Sentry issue ID.
`title`	string	Issue title. Shipfox uses `Sentry issue` when Sentry omits it.
`culprit`	string or `null`	Sentry issue culprit.
`level`	string or `null`	Sentry issue level.
`status`	string or `null`	Sentry issue status.
`platform`	string or `null`	Sentry issue platform.
`webUrl`	string or `null`	Sentry issue page URL.
`issueUrl`	string or `null`	Sentry issue API URL.
`projectUrl`	string or `null`	Sentry project URL.
`firstSeenAt`	string or `null`	Time Sentry first observed the issue.
`lastSeenAt`	string or `null`	Time Sentry last observed the issue.

Trigger fragment

Replace sentry_acme with the integration connection slug:

triggers:
  on_issue:
    source: sentry_acme
    event: issue.created

For trigger field rules, see the workflow schema reference.