Integrations · Business banking

Connect Plaid to Well

Read account balances and posted transactions from your linked bank and card accounts via the Plaid MCP server. Well syncs accounts, transactions, and the merchants behind them.

What Well pulls from Plaid

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

From PlaidIn Well
Transaction
Ledger line
Merchant
Vendor
Account balance
Cash position
Plaid logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Plaid → Well

6 triggers from Plaid.

  • When a transaction posts in a Plaid-linked account

    Captures each posted bank or card transaction with amount, currency, merchant, and the account it cleared in.

    Trigger·Transaction
  • When a pending transaction appears in Plaid

    Surfaces authorisations before they settle so the record is visible while it is still pending.

    Trigger·Transaction
  • When a Plaid account balance updates

    Reads the refreshed available and current balance on a linked account to feed your cash position.

    Trigger·Account
  • When a new account is linked through Plaid

    Registers a newly connected checking, savings, or credit account with its institution and mask.

    Trigger·Account
  • When Plaid resolves a merchant on a transaction

    Pulls Plaid's normalised merchant name so the counterparty resolves to a company in your graph.

    Trigger·Company
  • When Plaid removes a transaction

    Picks up reversals and deletions the institution issues so your ledger stays consistent with the bank.

    Trigger·Transaction

What Well does with your Plaid connection

Connect

Connect Plaid over OAuth (MCP DCR): Well registers a client through Plaid's OAuth Dynamic Client Registration and you approve on Plaid's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings transaction, merchant, and account balance in from Plaid on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

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

Available

Your data from Plaid lands in the workspace as ledger line, vendor, and cash position you can search, chart, and automate.

Questions Plaid unlocks

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

Ask Well

Ask anything about your Plaid connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Plaid connection…

Connect Plaid in three steps

  1. 01

    Link your bank and card accounts through Plaid

    Open Plaid in Well's Connections panel and begin. Well discovers the OAuth metadata at the Plaid MCP endpoint, registers itself through Dynamic Client Registration, and hands you to Plaid to choose which linked accounts are in scope. The selection of accounts stays yours; Well reads only what you authorise.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP serverapi.dashboard.plaid.com/mcp/sse
  2. 02

    Map your entities

    Well reads the accounts, their posted transactions, and the merchants behind them, capturing each transaction as a workspace transaction and each balance to your cash position through Well's data-views layer; the matched ledger entry is built internally from there.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Ask about balances across every linked account at once, table the recent transactions, or let an agent resolve merchants to vendors. There are no invoices in Plaid, so the workspace view is about money movement and balances rather than billing documents.

    • First syncstarts as soon as connect completes

Connecting completes in about a minute. Current balances are read straight away; the transaction history backfills in the background so questions answer while it fills in. Plaid developer docs.

How Plaid stays secure with Well

Plaid connects through its MCP endpoint over the Model Context Protocol, and the OAuth Dynamic Client Registration handshake keeps the bank credentials with Plaid rather than with Well. The token covers only the linked accounts you put in scope and their transactions, and it refreshes server-side. Well reads balances and movements; it has no ability to initiate a payment or alter anything at your institutions.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsapi.dashboard.plaid.com/mcp/sse
  • Read Plaid records

    Resources the Plaid MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve transaction, merchant, and account balance across your stack

    Match identifiers in Plaid against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Plaid records

    Not granted; Plaid is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Plaid passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

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

Frequently asked questions about Plaid and Well

Choose Plaid in Well's Connections panel and begin the handshake. Well discovers the OAuth metadata at the Plaid MCP endpoint, registers a client through Dynamic Client Registration, and routes you to authorise the bank and card accounts you want Well to read. Nothing to paste, and the consent step keeps the choice of which linked accounts are in scope entirely with you.

Plaid is a bank-and-card aggregator, so Well reads accounts, their posted transactions, and the merchants those transactions name. Each posted transaction is captured as a workspace transaction, every merchant resolves to the vendor it represents, and account balances feed your cash position. Well builds the matched ledger entry internally from there; Plaid itself carries no invoices, so Well never invents one. The connection is about money movement and balances, not billing documents.

A transaction Plaid reports is captured as a workspace transaction carrying its amount, currency, merchant string, and the account it cleared in; Well then builds the matched ledger entry internally. Well resolves the merchant to a known vendor where it can and leaves the source descriptor attached either way, so a cryptic bank memo still traces back to the institution it came from. Multi-currency activity keeps its original amount so cross-border accounts reconcile honestly.

Yes. Because every linked account's balance feeds a single cash-position view, a question like "what is across all our accounts right now" answers from the workspace rather than five banking tabs. Each balance keeps its account and institution, so the same view drills down to a single account when you need the detail behind the total.

Well reads account state and new transactions through the Plaid connection and folds them into the workspace as they are read through the connection, with the initial connect pulling the available history in the background. Plaid remains the live link to each institution; Well keeps a queryable copy so balances and movements sit next to the records from your other tools.

Disconnecting Plaid in Well revokes the token and ends Well's reads against your linked accounts at once; the connection only ever read, so there is nothing posted back to unwind. The transactions and balances already mirrored remain in your workspace for historical questions. To stop Plaid sharing the underlying accounts entirely, remove Well's access from Plaid's own dashboard as well.

Plaid logo

Ready to connect Plaid?

Connect once. Every transaction, merchant, account balance from Plaid becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.