Skip to main content
hooksnode listen connects to your project’s live event stream. For each webhook that the project receives, it sends a copy to a port on your computer.
The copy has the original method, path, headers and body. A provider’s signature, such as x-paystack-signature, still verifies on your machine.

​
Flags

Example: send events to your Express route.

​
What it does and does not do

  • A copy only. Your destinations still get each event. listen does not change deliveries, retries or the event log.
  • Live only. It sends events that arrive while it is connected. It does not send older events. Use replay for those.
  • Webhooks only. It sends events from webhook and WhatsApp sources. Mail and polled events do not go to listen.
  • Reconnects. If the connection drops, the CLI connects again. It waits 1 second at first, and up to 30 seconds. Events that arrive while it is not connected are not sent to your machine.
Make a separate dev project with no production destinations. Then your tests do not reach your live systems.