Skip to main content
Webhooks go both ways, and each direction is part of an automation rather than a subscription you configure separately.

​
Your service calls HERO

Post to an automation’s webhook URL and it runs, with whatever JSON you sent readable by its steps. See Starting a workflow from your own service for the URL, the secret, what you may post and how a step reads it.

​
HERO calls your service

Add a Send a webhook step to an automation. It posts to any HTTPS URL you name, with a body you write — so what HERO sends is whatever that workflow decided, rather than a fixed event schema. Because the body is a normal text field, it can carry anything the run knows: what triggered it, what an earlier step produced, or a value read from a table. A few things worth knowing about the outbound direction:
  • HTTPS only. The URL is resolved before the request and the connection is pinned to the addresses that resolved, so a hostname that later points somewhere else cannot redirect the call.
  • Every send is recorded on the run, because a request that has left HERO cannot be undone.

​
Stripe

HERO consumes Stripe’s own webhooks at POST /api/webhook/stripe for subscription and invoice events. That endpoint is for billing and is not related to automations.