Sentry events, straight into ntfy
Every new error, issue resolution, or assignment — posted to ntfy the moment it happens. No ntfy app to install, no monthly automation subscription.
The gap this fills: Sentry doesn't ship an official ntfy app. If you want new error, issue resolution, or assignment to show up in ntfy the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
ZestyGlue
Sentry — Issue.Created
TypeError: Cannot read property of undefined
checkout.js in processPayment
level: error
A real Sentry event, shown as ZestyGlue formats it for ntfy.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Sentry → ntfy connector. You'll get a unique webhook URL right away.
- Point Sentry at it. Go to Settings → Developer Settings → Create New Integration → Internal Integration, add a Webhook URL pointing to your ZestyGlue webhook URL, and check the resource subscriptions you want (e.g. Issue).
- Copy the Client Secret. Sentry generates a Client Secret for your internal integration — paste that into ZestyGlue's connector setup so every event can be verified as genuinely from Sentry.
- Point ntfy at ZestyGlue. Pick any topic name — e.g.
https://ntfy.sh/your-secret-topic — enter it into ZestyGlue, and subscribe to that same topic in the ntfy app or web client.
Tip: Sentry's internal integrations are per-organization, so create one that subscribes to just the resources you care about (usually Issue) to avoid a noisy channel from every comment and assignment change.
Events you can forward
issue created
issue resolved
issue assigned
comment created
Questions
Is my Sentry Client Secret safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Does this replace Sentry's own Slack or email alerts?
No — it runs alongside anything else you have configured. It's useful for routing Sentry alerts into a destination Sentry doesn't natively integrate with, like Telegram, ntfy, or a Notion log.
Can I filter to only certain error levels?
Not at the ZestyGlue level — Sentry sends every event for the resources you subscribe to in the internal integration. Scope which resources you subscribe to on Sentry's side instead.
Do I need to self-host ntfy?
No, the free public ntfy.sh server works fine for most people — just pick an unguessable topic name.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Sentry's side — Sentry never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.