Resources · Make integration

Braze Make integrationAutomate Braze with Make.

Can Make keep Braze fed without a developer? The Braze Make integration gives you 11 modules: 9 actions and 2 searches for user profiles, catalogs and message sends. This page shows how to link your account and build a first working flow, step by step.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Braze integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Braze Make integration do for you?

The Braze Make integration lets data from your other tools land in Braze, and lets Braze send messages, without writing code. In Make you build a scenario, the automation itself: a chain of modules, where each module is one brick that does one job, like updating a profile or sending a campaign. Braze offers no trigger here, so another app or a schedule starts the chain.

Profiles that stay current. When a customer signs up in a form tool or buys in your shop, Create or update a user profile writes the attributes, the event or the purchase to the right Braze user. Your segments then match what really happened.

A product catalog you never edit by hand. A spreadsheet or a database row changes, and Create or update a catalog item pushes the new price or stock level into the Braze catalog. List catalog items helps you check what is already there before you write.

Messages sent at the right moment. A support ticket closes or an order ships in another app, and Send a canvas message or Send a campaign message fires the matching Braze message.

Two limits to know before you start. Braze is an Enterprise app in Make, so it only runs on the Enterprise plan (the Make pricing page explains the plans), and it needs a paid Braze account. Braze also has no trigger module, so Braze events cannot start a scenario directly. Braze often has an n8n node too; the n8n vs Make comparison helps you pick a tool. New to the editor? The Make training starts from zero.

Connect

How do you connect Braze to Make?

  1. 01

    Create an API key in Braze

    In Braze, open Settings > APIs and Identifiers and click Create API Key. Give the key a name, tick all the permissions, save it, then copy the value from the Identifier column somewhere safe.

  2. 02

    Open the connection window in Make

    Add any Braze module to your scenario and click Create a connection. A connection is your Braze account linked to Make once; every Braze module in every scenario reuses it afterwards.

  3. 03

    Pick the instance and paste the key

    In Braze Instance, choose the instance your account lives on. Paste the key into API key, optionally name the connection, and click Save. Confirm access if Braze asks you to.

First scenario

Your first scenario: signup to welcome canvas

GoalWhen a new lead arrives in another app, Make updates the Braze profile and sends the welcome canvas.

  1. 01

    Start a new scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where leads arrive, such as your form tool, as the first module.

  2. 02

    Add the Braze profile module

    Click the + on the right, search Braze and choose Create or update a user profile. Select your connection, then map the email or name coming from the first module into the profile.

  3. 03

    Send the welcome canvas

    Add Send a canvas message after it and pick the canvas you prepared in Braze. Map the same user so the message reaches the profile you just updated.

  4. 04

    Test with Run once

    Click Run once and submit a test lead. Each module shows the bundles it received, one bundle being one item, here one lead. Check the profile in Braze before going further.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.

Modules

What each Braze module does

Braze gives you 11 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Users

4 modules
Braze1

Create or update a user profile

Action

In Make“Creates or updates attributes, events or purchases for a user profile given its Braze ID, external ID or user alias.”

This module keeps a Braze user in step with the rest of your stack: it writes attributes, events or purchases to one profile, created on the spot if it does not exist yet. You find the user by Braze ID, external ID or user alias.

When to use it
a purchase lands in your shop tool and should reach Braze as a purchase on the buyer's profile.
Watch out
use the same identifier everywhere, or the same person ends up as two profiles.
Braze2

List catalogs

Search

In Make“Gets a list of all catalogs.”

Returns every catalog in your Braze workspace, each one as its own bundle, so later modules can loop over them or pick one by name. Nothing gets changed, it only reads.

When to use it
before creating a catalog, to check the name is not already taken by a teammate's catalog.
Watch out
a search can return zero, one or many bundles; add a filter so the next module only receives the catalog you want.
Braze3

Create a catalog

Action

In Make“Creates a new catalog.”

Gives you a brand new, empty catalog in Braze, ready to receive items from a spreadsheet, a database or a product feed handled in the same scenario.

When to use it
a new product line or a seasonal collection needs its own catalog for personalized messages, and you want the setup repeatable.
Watch out
run it once per new catalog, not on every bundle, or the scenario will try to create the same catalog again and again.
Braze4

Delete a catalog

Action

In Make“Deletes a catalog given its name.”

Removes a whole catalog from Braze, identified by its name, which keeps your workspace free of catalogs nobody uses anymore.

When to use it
a temporary collection has ended and the messages that referenced it are retired.
Watch out
treat the deletion as final. Test it with Run once on a throwaway catalog before pointing it at real data, and double check the name you map.

Catalog items

4 modules
Braze5

List catalog items

Search

In Make“Gets a list of items inside a given catalog.”

Reads the items stored in one catalog and hands them to the next module as separate bundles, so you can compare them with your source or export them elsewhere.

When to use it
you want to spot items that exist in Braze but no longer exist in your product sheet.
Watch out
every returned item becomes a bundle, and each module after it spends one operation per bundle, so filter early on large catalogs.
Braze6

Get a catalog item

Action

In Make“Gets a catalog item given its ID.”

Fetches a single catalog item from its ID and gives you its current values to reuse downstream, for example in a report or a check before an update.

When to use it
you already know the item ID and need only that one item rather than the full list.
Watch out
the ID must match exactly what Braze stores; a typo or an extra space sends the module looking for an item that does not exist.
Braze7

Create or update a catalog item

Action

In Make“Creates or updates a catalog item given its ID.”

Your catalog stays aligned with the source of truth: this module writes one item from its ID, creating it when the ID is new and updating it when it already exists.

When to use it
a row changes in the spreadsheet or database that holds your products, and the new price or stock should reach Braze.
Watch out
pick a stable ID from your source, such as the SKU, so updates never create duplicates.
Braze8

Delete a catalog item

Action

In Make“Deletes a catalog item given its ID.”

Takes one item out of a catalog by its ID, so messages stop recommending a product you no longer sell.

When to use it
a product is discontinued in your shop or marked as archived in your database, and the change should follow in Braze.
Watch out
like any delete, this does not come back. Map the ID from the event that removed the product, never from a broad list, to avoid emptying the catalog.

Messages

2 modules
Braze9

Send a campaign message

Action

In Make“Sends a message from a given campaign.”

Triggers the message of an existing Braze campaign from your scenario, so a business event in another app can reach the customer through the channel set up in that campaign.

When to use it
an order is marked as shipped in your back office and the shipping campaign should go out.
Watch out
the campaign content is built in Braze, not in Make; prepare and review it there first, then pick it here.
Braze10

Send a canvas message

Action

In Make“Sends a message from a given canvas.”

Starts the message of a Braze canvas, the multi-step journey, from an event outside Braze, so the journey starts from what the person just did.

When to use it
a trial account is created in your product and the onboarding canvas should start for that person.
Watch out
update the profile first with Create or update a user profile so the canvas has fresh data to personalize with.

Other

1 module
Braze11

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Your way out when the ten other modules stop short: it calls any endpoint of the Braze API with the connection you already set up, so there is no second login to manage.

When to use it
you need a Braze feature that has no dedicated module in the list above.
Watch out
you write the request yourself from the Braze API documentation, so test it with Run once and read the response before trusting it. If you get stuck, Make troubleshooting covers the common errors.
Need help

Need help automating Braze with Make?

A person reads every message.

FAQ

Braze and Make: common questions

01Is the Braze Make integration free?
No. Braze is an Enterprise app in Make, which means its modules only run on the Enterprise plan. The Free plan still covers the 3,000+ standard apps, with 2 active scenarios and a minimum of 15 minutes between scheduled runs, but Braze is not part of it. You also need a paid Braze account; Braze offers a free 14-day trial account if you want to test before talking to their sales team.
02What do you need to connect Braze to Make?
You need three things: a paid Braze account, an API key, and the name of the Braze instance your account is hosted on. Create the key in Braze under Settings, APIs and Identifiers, select all the permissions, and copy the value from the Identifier column. In Make, click Create a connection on any Braze module, choose the instance, paste the key and save. The optional IP allow list must not block Make.
03Can a Braze event start a Make scenario in real time?
No, not with this app. Braze has no trigger module in Make, so nothing in Braze can start a scenario directly. The scenario starts from something else: a trigger from another app, such as your form tool or your shop, or the schedule on the first module, which runs every 15 minutes by default. On a paid plan the minimum interval between scheduled runs drops to 1 minute. Braze modules then come after that first step.
04What if the Braze module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the Braze API with the connection you already created, so you can cover what the 10 other modules do not, whether that is a user action, a catalog task or a message type. You write the request from the Braze API documentation and check the answer with Run once. The only limit the doc lists is the plan: Braze needs the Enterprise plan in Make.
05Should you use Make or n8n for Braze?
It depends on your setup. On the Make side, the hard fact is the plan: Braze runs only on Make's Enterprise plan and requires a paid Braze account. Braze often has an n8n node as well, so check both sides against the actions you need, such as profile updates, catalog items and canvas sends. This page does not rank the two tools; the n8n vs Make comparison linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations