Marketing Automation · Integration
Braze
Add Braze to your product for your customers, and give your AI agents governed access to it.
Embed a Braze integration so your customers can send product events into their own Braze workspace and trigger campaigns and canvases from inside your product, with governed agent access to the same data. Engagement data arrives as a high-volume event stream, so ordering and deduplication are handled for you and a retry does not message the same user twice. fastn handles each customer's API keys and upkeep, so onboarding another workspace is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Send user attributes and custom events into each customer's own Braze workspace, mapped to their taxonomy.
Trigger a Braze campaign or canvas entry from an event in your product so lifecycle messaging follows real behaviour.
Read segments and their sizes so your users can target and report inside your product.
Trigger your product on engagement events such as opens, clicks, and unsubscribes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a user's recent events and campaign history before drafting a message.
An agent triggers a campaign for a qualifying audience within governed permissions.
An agent reacts to an unsubscribe event and updates preferences in the customer's other systems.
Example prompt
Show canvases with the highest drop-off step in the last 30 days and how many users stalled there.
Set up Braze in 4 steps
- 01Open the Braze connector from your fastn dashboard.
- 02Have each customer authenticate their own Braze workspace with least-privilege REST keys.
- 03Map the user, event, and segment fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Braze integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Braze integration without building it. Your customers connect their own Braze account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Braze update is not your on-call problem.
- One integration serves your product and your agents. The same governed Braze connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Bloomreach Engagement
BitlyWorks well with
HubSpotOften used alongside
Tools the same teams tend to run next to Braze, across other categories.
Salesforce
Pipedrive
Zoho CRM
ApolloBraze integration FAQ
How do I add a Braze integration to my product?
Enable the Braze connector in your fastn dashboard, then let each customer authenticate their own Braze account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Braze client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Braze account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Braze account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Braze integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a user's recent events and campaign history before drafting a message.
Who maintains the Braze integration?
fastn does. When Braze changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Braze campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Braze?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Braze integration?
A common starting point: send user attributes and custom events into each customer's own Braze workspace, mapped to their taxonomy. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Braze integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Braze does not change your per-connector cost. You can start free with 3 connected accounts.
Add Braze to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.