Braintree Zapier integrationAutomate Braintree with Zapier.
The Braintree Zapier integration gives you 4 triggers and 1 action, with 0 searches. New customers, disputes, subscriptions and transactions can start a workflow, and Zapier can create a customer for you. Here is what it does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Braintree Zapier integration actually does for you
The Braintree Zapier integration links your payment account to the other tools you run, with no code. Something happens in Braintree (a payment, a new customer, a dispute), and Zapier passes it on to a spreadsheet, a CRM or a chat channel. One action also works the other way round: creating a customer in Braintree from another app.
Three results people usually build first. A live payment log: every new transaction becomes a row in a sheet the finance person already reads, thanks to New Transaction. A dispute alert: New Dispute pings the person who handles chargebacks, so the alert does not sit unread in an inbox nobody opens. A customer record kept in step: a signup in your form or CRM runs Create Customer, so the buyer already exists in Braintree before the first charge.
Now the honest part. Zapier does not refund, void or capture a payment here, and it cannot update or delete anything in Braintree: the only thing it writes is a new customer. There is no search either, so a Zap cannot look up an existing customer before acting. And every trigger is checked on a timer, so nothing is truly instant (more on that below).
If Zapier is new to you, the Zapier review gives the wider picture. The same app also exists on another platform: the Braintree Make integration page covers what Make offers for it, and Make vs Zapier compares the two tools criterion by criterion.
The Zapier words you need, in one minute
Seven terms come back on every line of this page. Read them once and the rest follows.
- Zap
- The automation you set up in Zapier: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap, here something new in Braintree. Once the Zap is on, Zapier keeps watching for it.
- Action
- What the Zap does once it has started: the step that writes, sends or creates something in an app for you.
- Task
- The unit Zapier bills. One task is one action that went through; your plan gives you a number of them each month.
- Polling vs instant
- Polling: Zapier asks Braintree for new items on a timer. Instant: the app calls Zapier itself. All Braintree triggers are polling.
- Filter
- A step that lets the Zap carry on only when the incoming item meets your condition, and quietly stops it otherwise.
- Connection
- Your Braintree account linked to Zapier once, then reused by every step of every Zap that touches Braintree.
What a Braintree Zap really costs
Braintree is not a premium app, so it works on the free plan. The bill comes from actions, never from watching.
- Free plan100 tasks a month
- Free plan Zap size1 trigger + 1 action
- Premium appNo
- Trigger cost0 tasks
The trigger costs nothing, however often Zapier checks Braintree for new payments. Each action that succeeds counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a second action, and you have a multi-step Zap that needs a paid plan. Note too that a few apps and a few actions take more than one task when they complete.
Connect Braintree to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need an existing Braintree account first, and access to whatever you want the Zap to read or write if it is not yours.
- 02
Pick Braintree
Type Braintree in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Braintree side, where the sign-in happens.
- 03
Sign in and grant access
Log in to Braintree in that tab and allow Zapier to use the account. The connection then shows up in your list, ready for every Zap you build with Braintree from now on.
Your first Braintree Zap: log every new transaction
GoalEach new Braintree transaction adds a row to a finance sheet, so the team stops exporting payments by hand.
- 01
Create the Zap
Start a new Zap and choose Braintree as the app that kicks it off. This is the Build stage: starting app and event, then the next app and its action.
- 02
Pick the trigger
Select New Transaction as the event and choose your Braintree connection. If none exists yet, Zapier walks you through the three steps above.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent transactions of the account, so pick a real one to map from instead of guessing what the data looks like.
- 04
Add the action
Add the spreadsheet step and map the transaction fields the test brought back into the columns. Test this step too and check the row that appears.
- 05
Publish
Click to publish and the Zap is on. From that moment, each new transaction lands in the sheet at the next check of your plan.
Braintree triggers on Zapier
4 events start a Zap when something happens in Braintree. Zapier checks for them at the interval your plan allows.
New Customer
Polling triggerIn Zapier“Triggers when you add a new customer.”
Starts the Zap each time a customer record appears in your Braintree account. That new customer can then be passed on, for example to a CRM, an email tool or a welcome sequence.
New Dispute
Polling triggerIn Zapier“Triggers when a new dispute is added.”
Fires when a new dispute is added to your Braintree account, in other words when one of your charges is contested. It is the trigger that protects revenue rather than the one that records it.
New Subscription
Polling triggerIn Zapier“Triggers when you a new subscription is added.”
Reacts to a recurring billing plan being added for a customer in Braintree. Useful if you sell memberships, software seats or any offer that charges on a cycle rather than once.
New Transaction
Polling triggerIn Zapier“Triggers when you add a new transaction.”
The workhorse of the integration: every fresh transaction recorded in Braintree can start a Zap. It is the event to hook your books or dashboards to.
Braintree action on Zapier
Braintree gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Customer
ActionIn Zapier“Create a new customer.”
Adds a new customer to your Braintree account from data another app sends, such as a form entry or a CRM contact. The buyer exists before the first charge.
When a Braintree Zap breaks
Most Braintree Zaps fail in predictable ways. None of them is exotic, and each has a simple fix.
The cases below come from Zapier's general behaviour and from the help article it links to Braintree. When a Zap misbehaves, start with the Zapier troubleshooting guide, then check these.
Old payments never show up
A Zap only reacts to what happens after it is switched on. Transactions and customers already in Braintree are not picked up; moving that history is a separate job.Create Customer feeds New Customer
A Zap that creates customers while another watches for new customers sets itself off again and again, and the task count drains fast. Keep the two apart.A bulk import stalls the trigger
After a migration or a mass import, a trigger can suddenly return a huge batch. Zapier's flood protection may hold that batch back instead of running it all.The connector itself changed
Zapier publishes an "App update: Braintree" help article. If a Zap built long ago acts oddly, that article is the first thing to read before changing anything.
Need help automating Braintree with Zapier?
A person reads every message.
