PathwAI's Customer.io integration is a destination listed in the Data Platform catalog, where it is locked and cannot be switched on from a workspace. Teams using Customer.io can send PathwAI data through webhooks: the Data Platform webhook destination posts each mapped event to an HTTPS endpoint you run, and an Ending step webhook posts each completed submission. That endpoint passes the data to Customer.io with your credentials.
What data moves
- Webhook destination: one request per mapped event, with the event name, timestamp, consent state and the properties a transformer allows.
- 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.
- Your endpoint to Customer.io: whatever it builds from those payloads.
Where it is configured
The Customer.io card appears under Data → Destinations, marked locked. The webhook destination is under Data → Destinations → Webhook, and Ending step webhooks are under the Ending's Events → Exit.
Use cases
Journeys from flow events
Forward flow_started and flow_completed so Customer.io can follow up with people who did not finish.
Onboarding after intake
Use the Ending webhook to pass a completed intake's contact details to Customer.io.
How to set it up
- Run an HTTPS endpoint that accepts JSON and calls Customer.io.
- In PathwAI, add a Webhook destination under Data → Destinations with that URL and a signing secret.
- Map the events to send and switch the destination on.
- Ask PathwAI about the Customer.io destination if you want PathwAI to deliver events.
Good to know
- 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.
Customer.io integration FAQ
Does PathwAI send events to Customer.io directly?
Not today. The Customer.io destination is locked in the catalog. Events reach Customer.io through an endpoint you run.
Which events can I forward?
The built-in flow events, custom Data Platform events and website SDK events you map on the webhook destination.
Can I verify the requests?
Yes. With a signing secret set, each request carries an X-Pathwai-Signature HMAC-SHA256 header.
Want to see Customer.io in a flow?
We can walk through where Customer.io fits in your funnel and exactly which data it would receive.