Sentry events, straight into Slack
Every new error, issue resolution, or assignment — posted to Slack the moment it happens. No $20+/month automation plan just to move one webhook.
Why not just use Slack's built-in options? Even where Sentry offers some form of Slack integration, it's often tied to one account, limited in which events it covers, or more than you need. ZestyGlue is a dedicated, always-on feed of exactly the events you choose, for $9/month instead of a full automation-platform subscription.
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 Slack.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Sentry → Slack 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 Slack at ZestyGlue. Create a Slack app (or reuse one) → Incoming Webhooks → Add New Webhook to Workspace, pick the channel, and copy the URL into ZestyGlue.
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.
Does this need Slack admin approval?
No app installation is required on Slack's side — an Incoming Webhook is just a URL generated once. No OAuth review, no admin approval flow.
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.