Sentry events, straight into Custom Webhook
Every new error, issue resolution, or assignment — posted to Custom Webhook the moment it happens. No automation-platform subscription just to relay one webhook.
Why not call Sentry's API directly from your own endpoint? You can — but then you own Sentry's signature verification, retry handling, and payload quirks yourself. ZestyGlue verifies the signature, normalizes the event into a clean JSON body, and POSTs it to your URL — you only write the part that's actually yours.
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 Custom Webhook.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Sentry → Custom Webhook 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 it at your endpoint. Paste the URL of your own server, script, or automation tool's webhook receiver — no signup, no app to install.
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 write my own server to receive this?
Yes — this destination expects your own endpoint (or a tool like a serverless function, a script, or another automation platform's webhook trigger) to receive the POST. If you don't have one yet, pick one of ZestyGlue's built-in destinations instead.
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.