Braze on Make Enterprise
Braze is a marketing automation platform. Audiences, campaigns, email and journeys, fed by data from the rest of the business. Here is what Make lists for it, what we build around it, and what to settle before you automate it.
What does Make list for Braze?
Make's page lists 9 actions, 2 searches by name.
Actions
- Create a catalog
- Create or update a catalog item
- Create or update a user profile
- Delete a catalog
- Delete a catalog item
- Get a catalog item
- Make an API call
- Send a campaign message
- Send a canvas message
Searches
- List catalog items
- List catalogs
Module lists change as Make updates the app. Treat this as a snapshot and confirm on Make's page before you scope work.
What do we build around Braze?
These are the kinds of scenarios we build for marketing automation. They describe our work, not features of Braze.
- Audience and consent syncs from the CRM and product data
- Campaign and lead-score hand-offs back to sales
- Event streams into the warehouse for reporting
- Suppression and unsubscribe handling shared across tools
Example flows
- A lead that reaches a score threshold becomes a task for the owner in the CRM
- An unsubscribe in one tool updates the suppression list everywhere
- Campaign engagement flows into the warehouse each day
What should you settle before automating Braze?
Settle these before the first production scenario so builders can start without waiting on a later security review.
- Where consent and suppression live, and that every tool reads the same list
- Which scenarios may send, and which only prepare audiences
- How a failed sync is surfaced before a campaign goes out
- Who approves a new field mapping
Platform-level controls such as SSO, roles, encryption and log retention are Make's own published terms; see make.com/security and our Make Enterprise page for how we scope against them. Make describes the Enterprise plan itself at make.com/enterprise.
Frequently asked questions
Can Make connect to Braze?
Yes. Make has a Braze app, and its page states that it is supported and maintained by Make. It is listed in Make's Enterprise integrations category. The modules and names on this page are what Make shows on its own Braze page as of November 5, 2026, so check Make's page for the current list.
What do you build around Braze?
We build the scenarios around it: audience and consent syncs from the CRM and product data; campaign and lead-score hand-offs back to sales; event streams into the warehouse for reporting. Scope is set on a call, and each scenario is documented in plain language before hand-over.
What should we decide before automating Braze?
Start with the guardrails: where consent and suppression live, and that every tool reads the same list; which scenarios may send, and which only prepare audiences; how a failed sync is surfaced before a campaign goes out. Settling these first lets builders start without waiting on a security review later.
Does the connection need Braze admin access?
That depends on what the scenarios do and on Braze's own permission model. We aim for a dedicated service account with the narrowest role that works, and we record which scenarios write and which only read. Your Braze administrator decides what that account may reach.
Consultants in a Box is a Make partner. This page is written by us and is not published by Make or by Braze's vendor. Braze, Make and related names are trademarks of their owners. Statements about Make's platform are the ones Make publishes.
Planning to automate Braze?
Book a call. We map your systems to the pages here, agree the guardrails and give you a written scope and price afterwards.