Integrations · Payments and banking

Connect Brex to Well

Import Brex transaction and company record into Well. Match each one to the ledger line and customer it settles against in your workspace.

Connect BrexSee what Well does

What Well pulls from Brex

Brex feeds transaction, company record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Brex’s access.

From Brex		In Well	Relation
Transaction		Ledger line	Becomes
Company record		Customer	Enriches

Sync mode: incremental polling
Refresh: scheduled
Direction: Brex → Well

What Well does with your Brex connection

Connect

Connect Brex over OAuth 2.0: you approve on Brex's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings transaction and company record in from Brex on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Brex entity into ledger line and customer, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Brex lands in the workspace as ledger line and customer you can search, chart, and automate.

Questions Brex unlocks

Ask in plain language. Well answers from your connected Brex connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Brex connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Brex connection…

1 agent skill runs on Brex.

Well lists Brex in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Brex

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Brex in three steps

01
Authorise Brex via OAuth 2.0
Open Well's Connections panel, find Brex, and click Connect. You're redirected to Brex's authorize screen, where you'll see the exact scopes Well requests. Approve, and you land back in Well with the connection live.
- AuthOAuth 2.0
- Accessread-only
02
Map your entities
Well reads transaction and company record from Brex on first connect and brings each record into your workspace using the canonical mappings defined in Well's data-views layer.
- Mappingpreconfigured by Well
03
Use the data
Use the data: ask questions in conversation, build records tables, or let agents act on Brex records. Brex is read-only in Well; the records stay in your workspace with the original source identifier preserved.
- First syncstarts as soon as connect completes

OAuth handshake typically under a minute. Backfill of historical records runs in the background; you can use Well in conversation against incoming records while the backfill completes.

How Brex stays secure with Well

Well calls Brex's API with an OAuth 2.0 token scoped to transaction and company record. Brex's consent screen shows you the same list before you approve. Brex enforces scope server-side; authentication runs entirely through Brex's authorize screen so Well never sees your credentials. Tokens refresh automatically; rotation is one click away.

OAuth 2.0Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Brex records
Endpoints the Brex API token grants, scoped by your consent.
granted
Resolve transaction and company record across your stack
Match identifiers in Brex against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Brex records
Not granted; Brex is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Brex passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
refused

Disconnect any time from Well settings or Brex’s admin panel.

Frequently asked questions about Brex and Well

How do I connect Brex to Well, and how long does it take?

Open Connections in Well, pick Brex, and click Connect. You're redirected to Brex's OAuth screen, you approve the scopes Well requests, and you land back in Well with the connection live. The whole flow runs under a minute and never requires you to handle client credentials.

What does Well pull into the workspace from Brex?

Well brings in transaction, and company record from Brex and reshapes each entity into your workspace: transaction becomes ledger line; company record becomes customer. Every record arrives with the source identifier preserved, so Brex stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well surface Brex customer balances and historical activity?

Each Brex customer carries their full payment history, outstanding balance, and dispute record in Well. Ask "what's our lifetime revenue from Globex through Brex" and the answer joins every payment, refund, and dispute to a single customer view, with the source Brex identifiers preserved.

How does Well preserve the link from a workspace ledger line back to the original transaction in Brex?

Every workspace ledger line built from Brex carries the source transaction identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Brex record; from Brex, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

How often does Brex sync with Well, and what triggers a refresh?

Well polls Brex regularly for transaction and company record. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on Brex's side stays modest.

Can I disconnect Brex and what happens to the data Well already pulled?

Open Connections > Brex in Well and click Disconnect. Well calls Brex's token revocation endpoint and stops calling Brex immediately on its side; provider-side propagation to Brex's admin panel varies by provider. The transaction and company record Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Brex?

The Brex records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.