Guides · Sentry
Get a Mac notification for new Sentry issues
A Sentry internal integration can call a webhook when an issue is created, resolved or assigned. EventBar gives each a switch and shows the issue title in the notification.
Needs: the free EventBar app on your Mac, an EventBar account, and a Sentry account with permission to add webhooks. About five minutes. Generic JSON.
Steps
- Create the webhook URL. In the EventBar dashboard, open the Webhooks tab, pick the group this belongs to (one group per site or app is the usual shape), choose the provider Generic JSON, name it, and press Create. Copy the URL; it stays visible and can be rotated any time.
- Paste it into Sentry. In Sentry: Settings, then Developer Settings, then Create New Integration (internal). Set the Webhook URL to your hook URL and enable the issue webhook. Create the EventBar hook as Generic JSON with type field
action, so you getcreated,resolved,assigned. - Trigger one. Most services offer a test delivery; otherwise do the real thing once. It shows up in the dashboard's Events tab within a second and in the menu bar, as an undefined type named after the event. That first one is your proof the wiring works.
- Make it read well. Press Define on the new type and give it a title and a body template. Fields come from the payload, nested ones with dots. The table below is a starting point.
What you'll see
| Type | Title | Body template |
|---|---|---|
created | New issue | {data.issue.title} · {data.issue.culprit} |
resolved | Resolved | {data.issue.title} |
assigned | Assigned | {data.issue.title} |
Every type has its own switch in the menu bar, so a noisy one can be quiet on this Mac and still counted. Counts cover the last hour, 24 hours, 7 days, 30 days and all time.
Worth knowing
- Link template
{data.issue.permalink}opens the issue from the notification. - Prefer a default type of
sentryplus a body of{action}: {data.issue.title}if you'd rather have one switch for all Sentry traffic. - The older Sentry webhooks plugin posts a flat payload (
{project_name},{message},{url}) with no action field; use a default type with it.
The full contract, including how each preset reads a payload and what the answers mean, is in the API docs. Something about Sentry's payload changed? Tell us and we'll fix the guide.