Features
Every Hookfire feature, in the order an event moves through the app, with the plan that includes it.
01 · Receive
Payments, ecommerce, billing, developer tools and support, each one already mapped event by event.
Each event has a title, a body and a link written for it, filled in from the payload as it arrives.
02 · Decide
Say which events are worth a notification, in the same dot paths the templates use.
Say how urgent each event is, and let the urgent ones behave like it.
A busy shop should not make your phone unusable at night, and silence should never cost you the record.
03 · Deliver
One event, delivered wherever the person who has to act on it is looking.
Cap how many events an hour an integration may interrupt anyone for, and relax.
Up to three link buttons on a notification, and the product photo or avatar that came with the event.
Not every event needs to interrupt someone the second it arrives.
04 · Operate
Every notification keeps its own outcome, so "did it send?" is never a guess.
The stored payload is still there, and a source that quietly stops is the failure nobody notices.
Let Hookfire be the door every webhook comes through, and keep your own systems fed behind it.
05 · Ask
Hookfire runs an MCP server, so an assistant such as Claude or ChatGPT can read your notifications and act on them, as you.
Send a real sample payload through the whole pipeline and watch it land.
Pro and Max
iOS, Android and a browser inbox that updates while you are looking at it.
Pro and Max
Describe your own source once, and it renders like any built-in one.
Max
Pick the recipients for each event, and push or inbox for each of them.
Max
Roles, so an invitee is not an admin the moment they accept. Pro: two people, both admins.
Max
Give an event 5 minutes to a day. An alert that cannot go out in time is not pushed, emailed or posted, and still lands in the inbox.
Max
Pro keeps thirty days. Max keeps everything, and hands it back.
Max
| Feature | Pro | Max |
|---|---|---|
| Integrations | 3 | Unlimited |
| Events per month | 2,000 | Unlimited |
| Events per integration | Unlimited | Unlimited |
| Team members | 2 | Unlimited |
| Notification history | 30 days | Unlimited |
| All 55 built-in sources | ||
| Signature verification, in each source's own scheme | ||
| Push notifications and web inbox | ||
| Tap a notification through to the event in the source | ||
| Test events | ||
| Delivery outcome recorded for every notification | ||
| Quiet hours, snooze and per-integration mute | ||
| Team roles | Everyone is an admin | Admins and members |
| Filter rules that read the payload before anyone is woken | ||
| Priorities, with critical alerts repeating until acknowledged | ||
| Choose who gets each event, push or inbox per person | ||
| Email notifications | ||
| Slack, Discord and Microsoft Teams channels | ||
| Link buttons and pictures, on Android, in email and in chat | ||
| An icon of your own for each integration | ||
| Deliver a notification later, up to 7 days ahead | ||
| Notification expiry: stale alerts are dropped instead of arriving late | ||
| One summary instead of a burst, during spikes or always | ||
| Rate cap and spike protection per integration | ||
| Delivery analytics: success rate, latency and volume | ||
| Told when an integration that was delivering goes quiet | ||
| Replay a recorded delivery | ||
| Rewrite what a built-in source's notifications say | ||
| Forward verified webhooks on to your own endpoints | ||
| Custom webhook sources | ||
| CSV export | ||
| MCP server for AI assistants |
The trial is Max, so nothing above is held back. No credit card required.
Weighing us against something else? Read the comparisons or browse every integration