Features

From webhook received to notification delivered

Every Hookfire feature, in the order an event moves through the app, with the plan that includes it.

01 · Receive

Pro and Max

55 services wired in, each signature checked in its own scheme

Payments, ecommerce, billing, developer tools and support, each one already mapped event by event.

  • Stripe, Shopify, GitHub, Sentry, Zendesk, Paddle and 49 more
  • Every signature checked in that source's own scheme, and most timestamped ones refused once they are five minutes old
  • Once its signing secret is in, a request with a missing or wrong signature is turned away: nothing stored, nothing sent, nothing forwarded
Pro and Max · editing on Max

Notifications written by a person, not dumped JSON

Each event has a title, a body and a link written for it, filled in from the payload as it arrives.

  • Amounts, dates, array sizes and first lines formatted for you
  • On Max, rewrite the title, body and link of any built-in event, per integration
  • A rewrite that breaks on a real payload falls back to the built-in wording

02 · Decide

Max

Rules that read the payload before anyone is woken

Say which events are worth a notification, in the same dot paths the templates use.

  • Twelve operators: is, is not, greater or less than, contains, is present, is one of
  • Match every rule, or any one of them
  • An event a rule turns away is dropped, not filed away to read later
Max

Critical alerts keep asking until someone answers

Say how urgent each event is, and let the urgent ones behave like it.

  • Low, normal, high and critical, each mapped to how the phone should interrupt
  • A critical alert repeats every five minutes, up to six times
  • It stops for each person as soon as they open or acknowledge it, in the app or over the API
Pro and Max

Quiet hours, snooze and mute, and nothing is lost

A busy shop should not make your phone unusable at night, and silence should never cost you the record.

  • Quiet hours per person, in your own timezone, running through midnight if you like
  • Snooze yourself for 1 to 24 hours, or mute one integration for the whole team
  • The event still lands in the inbox, saying why the push was held back

03 · Deliver

Pro and Max · email and chat on Max

Your phone, your inbox, and the channel your team watches

One event, delivered wherever the person who has to act on it is looking.

  • Push to iOS and Android, and a live inbox in the browser
  • Email, and posts to Slack, Discord and Microsoft Teams, on Max
  • Tap a notification and land on the charge, the order or the commit itself
Max

A noisy integration goes to the inbox, not in the bin

Cap how many events an hour an integration may interrupt anyone for, and relax.

  • Over the cap the event is still received, rendered and recorded; only the push waits
  • Admins are told once per spike, not once per event
  • Critical alerts still come through
Max

Buttons to act on, and a picture of what happened

Up to three link buttons on a notification, and the product photo or avatar that came with the event.

  • On Android, in email, and in Slack, Discord and Teams posts. iOS shows the notification without them for now
  • Give each integration an icon of its own, by link or by upload
  • A button whose link does not come out as a proper web address is left off, and the rest still go
Max

Held for later, or folded into one summary

Not every event needs to interrupt someone the second it arrives.

  • Hold an event for a set number of minutes, or let your own source's sender pick the time, up to seven days ahead
  • Everything waiting is listed in the history, with a Cancel button
  • During a spike, or always, one summary every 5 to 60 minutes instead of a push per event. Critical alerts are never held or summarised

04 · Operate

Pro and Max · analytics on Max

See what arrived, what did not, and how fast

Every notification keeps its own outcome, so "did it send?" is never a guess.

  • Every notification's outcome is recorded, and your inbox says when and why a push was held back
  • A list of the notifications that did not arrive, per person, with the reason
  • On Max, thirty days of success rate, median and slowest latency, volume, and a breakdown of what was sent, refused or held back
Max

Send one through again, and hear about the ones that stop

The stored payload is still there, and a source that quietly stops is the failure nobody notices.

  • A replay runs the kept payload through today's wording and today's subscriptions
  • Hookfire says up front when a replay would notify nobody, instead of doing nothing
  • Set the gap that counts as silence, and be told when an integration goes quiet
Max

Pass the verified stream on to your own endpoints

Let Hookfire be the door every webhook comes through, and keep your own systems fed behind it.

  • The body byte for byte, signed with HMAC-SHA256 over the timestamp and the payload
  • HTTPS only, public addresses only, re-checked and pinned before every request
  • Eight tries over about an hour, then a one-press replay when you are ready

05 · Ask

Max

Ask your AI assistant what came in

Hookfire runs an MCP server, so an assistant such as Claude or ChatGPT can read your notifications and act on them, as you.

  • "How many payments failed this week?" It counts events per integration and event type, up to 90 days back
  • "What was in that order?" It opens a notification with the values Hookfire read and its link, just as the app shows it
  • "Mark the Stripe ones read" or "acknowledge that alert", so a critical alert stops repeating for you
  • "Send a test charge.failed" or "mute Sentry for two hours". It is for organization admins
  • Paste the server URL into Claude, ChatGPT, Claude Code, Cursor or another MCP client, sign in and approve. A client that cannot sign in takes a personal token from your settings

Also included

Test events

Send a real sample payload through the whole pipeline and watch it land.

Pro and Max

Apps and web inbox

iOS, Android and a browser inbox that updates while you are looking at it.

Pro and Max

Custom webhook sources

Describe your own source once, and it renders like any built-in one.

Max

Who gets what

Pick the recipients for each event, and push or inbox for each of them.

Max

Admins and members

Roles, so an invitee is not an admin the moment they accept. Pro: two people, both admins.

Max

Notification expiry

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

Unlimited history and CSV export

Pro keeps thirty days. Max keeps everything, and hands it back.

Max

Compare plans

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

Try all of it for 7 days

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