When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category.
Trigger·Transaction
Integrations · Spend managementConnect Ramp to Well
Connect Ramp so its card transaction, vendor, cardholder, and receipt become queryable in conversation and through your agents.
What flows between Well and Ramp
Well writes reconciled card transaction, vendor, cardholder back to Ramp after they clear your review queue, with the source-record link preserved. Use Ramp as the destination for entries enriched across your other connected tools.
| From Ramp | In Well | Relation | |
|---|---|---|---|
| Card transaction | Expense | Becomes | |
| Vendor | Supplier | Resolves to | |
| Cardholder | Team member | Links to | |
| Receipt | Audit attachment | Preserves as |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Ramp ⇄ Well
12 triggers and actions in Ramp.
When a Ramp bill is approved
Detects approved bills ready to push to your accounting system.
Trigger·InvoiceWhen a Ramp reimbursement is filed
Pulls employee reimbursement requests with receipt and category.
Trigger·TransactionWhen a Ramp transaction is still missing a receipt
Well flags Ramp transactions where no receipt has been uploaded so finance can chase them.
Trigger·DocumentWhen a Ramp vendor record appears in your account
Well discovers new Ramp vendors via the read-only ETL load and mirrors them as company records.
Trigger·CompanyWhen a Ramp transaction is coded by a Ramp rule
Picks up Ramp transactions that arrive with an automated coding rule already applied.
Trigger·TransactionWhen a Ramp transaction trips a spend policy
Pulls the policy_violations field on the transaction so non-compliant lines surface for review.
Trigger·TransactionWhen a Ramp card account is read
Pulls each Ramp card account the workspace holds with its limit and the cards bound to it.
Trigger·AccountCreate a draft bill in Ramp Bill Pay
Well forwards the PDF to your company's @ap.ramp.com address; Ramp OCR creates a draft bill with invoice number, vendor, payment details, and line items pre-filled.
Action·Invoice
What Well does with your Ramp connection
Connect
Connect Ramp over OAuth (MCP DCR): Well registers a client through Ramp's OAuth Dynamic Client Registration and you approve on Ramp's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings card transaction, vendor, and cardholder in from Ramp 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 Ramp entity into expense, supplier, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Ramp lands as expense, supplier, and team member you can search, chart, and automate, and approved records flow back to Ramp once they clear your review queue.
Questions Ramp unlocks
Ask in plain language. Well answers from your connected Ramp connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Ramp connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Ramp connection…
Connect Ramp in three steps
- 01
Authorise Ramp via MCP
From Well's Connections panel, search for Ramp and click Connect. Well discovers Ramp's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Ramp's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverramp-mcp-remote.ramp.com/mcp
- 02
Map your entities
Well's MCP client discovers card transaction, vendor, cardholder, and receipt from Ramp that Ramp's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Ramp records. Because Ramp ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Ramp records happens in the background.
How Ramp stays secure with Well
Well connects to Ramp's MCP server (ramp-mcp-remote.ramp.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Ramp secret. Tokens are scoped to the card transaction, vendor, cardholder, and receipt Ramp exposes and refreshed server-side. Reads only, Well cannot modify or delete Ramp records.
OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requestsramp-mcp-remote.ramp.com/mcp
- granted
Read Ramp records
Resources the Ramp MCP server exposes, scoped by your OAuth approval.
- granted
Resolve card transaction, vendor, cardholder, and receipt across your stack
Match identifiers in Ramp against the same entities your other connected tools expose, so each record carries cross-tool context.
- granted
Deliver documents to your Ramp inbox
Well forwards approved documents to your Ramp email-in address; Ramp drafts the record and you post it. No write credential to Ramp is requested.
- refused
Store Ramp passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Disconnect any time from Well settings or Ramp’s admin panel.
Frequently asked questions about Ramp and Well
From Well, open Connections, find Ramp, and click Connect. Well discovers the OAuth metadata at ramp-mcp-remote.ramp.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Ramp's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in card transaction, vendor, cardholder, and receipt from Ramp and reshapes each entity into your workspace: card transaction becomes expense; vendor becomes supplier. Every record arrives with the source identifier preserved, so Ramp stays the source of truth while Well lets you query the data alongside the rest of your stack.
Once Ramp is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Ramp source, so you can always trace a workspace record back to the original.
Yes. Ramp receipts are indexed in your workspace as audit attachment, so questions like "show me last week's receipts from Ramp" return them with the original Ramp link, the workspace context, and any related records (counterparty, period, attached document) joined inline.
Well combines live Ramp events with periodic reconciliation reads of card transaction, vendor, cardholder, and receipt. New rows appear within seconds when Ramp pushes them; periodic reads catch anything a push missed. The first connect backfills history from Ramp in the background.
Open Connections > Ramp in Well and click Disconnect. Well calls Ramp's token revocation endpoint and stops calling Ramp immediately on its side; provider-side propagation to Ramp's admin panel varies by provider. The card transaction, vendor, cardholder, and receipt Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Once a reconciled record clears your review queue, Well forwards the extracted document to your Ramp email-in address with the matched context attached: line items, ledger codes, vendor or customer references, and the source PDF. Ramp's own capture reads it and drafts the entry; you review and post it, so Ramp stays the system of record. Well holds no write credential to Ramp and delivers only what you have approved (case-by-case or under a per-rule auto-forward threshold you set).
Connect Ramp with
Ready-to-ship workflows that pair Ramp with another tool through Well.
Freshbooks
Reconcile Ramp card transactions, bills, and reimbursements…
Bill.com
Reconcile approved Ramp bills inside Well, forward each docu…
Melio
Route approved Ramp bills into Melio for ACH or check disbur…
Pennylane
Reconcile Ramp card transactions and bills inside Well with…
Xero
Reconcile Ramp card transactions, bills, and reimbursements…
Xero
Pull Xero bills and contacts into Well, match them to Ramp c…
QuickBooks
Reconcile Ramp card transactions and reimbursements inside W…
Gmail
Parse supplier invoices and receipts from Gmail inside Well,…
Pairs well with Ramp
More in Spend management
Popular cross-category
Ready to connect Ramp?
Connect once. Every card transaction, vendor, cardholder from Ramp becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.