Use cases
hooksnode started as payment webhook fan-out. Today it also reads inboxes, watches URLs and turns bank alerts into events. Here is what teams build with it.
Payments
Your processor sends one callback per charge. Point Paystack, Flutterwave or Stripe at one hooksnode URL. Send each charge to your ledger, CRM, wallet service and notifications. Each destination has its own retries and filter.
paystack → hooksnode → ledger, crm, wallet
Read the Shuttlers story →Finance
Your bank sends no webhooks, but it sends an email for each credit. Connect the inbox that gets the alerts and turn on bank alerts. Each credit becomes a bank.credit.received event with the amount, reference and payer. Match it to an open invoice and send a receipt.
bank alert email → bank.credit.received → invoicing
Bank alert docs →Operations
Supplier invoices, orders and courier updates arrive as email. Connect Gmail, Outlook or any IMAP mailbox. Each new message becomes an email.received event with sender, subject, text and attachment details. Filter by sender and send it to the right team or agent.
orders@ inbox → email.received → fulfilment api
Mail source docs →Monitoring
Exchange rates, tenders, stock levels and partner APIs change with no push. Watch a URL on a schedule. hooksnode compares each response with the last one and sends an event only when something changed, with the fields that changed.
GET /rates every 5 min → http_poll.changed → pricing
Watch a URL docs →Agents
An agent can act only when it knows that something changed. Give your agent one stream of typed events from webhooks, inboxes, bank alerts and watched URLs. Filter by type and send each event to the agent endpoint, with retries if it is busy.
many sources → typed events → agent endpoint
Messaging
Add a WhatsApp source. hooksnode answers the Meta handshake and checks the signature. Send each message to your support tool and your bot at the same time. Meta retries of the same body are stored once.
whatsapp cloud api → hooksnode → helpdesk, bot
WhatsApp docs →Developers
Build against real webhooks, not samples. Run hooksnode listen 3000 and each webhook your project receives also goes to your laptop, with the original headers and body. No tunnel. Use a separate dev project so production destinations do not fire.
live events → hooksnode listen → localhost:3000
Install the CLI →Monitoring
Send each monitoring alert to Slack, PagerDuty and your incident tool at once. A Slack rate limit never stops the page, because each destination retries on its own.
monitor → hooksnode → slack, pagerduty
Use the Free plan to prove the path. Use Pro for live payment webhooks.
Start free →