When a Ramp card is swiped
Captures every card transaction with merchant, amount, currency, and category.
Trigger·Transaction
Integrations · Spend managementConnect Ramp to Well
Sync Ramp card transactions, bills, and reimbursements into Well via the Ramp MCP server and forward extracted bill PDFs to your Ramp Bill Pay inbox
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
10 triggers and actions in Ramp.
When a Ramp reimbursement is filed
Pulls employee reimbursement requests with their amount and category as a transaction.
Trigger·TransactionWhen 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·InvoiceAttach the source document to the Ramp bill
The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·DocumentResolve a Ramp vendor from the bill
Ramp's OCR resolves the vendor name from the document. You confirm or merge against an existing Ramp vendor.
Action·Company
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
Connect Ramp to Well
Authorize Well to access your Ramp account through the secure connection setup.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverramp-mcp-remote.ramp.com/mcp
- 02
Map your entities
Confirm the connection within your Well dashboard to begin pulling card transactions, accounts, and people.
- Mappingpreconfigured by Well
- 03
Use the data
Provide your Ramp Bill Pay email-in address if you want to forward extracted bill PDFs directly to your AP inbox.
- First syncstarts as soon as connect completes
Once connected, your Ramp transactions and company details sync automatically 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
How does Well retrieve data from Ramp?
Well uses the Ramp MCP server to pull information about your company, people, accounts, payment means, and transactions. This data syncs in the background to keep your records current.
Can Well directly create or edit transactions inside my Ramp account via an API?
No. Well has no API write channel to Ramp. To send bills to Ramp, Well forwards extracted bill PDFs to your unique Ramp Bill Pay email inbox.
What specific Ramp entities does Well access?
Well retrieves accounts, company details, payment means, people, and transaction records.
Connect Ramp with
Ready-to-ship workflows that pair Ramp with another tool through 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.