Hookfire

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

33 services wired in, and only what really came from them

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

  • Stripe, Shopify, GitHub, Sentry, Zendesk, Paddle and 27 more
  • Every signature checked in that source's own scheme, and a timestamped one refused after five minutes
  • An unsigned request 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 the moment somebody acknowledges 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 an hour or a day, 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, and told again only when it settles back down
  • Critical alerts still come through

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.

  • Sent, failed, skipped or suppressed, with the reason, per person and per channel
  • A failed-delivery list for the integration, newest first
  • On Max, thirty days of success rate, median and slowest latency, and volume
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 retries over about an hour, then a one-press replay when you are ready

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

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 33 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
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

Try all of it for 7 days

The trial is Max, so nothing above is held back. No credit card required.

Start free for 7 days See the prices

Weighing us against something else? Read the comparisons or browse every integration