The Hookdeck Sentry integration is pending publication by Sentry and isn't available to install yet. This guide describes how it will work once it's available.

Sentry Hookdeck Integration Benefits

  • Track problems with your event flows next to your application errors. Hookdeck Issues such as failed deliveries, transformation errors, backpressure, and rejected requests become Sentry issues in the Sentry project you choose.
  • Keep one status across both tools. Resolving, archiving, reopening, or assigning an issue in Sentry updates the Hookdeck issue, and changing a Hookdeck issue's status updates the Sentry issue.
  • Use your existing Sentry workflow. Sentry alert rules, assignment, and ownership apply to Hookdeck issues like any other Sentry issue.

How it Works

When a Hookdeck Issue Trigger opens an issue, Hookdeck creates a Sentry issue in the Sentry project selected for that trigger. Each Hookdeck issue maps to exactly one Sentry issue. If the Hookdeck issue happens again after being resolved, the same Sentry issue is reopened and marked as a regression.

The Sentry issue includes:

  • Title: the cause of the Hookdeck issue, for example Your destination responded with an HTTP 500 code on your connection stripe -> orders.
  • Environment: the name of your Hookdeck project.
  • Tags: hookdeck_issue_id, hookdeck_issue_type, hookdeck_project, and when available connection, source, and destination, so you can search and filter Hookdeck issues in Sentry.
  • Context: a hookdeck section with links to the issue and its issue trigger in the Hookdeck dashboard.

Hookdeck doesn't send event payloads, headers, or other request data to Sentry.

Status changes are kept in sync in both directions:

Change in HookdeckResult in Sentry
Issue resolvedSentry issue resolved
Issue ignored or dismissedSentry issue archived
Issue reopenedSentry issue unresolved
Issue acknowledgedNo change
Change in SentryResult in Hookdeck
Issue resolvedIssue resolved
Issue archivedIssue ignored
Issue unresolvedIssue reopened, if it was resolved or ignored
Issue assignedIssue acknowledged, if it was open

Changes coming from Sentry notify the issue trigger's other channels, such as email or Slack, but aren't sent back to Sentry. Changes Sentry makes on its own, such as auto-resolving issues after a period of inactivity, don't change the Hookdeck issue.

Each Hookdeck issue sends one event to Sentry when it opens, and one more each time it reopens. These events count against your Sentry error quota.

Requirements

  • A Hookdeck plan that includes notification integrations, and the Member role or higher in the Hookdeck project.
  • Permission to install integrations in your Sentry organization. By default, this is the Owner and Manager roles.
  • A Sentry organization can be connected to one Hookdeck project at a time.

Hookdeck requests the following Sentry permissions:

PermissionUsed to
Project: ReadList your Sentry projects and find the project's client key to create issues
Issue & Event: Read & WriteCreate Sentry issues and update their status
Organization: Read & WriteRead your organization's details, and uninstall Hookdeck from your Sentry organization when you disconnect it in Hookdeck

Support

If you need help with this integration, please contact support@hookdeck.com.

Integration Walkthrough

Go to the Hookdeck dashboard and from the top-left menu, navigate to the Organization and Project you want to enable the Sentry integration within.

Within the desired Hookdeck project, go to Settings -> Integrations. Click the Connect button next to the Sentry integration listing. This opens the Hookdeck installation page in Sentry.

Sign in to Sentry if needed, select the Sentry organization to install Hookdeck in, review the requested permissions, and click Accept & Install. Once installed, Sentry redirects you back to the Hookdeck dashboard.

A Sentry Connected dialog is shown within the Hookdeck dashboard. To send issues from all your existing issue triggers to Sentry, check Attach to all issue triggers, select the Sentry Project to create issues in, and click Confirm. Otherwise, click Skip and choose the Sentry project on each issue trigger instead.

If you installed Hookdeck from Sentry rather than from the Hookdeck dashboard, Hookdeck asks you to confirm the Sentry organization before connecting it to your project.

Send an issue trigger's issues to Sentry

  1. Go to Issue Triggers and select the issue trigger.
  2. Under Notification channels, turn on Sentry.
  3. Select the Sentry Project to create issues in.
  4. Click Save.

Each issue trigger can send to a different Sentry project.

Connection Status

The Sentry listing in Settings -> Integrations shows the status of the connection:

  • Connected: Hookdeck can create and update Sentry issues. Hover the info icon to see the connected Sentry organization.
  • Degraded: Hookdeck can't reach Sentry right now. Your integration and issue trigger settings are kept, and Hookdeck keeps using the last known list of Sentry projects.
  • Expired: Sentry no longer accepts Hookdeck's access, for example because Hookdeck was uninstalled from your Sentry organization. Click Reconnect to install it again. Your issue trigger settings are kept.

How to Uninstall

Go to the Hookdeck dashboard and from the top-left menu, navigate to the Organization and Project you want to disable the Sentry integration within.

Within the desired Hookdeck project, go to Settings -> Integrations. Click the Disconnect button next to the Sentry integration listing. Click Disconnect in the dialog to confirm.

Disconnecting removes Sentry from all your issue triggers and uninstalls Hookdeck from your Sentry organization. If Hookdeck can't uninstall itself, the dashboard tells you. Uninstall it in Sentry under Settings -> Integrations -> Hookdeck instead.

You can also uninstall Hookdeck directly from Sentry. Hookdeck then shows the integration as Expired until you reconnect or disconnect it.

Troubleshooting

Sentry says Hookdeck is already installed. Hookdeck is still installed in that Sentry organization, for example after disconnecting it from another Hookdeck project. Uninstall it in Sentry under Settings -> Integrations -> Hookdeck, then connect again from Hookdeck.

No Sentry projects are available. Hookdeck couldn't find any projects in the Sentry organization. Create a project in Sentry, then connect again.

Issues don't appear in Sentry. Check that the issue trigger has the Sentry channel turned on with a Sentry project selected, that the integration isn't Expired, and that the Sentry project isn't dropping events because of rate limits, spike protection, or inbound filters.

Changelog

  • 2026-09-24: Initial release. Create Sentry issues from Hookdeck issues and sync their status both ways.

If you're not already up and running with Hookdeck, then get started with our quickstart guide.