When a Braintree event fires, find the customer row in Google Sheets and update its payment status

When a Braintree event you choose fires, this workflow looks up the customer’s row in your Google Sheets tracker and updates that row with the payment status from the event.

Braintree

Google Sheets

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 2.4k sites Free to import

The When a Braintree event fires, find the customer row in Google Sheets and update its payment status workflow on the FlowMattic canvas, with 3 steps across Braintree, Google Sheets — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A billing tracker in Google Sheets is only useful while it is current. If you update each customer's payment status by hand after checking Braintree, the sheet falls behind on busy days. This workflow finds the right row and updates it when Braintree reports an event.

The Braintree trigger fires for the events you choose in its setup. FlowMattic then runs Lookup Row Data in Google Sheets, searching your tracker for a value from the event, such as a customer ID or email. The row it finds is passed to the Update Row step, which writes the mapped values into that same row.

Which identifier you can search on depends on what the Braintree event carries, so look at a test run before you set the lookup. If no row matches, the update has no row to change, and Task History shows what happened on each step.

Subscription tracker for a membership site

Each member has a row with their Braintree customer ID. When a subscription event arrives, the status column on that member's row is changed to match.

Invoice log for a small agency

Your clients pay through Braintree and your team checks a shared sheet. The payment column fills in on its own, so nobody asks the accountant whether a client has paid.

A collections sheet for your finance lead

Your finance lead works from one spreadsheet of customers. Picking only the Braintree events that matter to collections keeps the status column on each row up to date for that review.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Braintree Custom Events
Fires for the Braintree events you select in the trigger's setup. The event data is passed on, so you can use it to search the sheet and to fill in the status.
Step 2Action
Google Sheets Lookup Row Data
Searches your chosen spreadsheet for a value from the Braintree event, such as a customer ID. The matching row's data and position are passed to the next step.
Step 3Action
Google Sheets Update Row
Updates the row the lookup found in your Google Sheets spreadsheet with the values you map from the Braintree event, such as the event type or payment status. Other columns stay as they were.

What you need

FlowMatticCore
Braintree AccountAccount
Google Sheets AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Store a Braintree customer ID in your sheet if the events you pick carry one. An ID matches more reliably than a name, and a test run shows whether an email is included at all.
Add a Filter between the two Google Sheets steps that continues only when the lookup returned a row. Runs for customers missing from the sheet then stop before the update.
Map only the columns you want changed in Update Row, such as status and date, so the customer's other details in that row are left alone.

Questions about this workflow

Which Braintree events can start this workflow?

The trigger fires for the events you choose when you set it up in FlowMattic. Pick only the events that should change a customer's payment status in your sheet.

What if the customer has no row in my Google Sheet?

The lookup finds nothing, so the Update Row step has no row to update. Task History shows that run. The workflow doesn't add new rows as imported.

Does my sheet need a particular layout?

It needs one column holding a value the Braintree event also carries, such as a customer ID, for the lookup to search. The other columns are whatever you map in Update Row.

Do I need a Braintree account to use this workflow?

Yes. You connect your Braintree account to the trigger, and a Google account with edit access to the tracker spreadsheet.