Webhooks, delivered
Any webhook,
on your phone.
A hook is a URL that receives requests. zhooky pushes them to your phone, keeps them so you can read them, and runs what you want next.
Saturday
9:41
- zhookynow
#payments
POST /stripe · 33 B
- zhooky1m
#deploys
POST /github · 45 B
- zhooky4m
Backup done
3.2 GB
The journey
A request becomes a notification
Pick what is sending. The notification is the one zhooky would really produce, and the lines under it are the resolver's own account of where each field came from.
{
"amount": 4200,
"status": "failed"
}On your phone
#payments
POST /stripe · 33 B
- title
- from the hook's name
- message
- from the request line
{
"action": "completed",
"conclusion": "failure"
}On your phone
#deploys
POST /github · 45 B
- title
- from the hook's name
- message
- from the request line
{
"title": "Backup done",
"message": "3.2 GB"
}On your phone
Backup done
3.2 GB
- title
- from the body's "title"
- message
- from the body's "message"
How it works
One hook, three capabilities
A personal endpoint, a topic and an inspector URL are the same thing with different capabilities switched on.
Inbox
01Store, inspect, search and replay the requests a hook received — the whole body, exactly as it arrived.
Subscribers
02The devices that get notified when a request arrives.
Actions
03An ordered pipeline: filter, transform, then push, forward or e-mail.
Use cases
What people point at a hook
Free to start
1 hook and 100 pushes a month, with no account to create first.
The phone app is coming soon to the App Store and Google Play. Hooks, the inbox and forwarding work in the browser today.