Brex Claude Connector

A connector is a connection to data, not a magic button. It tells Claude where to read. Whether the output is useful still depends on what you ask and how you check the result.

Brex is the corporate card and spend management layer for venture-backed and growth-stage companies. The Claude connector exposes transaction, receipt, and policy data so the question “who is spending what on what, and where is the policy slipping” becomes a one-prompt answer instead of a finance-team triage cycle.

What is the Brex Claude connector?

The Brex Claude connector is a permission-controlled bridge to your Brex workspace. It uses OAuth and respects Brex’s role-based permissions. Read access covers card transactions, receipts, vendor data, expense categories, and spend policies. Write actions (initiate reimbursements, modify policies) require explicit admin scope.

What can Brex do once Claude is connected?

• Read card transactions. Pull all card activity by user, vendor, category, date.
• Read receipts and memos. Including images of receipts uploaded by employees.
• Read vendor data. Top vendors by spend, frequency, category.
• Read spend policies. Pull policy rules; surface violations.
• Initiate reimbursements with write scope. Restricted to admin roles.
• Cross-connector with QuickBooks or Mercury. Reconcile card spend against accounting categories or bank reality.

How do I add the Brex connector?

1. In Claude, open the toolbox in the bottom-left, click Customize, then Connectors.
2. Click the +, then Browse connectors.
3. Find Brex in the directory. Click + on the card.
4. The Brex OAuth flow opens. Sign in. Approve read scopes for transactions, receipts, and policies. Add write scopes only if you are an admin with reimbursement authority.
5. Test: “Show me the five largest card transactions from last week.” If they come back, Brex is live.

Brex’s permission model is role-based with strict separation between viewer, manager, and admin. The connector respects your assigned role. For finance teams, start with a manager-level seat for visibility; reserve admin scope for the one or two people who actually authorize spend changes.

Standout prompts for Brex

These are the prompts that exploit Brex’s specific capability rather than treating Claude like a generic chat tool. Copy, paste, modify the specifics.

• Policy Violation Audit. Reads transactions over the past month, surfaces every spend that violates a written policy (over per-meal limit, wrong category, missing receipt), drafts the per-employee outreach.
• Vendor Spend Rollup. Reads card spend by vendor over the past quarter, surfaces top 20 vendors, drafts the cost-control review for finance team.
• Missing Receipt Sweep. Reads transactions over $25 with no attached receipt, drafts the per-employee nudge with deadline.
• Monthly Close Prep. On the last business day of the month, drafts the close-ready report: all transactions categorized, missing receipts flagged, policy violations summarized.
• Subscription Sprawl Detection. Reads recurring vendor charges, clusters by tool type, surfaces overlapping SaaS subscriptions across teams.
• Travel Spend Brief. Reads travel category spend, surfaces top destinations and per-trip averages, drafts the travel-budget review.
• Team Spend Compare. Reads card activity by department, surfaces relative spend rates, drafts the budget-vs-actual narrative.
• Vendor Negotiation Prep. For a top vendor, reads payment history and category, drafts the renegotiation talking points.
• New-Card Onboarding Brief. For a recently hired employee with a new card, drafts the spend-policy explainer email referencing actual amounts.
• Reimbursement Backlog Drain. Reads pending reimbursement requests, surfaces the oldest, drafts the approval batch for admin review.

What are the limits?

• Write actions need admin scope. Reading is the default. Initiating reimbursements or modifying policies requires admin-level write scope.
• Brex API rate limits. Heavy use can hit Brex’s per-minute API ceiling. Pace longer audits across batches.
• Per-query transaction cap. A single query usually returns 100-500 transactions. For longer audits, batch by date range.
• Receipt image quality varies. Receipt image readability depends on the employee’s upload; some receipts may need manual review.

Is the Brex connector safe?

• For paid Claude plans, Brex data accessed via the connector is not used to train models and is not retained beyond the request.
• Card transaction data and employee spend behavior is sensitive HR-adjacent data. Treat connector access with care; restrict to finance and management roles.
• Policy and reimbursement write actions should always be reviewed before commit. Use draft-then-approve patterns.
• Revoke from Claude Settings → Connectors and from Brex’s Settings → Integrations.

When does a connector pay off vs. just chatting with Claude?

Connectors earn their setup time when the data updates faster than you can retype it, lives behind login, or runs into the thousands of items. For one-off questions about static information, plain Claude through the chat interface is faster than installing anything. The break-even is usually around the third time you would otherwise be copy-pasting context for the same kind of question. For the full list of connectors and which pillar each belongs to, see the Claude Connectors hub. If a term in this post is unfamiliar, the AI Glossary has plain-English definitions.

Frequently asked questions

Brex or Ramp or American Express?

Brex for tech-forward startups and growth companies (especially VC-backed). Ramp for spend management plus card across all stages. Amex for premium rewards but weaker software. The Claude connector currently covers Brex; Ramp has a connector on the roadmap.

Can Claude approve reimbursements automatically?

With write scope, yes, but most finance teams keep approval manual: Claude drafts the batch, an admin clicks approve in Brex. Stops auto-approving a wrong reimbursement.

Does the connector work with Brex Cash?

Yes. Brex Cash account balances and activity are exposed via the connector alongside card data.

Will Claude trigger Brex notifications?

Standard Brex notification behavior applies for any write action. Employees get the usual reimbursement notifications. Test in a sandbox if possible.

Can Claude read Brex Travel bookings?

Yes if you use Brex’s travel booking feature. Useful for surfacing travel patterns and cost-per-trip analysis.

How does this pair with QuickBooks?

Pair them. Brex is card-spend truth; QuickBooks is books truth. Claude reads both to surface unreconciled categorization gaps.

Can Claude help with corporate card policy redesign?

Yes. Reads spend patterns plus existing policy, drafts recommendations for tightening or loosening limits based on actual behavior data.

Sources

• Anthropic: Introducing Connectors · official launch and partner list
• Brex developer documentation · what the Brex connector exposes
• Brex API reference · API surface for the connector
• Anthropic Trust Center · privacy and compliance posture
• Anthropic privacy notice · connector data handling

You might also like

• Claude Connectors Guide (2026) · the master hub
• Claude Connectors for Finance + Accounting · the pillar this connector belongs to
• Mercury Claude Connector · the banking sibling
• Stripe Claude Connector · the payments-side sibling
• Claude for Finance Professionals · the broader finance playbook
• How to Use Claude AI · the beginner walkthrough
• Best Claude Prompts: 50 Examples · the broader collection
• Best AI Prompts by Job and Use Case · 60+ prompt packs organized by role and artifact