Sentry issues as push notifications
July 23, 2026 · 3 min read
Sentry emails are easy to ignore and its mobile app notifications drown among all the others. A webhook alert rule pointed at Webhooky gives production errors their own unmistakable sound on your phone.
Setup
- Create an endpoint in the Webhooky app (Android / iOS) – “Sentry”, sound
error_2, default text like “New issue in production”. - In Sentry enable the webhook integration: Settings → Integrations → WebHooks, and enter your endpoint URL as the callback.
- Create an alert rule: Alerts → Create Alert → Issues, condition e.g. “a new issue is created”, action “Send a notification via WebHooks”.
What arrives on your phone
Sentry's legacy webhook payload carries the error's message and metadata; where present, Webhooky shows it as the notification text, otherwise your endpoint's default texts apply. Either way the point is the sound: your catch-block noise is different from your marketing noise.
Tuning tips
- Only what matters: scope the alert rule to
level:errorand above, or one rule per project with different endpoints/sounds. - Rate limits: set the rule's action interval (e.g. at most every 30 minutes per issue) so an error storm doesn't become a push storm.
- Self-hosted Sentry works identically – the WebHooks integration is part of the open-source build.
Not using Sentry? The same pattern works with a plain catch block in your own code.
Get Webhooky
Free for your first 100 notifications – set up your endpoint in two minutes.
