Connect Braze
Send events and user attributes through a trigger.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
api_key | REST API key with users.track permission. |
rest_endpoint | The REST endpoint for your Braze region, without /users/track. |
Connect
Open Integrations, find Braze, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create the REST key in Braze Settings → APIs and Identifiers. Copy the REST endpoint for the same workspace.
- Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
Verify the result
The check POSTs an update-existing-only probe for vibetag_test_no_op. It can touch that existing profile; it is not an email send. AXO treats a 400 response as authenticated, so inspect the detail and verify a real intended event separately.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Use the workspace’s regional REST host. A 401 indicates credentials; a 403 indicates permissions. A green authentication probe does not validate your event template.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Provider reference: Braze users/track permissions and payloads. Reviewed October 2026.
Next: create an event-triggered action, or implement a webhook receiver.