All integrations
Messaging

Braze

Forward mapped flow events to Braze profiles as custom events.

PathwAI's Braze integration forwards flow and submission events to Braze user profiles as custom events. It is a Data Platform destination: you paste a Braze REST API key with the users.track permission and your REST endpoint, choose which events to send and what to call them in Braze, and PathwAI delivers them from its servers through /users/track, retrying when a request fails.

What data moves

  • PathwAI to Braze: each mapped event as a custom event with external_id, your chosen event name, the original timestamp and properties.
  • Only events you map are sent, and only the properties a transformer emits. Everything else is dropped.
  • Events without an external ID are skipped, because Braze matches profiles by external ID.
  • The REST key is encrypted at rest and not shown again after saving.

Where it is configured

Data → Destinations → Braze holds the REST API key, the REST endpoint and an optional App Identifier. Event names and property transformers are set in the destination's Events tab.

Use cases

Abandoned-flow nudges

Send flow_started and flow_completed, then trigger a Braze Canvas for people who started without finishing.

Segments by flow outcome

Map a custom event on each Ending so Braze segments can tell outcomes apart.

Personalized messages

Pass the plan or product chosen as a property and use it in Liquid personalization.

How to set it up

  1. In Braze, open Settings → APIs and Identifiers, create a REST API key with the users.track permission and copy your REST endpoint.
  2. In PathwAI, open Data → Destinations, choose Braze and paste the key and endpoint.
  3. In the Events tab, add each source event with the Braze event name it should appear as.
  4. Attach a transformer to choose properties, then switch the destination on.

Good to know

  • Braze receives custom events. User attributes and Braze purchase objects are not written.

Braze integration FAQ

How does PathwAI match Braze users?

By external ID. Events without one are skipped, so make sure your flows identify the person.

Which properties reach Braze?

Only the properties your transformer emits. With no transformer, no custom properties are sent.

What if Braze is unavailable?

Delivery runs in the background and failed requests are retried.

Want to see Braze in a flow?

We can walk through where Braze fits in your funnel and exactly which data it would receive.