Brex

Connect AI agents to Brex corporate cards and spend management. Agents monitor card and cash transactions, issue virtual cards with spend limits, check account balances, and pull expenses into approval and reconciliation workflows.

10 actions API key available

Brex website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A vendor purchase request is approved in the procurement workflow

List Users resolves the requesting employee's Brex user ID

List Card Accounts confirms available credit comfortably covers the requested limit

The finance lead reviews the card request, vendor, owner, limit, and duration, and approves or adjusts the amount

Create Virtual Card issues the card to the requester with the approved spend limit and expiry

The card details and purpose log to the vendor record and the procurement ticket

The requester gets the card confirmation, and finance's channel gets the issuance record

What This Integration Enables

Corporate spend is a stream of small decisions that finance only sees in aggregate, weeks later. This connector moves FlowRunner agents into the stream: they read settled card and cash transactions as they post, watch balances and available credit across accounts, pull expenses into approval workflows, and, on the write side, issue virtual cards with spend limits under human control. The read operations run wide and continuous. The one operation that creates spending power is narrow and gated, which is exactly the shape a finance team should demand from automation. - Sync settled card and cash transactions into ledgers and reconciliation sheets on a schedule - Issue virtual cards per vendor or per purchase with limits and durations, after a person approves - Monitor cash balances and available credit and alert when thresholds are crossed - Pull card and reimbursement expenses into reporting and approval workflows - Resolve organization users and roles before assigning card ownership

Without FlowRunner

The shared card problem One corporate card number circulates for a dozen subscriptions, and no one can say which vendor leaked it when fraud hits

Reconciliation as archaeology Finance reconstructs the month from statement lines, receipts in inboxes, and memory

Balance surprises Available credit is whatever the dashboard says when someone thinks to look, which is usually after it mattered

With FlowRunner

One card per vendor, scoped and expiring Virtual cards are issued per purpose with limits and durations, so exposure is bounded by design

Transactions flow to the ledger daily Card and cash transactions sync to the reconciliation sheet on a schedule, cursor-paginated so nothing is missed or doubled

Thresholds watch themselves Agents check balances and available credit continuously and page finance when a line crosses the mark

Use Case Scenarios

Reconciliation that happens nightly instead of monthly

Each night, an agent pages through List Card Transactions and List Cash Transactions with the stored cursors, and appends new settled activity to the reconciliation sheet in [Google Sheets](/integrations/google-sheets): amount, merchant, posted date, card. Unmatched or uncategorized lines get flagged for the controller's morning review in [Slack](/integrations/slack). At close, the work is confirming a handful of exceptions, not rebuilding a month.

A card per vendor, issued through the approval it deserves

Marketing needs a new analytics subscription. The request carries the vendor, the monthly price, and the owner. The agent verifies the numbers against the vendor record in [QuickBooks Online](/integrations/quickbooks), confirms capacity with List Card Accounts, and puts the issuance in front of the finance lead: $150 monthly limit, twelve-month duration, owned by the requester. On approval, Create Virtual Card issues it. When the subscription is cancelled next year, that card dies with it, and no shared number needs rotating.

The credit line that never surprises anyone again

Every morning, an agent reads List Card Accounts and List Cash Accounts. Available credit and operating balances post to a finance dashboard row, and when available credit drops below the threshold finance set, the alert reaches the CFO's channel with the number, the trend, and the largest recent transactions from List Expenses attached. The conversation about capacity happens days before a declined payment would have forced it.

Human-in-Loop Highlight

Create Virtual Card mints spending power. The card it returns is live immediately, usable for online and recurring payments up to its limit, and a limit typed in cents makes the failure mode concrete: 100000 is $1,000, and an agent that confuses units or trusts a spoofed request has issued a working payment instrument to the wrong number or the wrong person. That is not a data error you correct later; whatever was spent before someone noticed is spent. So issuance never rides on agent judgment alone. The agent assembles the request, owner resolved via List Users, capacity confirmed via List Card Accounts, limit and duration stated in dollars, and a named finance approver confirms before the call runs. Every card the workflow creates traces back to a person who said yes to that amount, which is the audit trail your next financial review will ask for.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Transactions

List Card Transactions Lists settled transactions on the primary card account, most recent first, with amount, merchant, dates, type, and card metadata. Cursor-paginated with optional posted-date filtering: the backbone of scheduled reconciliation syncs.
List Cash Transactions Lists transactions for a specific cash account, most recent first, with amount, description, type, and posted date. Cursor-paginated; account IDs come from List Cash Accounts.

Cards

List Cards Lists all cards, virtual and physical, with ID, name, owner, status, last four digits, and spend controls. The inventory view for audits of what spending power exists.
Get Card Retrieves a single card's full details by ID, including configured spend controls. Used to verify a card's limits before and after changes.
Create Virtual Card Creates a virtual card owned by a specified user with an optional spend limit and duration, issued immediately. Amounts are in cents. The operation this page's approval gate exists for.

Accounts

List Cash Accounts Lists all cash accounts including the primary operating account, with status, current balance, and account and routing numbers where available.
List Card Accounts Lists card accounts with current available credit and outstanding balance. The capacity check that runs before issuance and behind every threshold alert.

Users

List Users Lists organization users with name, email, status, and role, cursor-paginated. The resolution step before assigning card ownership.
Get Current User Retrieves the profile behind the API token. Used to verify credentials and record the acting identity in audit logs.

Expenses

List Expenses Lists expenses across the account, most recent first, with amount, merchant, status, category, and associated user, filterable by card or reimbursement type. Feeds approval queues and spend reporting.

Frequently Asked Questions

What can FlowRunner do with Brex?

FlowRunner agents can run List Card Transactions, List Cash Transactions, and List Cards in Brex, plus 7 more actions.

Does connecting Brex to FlowRunner require OAuth?

No. Brex connects to FlowRunner with an API key, no OAuth flow required.

Can Brex trigger a FlowRunner workflow automatically?

Brex doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Brex

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us