Resources · Make integration

Braintree Make integrationAutomate Braintree with Make.

What can Braintree do inside Make without a developer? The Braintree Make integration gives you 10 modules: 2 triggers, 6 actions and 2 searches around customers and transactions. This guide is for merchants and ops teams, and it walks you from the connection to a first working scenario.

Try the Braintree integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Braintree Make integration let you automate?

The Braintree Make integration links your Braintree merchant account to Make, a visual tool where you chain apps together without code. Make reads your new customers and transactions, then creates, updates, looks up or deletes customer records for you, so payment data reaches the rest of your stack on its own.

Welcome every new buyer. Watch New Customers spots each customer added in Braintree, and the next module can push that person into your CRM, a mailing list or a shared sheet. Nobody copies names by hand anymore.

Keep a clean payment log. Watch New Transactions picks up fresh transactions, and Get a Transaction pulls the full record when you need more detail. Finance gets one tidy list instead of exports.

Keep customer records in sync. When a client changes details in your own tools, Search Customers finds the matching Braintree profile and Update a Customer rewrites it. Create a Customer covers the people who do not exist yet.

What Make does not give you here: there is no instant trigger, so both triggers run on a schedule, and there is no generic Make an API Call module. For anything outside the ready-made modules, Execute a GraphQL Query is the way in. If you are still weighing your tools, the n8n vs Make comparison lays out the differences, the Make review walks through the editor, and Make pricing explains how operations are billed.

Connect

How do you connect your Braintree account to Make?

  1. 01

    Collect your API keys in Braintree

    In Braintree, click the gear icon at the top right, choose API, then scroll down to API Keys. Copy the Environment and the Public key. For the Private key, click View in its column first, then copy it.

  2. 02

    Open the connection window in Make

    Add any Braintree module to your scenario and click Create a connection. A connection is your Braintree account linked to Make once and then reused by every Braintree module. The Connection name field is optional but handy.

  3. 03

    Paste the credentials and save

    Enter the Environment, Public key and Private key you copied, or follow the on-screen instructions, then save. Make can now read your Braintree data and fill the module fields with what it finds in your account.

First scenario

Your first scenario: turn each sign-up into a Braintree customer

GoalWhen someone signs up in another app you use, Make creates the matching customer in Braintree.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. A scenario is the automation you build: a chain of modules, each one a single brick like a trigger or an action.

  2. 02

    Start from your sign-up tool

    Pick the trigger of the app where people sign up, such as your form tool or CRM, and create its connection. This first module starts the scenario each time a new sign-up shows up.

  3. 03

    Add Create a Customer

    Click the + on the right, search for Braintree, choose Create a Customer and click Create a connection if your account is not linked yet. Map the sign-up details into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module and read the bundles it received: a bundle is one item passed along, here one new customer.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default on a new scenario. Then switch the scenario on so it keeps running without you.

Triggers

What can start a Braintree scenario?

2 modules start a scenario when something happens in Braintree. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Braintree as soon as it happens.

Braintree1Watch New Customers

Watch New Customers

Scheduled trigger

In Make“Watches for new customers.”

Watch New Customers hands you every customer freshly added to your Braintree account, one bundle per person, ready to flow into the next module. It is the natural starting point when a new buyer should show up somewhere else without anyone retyping the record.

How it fires
this is a scheduled trigger, so Make checks Braintree on the scenario's schedule rather than being alerted the moment a customer is created.
When to use it
onboarding flows, such as adding each new buyer to a CRM, a welcome email list or a customer sheet shared with support.
Watch out
on the Free plan the shortest interval between two runs is 15 minutes, so plan for that gap before promising instant follow-ups.
Braintree2Watch New Transactions

Watch New Transactions

Scheduled trigger

In Make“Watches for new transactions.”

Watch New Transactions turns each new Braintree transaction into a bundle your scenario can log, report on or route to finance. You get a steady feed of payment activity out of Braintree, without exporting anything by hand.

How it fires
scheduled. Make polls Braintree on the scenario's schedule and collects the transactions that appeared since the previous check.
When to use it
building a payment log in a spreadsheet, alerting a team channel about sales, or feeding an accounting tool with fresh entries.
Watch out
each transaction is its own bundle, and every module after the trigger runs once per bundle, which counts as operations on your plan.
Modules

What can you do with Braintree in Make?

Braintree gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Braintree1

Create a Customer

Action

In Make“Creates a new customer.”

Create a Customer adds a new customer profile to Braintree from data that lives elsewhere, so the buyer already exists in Braintree before any payment happens.

When to use it
a lead signs up in a form or a CRM and should become a Braintree customer too.
Watch out
run Search Customers first when the same person might already exist, or you may end up with duplicates.
Braintree2

Delete a Customer

Action

In Make“Deletes a customer.”

Delete a Customer removes a customer profile from Braintree, which keeps your account tidy when someone leaves or asks to be erased from your records.

When to use it
closing an account after an explicit request, triggered from your support or CRM tool.
Watch out
treat every deletion as final and test on a dummy customer with Run once before you switch the scenario on.
Braintree3

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

Execute a GraphQL Query lets you send your own authorized GraphQL query to Braintree, which opens up anything the ready-made modules leave out.

When to use it
you need data or an operation that none of the other nine modules offers.
Watch out
you write the query yourself, so start with a small read-only query and check the result with Run once before relying on it.
Braintree4

Get a Customer

Action

In Make“Retrieves a customer.”

Get a Customer fetches one known customer from Braintree with their full details, so later modules can use the complete record instead of a partial one.

When to use it
you already hold the customer reference from a previous module and want the rest of the profile.
Watch out
it returns a single customer; when you only know part of the details, Search Customers is the better fit.
Braintree5

Get a Transaction

Action

In Make“Retrieves a transaction.”

Get a Transaction pulls the full record of one specific Braintree transaction, which helps when a summary is not enough to reconcile a payment or answer a customer.

When to use it
right after Watch New Transactions, or when a support ticket mentions a payment you need to inspect.
Watch out
it targets one transaction at a time; to scan several, pick Search Transactions instead.
Braintree6

Update a Customer

Action

In Make“Updates a customer.”

Update a Customer rewrites an existing Braintree customer with fresh information, so the profile stays aligned with what your CRM or billing tool knows.

When to use it
a buyer changes company or contact details in another system and Braintree should follow.
Watch out
it needs the right customer to change, so place Search Customers or Get a Customer before it to target the correct profile.
Braintree7

Search Customers

Search

In Make“Searches for customers.”

Search Customers looks through your Braintree customers and returns the ones that match, which is how you check whether someone already exists before acting.

When to use it
before creating or updating a profile, to avoid duplicates and to find the right record.
Watch out
a search can return zero, one or many bundles, and each following module runs once per bundle it receives.
Braintree8

Search Transactions

Search

In Make“Searches for transactions.”

Search Transactions finds the Braintree transactions that match what you look for, giving you a batch of payments to report on or reconcile in one pass.

When to use it
a finance review or a dispute where you need every payment linked to a situation, not just the newest one.
Watch out
a broad search can return many bundles, and each one costs operations in the modules that follow.
Need help

Need help automating Braintree with Make?

A person reads every message.

FAQ

Braintree and Make: frequently asked questions

01Is the Braintree Make integration free?
Yes, on the Make side. Braintree is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and allow unlimited active scenarios. Braintree itself needs an active merchant account, billed on Braintree's own terms, which this page does not cover.
02What do you need to connect Braintree to Make?
You need an active Braintree merchant account and three values from it: the Environment, the Public key and the Private key. All three sit in the API Keys section, reached through the gear icon and the API menu in Braintree. The Private key stays hidden until you click View. In Make, add a Braintree module, click Create a connection, give it a name if you like and paste those values. The connection is then shared by every Braintree module in your scenarios.
03Do the Braintree triggers in Make react in real time?
No. Both Braintree triggers, Watch New Customers and Watch New Transactions, are scheduled. Make checks Braintree on the schedule you set on the first module, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans go down to 1 minute. There is no instant trigger for Braintree in Make, so a new customer or payment appears in your scenario at the next scheduled check.
04What if a Braintree module you need is missing in Make?
Start with Execute a GraphQL Query. It sends an authorized GraphQL query of your own to Braintree and covers what the other nine modules do not. The Braintree app in Make has no generic Make an API Call module, so this GraphQL module is the only open door inside the app. If writing queries is not your thing, the Hack'celeration team can build that part of the scenario with you and check it before it goes live.
05Should you use Make or n8n for Braintree?
It depends on what you need. On Make, Braintree comes with 10 ready modules: 2 scheduled triggers, 6 actions and 2 searches, available from the Free plan and set up visually in the editor. The same app often has an n8n node too, so check what that node covers against your own flow before choosing. The deciding criteria are the modules your scenario really needs, the tool your team already knows and the way each platform counts usage.
Same platform

Other docs you might need on this stack.

Browse all integrations