Get your URL
Create a free account. You get a personal hook URL, your identifier and your key. That URL is your notification address.
How Hook.Notifier works
You get a personal URL. You call it from anything. A real notification lands on your phone. That is the whole product, and it takes a minute to start.
Call it
Send an HTTP request to your URL from anything: a shell script, a webhook from Stripe or GitHub, a Zapier or Make automation, or a few lines of code.
Get notified
A real native notification lands on your phone through the mobile app, and in your browser inbox. It stays there, tagged and searchable.
The whole thing, in one line
Anything that can make an HTTP request can notify you. A browser, a script, a webhook, a no-code automation.
curl "https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=Hello&body=My first notification"What you do not have to build
A Firebase project
Apple push certificates
A backend to store device tokens
A mobile app to receive them
Hook.Notifier already is the app, the inbox, and the delivery. You just call your URL.
It does more than ping
Priorities and quiet hoursSend priority=low for silent logs, critical for alerts that break through your quiet hours. Everything else waits for the morning.
Any webhook, no middlemanA named hook per source with a payload template turns raw Stripe or GitHub JSON into a readable notification.
Notifications that updateThe send returns an id. PUT the same URL with that id and the notification updates in place, on the device too.
Scheduled sendsAdd delay=10m or at=tomorrow to be notified later. Reminders in one curl, up to three days ahead.
Markdown, images, buttonsBold what matters, attach an image, add up to three action buttons that open the right page in one tap.
Outgoing webhooksRelay what you receive to Slack or any other tool. Hook.Notifier is a two-way bridge, not a dead end.