Skip to content
ClickRuntime

Automate Brex

Stay on top of money leaving and arriving through Brex: transfers that fail, yesterday's card purchases and a record of settled payments. Brex reports transfer outcomes as events, so a failed payment to a vendor doesn't sit unnoticed. Describe what you want to your AI assistant, check what it will do, and it keeps running.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: when a Brex transfer fails, email me the amount, the counterparty and the failure reason if Brex gives one.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Brex

An immediate email when a transfer fails, a morning post of card spend with large charges called out, and a Monday log of completed transfers. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get an email the moment a transfer fails

You learn about a failed Brex payment straight away, with the amount and who it was going to.

See how it works
Daily

Get yesterday's card spend in Slack each morning

Your finance channel starts the day with every Brex card charge from yesterday and a total, with anything over $500 marked.

See how it works
Collects as they arrive, acts daily

Get a weekly log of completed transfers

Every Monday you get last week's settled Brex transfers in one list, money in and money out.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Brex, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Brex automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Brex should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every morning, check Brex and tell me about any outgoing transfer over $5,000 or any card spend at a merchant we have not used before.

Every Monday, post last week's Brex spend by category to our #finance Slack channel.

Every day, add Brex transactions to Google Sheets, have AI categorize the ones without a memo, and email me the ones it could not classify through Gmail.

Beyond chat

Have Brex work when you're not in the chat

Connecting Brex to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Brex

Brex connects with a user token that a Brex account or card admin creates in the dashboard, limited to the scopes you choose.

Brex

Fintech / Spend management

  1. Sign in to dashboard.brex.com as an account or card admin and go to Developer, then Settings.
  2. Choose Create Token, give it a name and select read scopes for the data your automations use, such as transfers and transactions.
  3. Copy the token now, because Brex shows it only once.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for Brex.

Good to know

Brex limits that affect automations

  • A Brex token expires after 90 days without use. An automation that runs at least weekly keeps it active; a paused one may need a new token.
  • The token is shown once when you create it. If you lose it, create a new one.
  • The Brex API works against your live account only, with no separate sandbox for testing.

FAQ

Questions about automating Brex

What can ClickRuntime see in Brex?
Only what the token's scopes allow. The automations here use read access to transfers and card transactions.
Can it send money from Brex?
None of the automations listed here move money, and a read-only token can't. Brex also requires a unique key on money-movement requests so a retry can't pay twice.
How quickly do I hear about a failed transfer?
Right away. Brex sends an event when a transfer fails, and ClickRuntime fetches the amount and counterparty and emails you then.
Why did my Brex connection stop working?
Most likely the token went 90 days without use and expired. Create a new one and replace the secret in the ClickRuntime dashboard.
Do I need AI for Brex automations?
No. These alerts and digests are straightforward. No AI key is needed: AI comes with every ClickRuntime plan.
Is this a Brex connector for ChatGPT or Claude?
Not for chatting with Brex data. A chat connector lets your assistant read and change Brex while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Brex event.

Related pages

Keep exploring

Tell your assistant what Brex should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude