PathwAI's Webhooks integration sends flow data to an HTTPS endpoint you control, in two ways. Ending step webhooks post the completed submission, with its answers and optionally the cart and user profile, when a respondent reaches an Ending. The Data Platform webhook destination posts each event you map, such as flow_started or purchase, signs it with HMAC-SHA256 when you set a secret, and retries failed deliveries.
What data moves
- Ending webhook: The JSON body holds the submission ID, flow ID and a timestamp, plus the answers keyed by each step's custom key. The cart and the user profile are added when you include them. Answers can be shaped as flat objects, flat primitives or a rich array.
- Webhook destination: a POST per mapped event with the event ID, name, type, timestamp, consent state and the properties a transformer allows, plus X-Pathwai-Event-Id and X-Pathwai-Timestamp headers.
- With a signing secret, an X-Pathwai-Signature header holds sha256= and an HMAC-SHA256 of the raw body.
Where it is configured
Ending step webhooks are set on an Ending step under Events → Exit, with URL, method, headers and payload options. The webhook destination is added under Data → Destinations → Webhook, with URL, custom headers and an optional signing secret.
Use cases
Completed intakes into your own systems
Post each completed intake to your EHR bridge, CRM or data warehouse loader.
Separate outcomes, separate endpoints
Give each Ending its own webhook, so qualified and not-qualified respondents go to different places.
A signed event stream
Map flow events on the webhook destination and verify each request's signature before processing it.
How to set it up
- For submissions: open the Ending step, go to Events → Exit, add a webhook, and set its URL, method, headers and payload mode.
- For events: open Data → Destinations, add Webhook, and enter the URL, headers and a signing secret.
- On the destination's Event mapping tab, add the events to send and attach transformers for any properties.
- Use the destination's test event, then switch it on.
Good to know
- Ending webhooks run on PathwAI's server once, when a respondent reaches an Ending step and the submission completes. They are not retried, and the request times out after 10 seconds, so the receiving service should answer quickly.
- The Data Platform webhook destination sends only the events you add and switch on in its Event mapping tab. With a signing secret set, each request carries an X-Pathwai-Signature header with an HMAC-SHA256 of the body, and a failed delivery is retried before it is set aside.
Webhooks integration FAQ
Which webhook should I use?
Use an Ending webhook to receive a whole submission when it completes. Use the webhook destination to receive individual events as they happen, signed and retried.
Are ending webhooks signed?
No. Add your own authorization header to the webhook. Signing with HMAC-SHA256 is a feature of the Data Platform webhook destination.
Can I choose which answers are sent?
Yes. Ending webhooks send all answers or selected fields and can exclude fields. The destination sends only the properties a transformer allows.
Want to see Webhooks in a flow?
We can walk through where Webhooks fits in your funnel and exactly which data it would receive.