To get a push notification from Sentry, add a webhook action to a Sentry alert rule and point it at your Hook.Notifier URL. When a new error appears in production, it lands on your phone right away.
Sentry is excellent at catching and grouping errors. The gap is the delay between an error happening and you noticing. Hook.Notifier closes it with a native push.
Add the webhook action in Sentry
- In Sentry, open your project and go to Alerts → Create Alert.
- Choose an Issues alert.
- Set the condition, for example A new issue is created, or The issue is seen more than N times in a period.
- Under Then perform these actions, add Send a notification via a webhook (an Internal Integration with a webhook URL).
- Point the webhook at your Hook.Notifier URL:
https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=New%20Sentry%20error&body=A%20new%20issue%20was%20created%20in%20production&tags=errors&priority=high
- Save the rule and trigger a test error to confirm the push.
First get your URL
Your Hook.Notifier URL is https://hooknotifier.com/{IDENTIFIER}/{KEY}. Create a free account to get yours, then use it as the webhook target in Sentry.
Tune the noise
Error alerts are useless if they fire constantly. Two habits keep them useful:
- Alert on new issues and on spikes, not on every event. A known error hitting once more is not news.
- Route to a dedicated tag like
tags=errorsso you can mute it during a deploy and un-mute after.
Use priority=high for production and priority=normal for staging, so a real user-facing error is louder than a noisy test environment.
Why it matters
The first minutes of a new production error are when a fix is cheapest, before it spreads and before users start leaving. A push that reaches your phone the second Sentry catches it buys you those minutes.
New to this? Start with how to send yourself a native push notification, or see get notified when a GitHub build fails.