How often does Gmail data sync to Ramp?

Gmail pushes events to Well in real time via webhooks, so most records land within a minute of the underlying action. Each event is matched immediately and reaches Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Gmail record post to Ramp automatically?

Not always. Within seconds of Gmail firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Ramp email-in address and Ramp drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

How does Well match Gmail records to entries in Ramp?

Well parses each Gmail attachment into a structured invoice, then probes your Ramp ledger for an open bill or vendor with the same amount, due date, and supplier name. The probe ranks candidates by counterparty proximity, date window, and total match; above 85% it links the parsed PDF to the existing Ramp entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.

What happens to historical Gmail data when I first connect to Ramp?

Gmail exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Gmail record IDs and updates existing Ramp entries instead of duplicating them.

Does Well handle multi-currency records between Gmail and Ramp?

Gmail carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.

How does Well authenticate with Gmail and Ramp?

Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Gmail and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Gmail to Ramp

AvailableNative · GmailNative · Ramp

Connect Gmail to Ramp with Well

Stop chasing wire references: Gmail payment-instruction messages collapse onto the matching Ramp transfer with the original supplier reference preserved.

Connect both toolsView all integrations

Gmail

Source

The Gmail integration turns your inbox into an automated invoice capture flow.

Ramp

Target

The Ramp integration connects your corporate card and expense management platform to Well.

Why this pair

Most receipts that back a Ramp charge arrive by email before they ever reach the books.

Connecting Gmail to Ramp through Well closes that gap. Well reads invoice and receipt attachments from Gmail with read-only scope, parses each into a structured document, and matches it against Ramp card transactions on supplier, amount, and date over Ramp's MCP server. The matched receipt is surfaced against the Ramp transaction so the spend record carries its proof, and the Ramp policy classification stays intact. Reviewers approve a charge that already has its receipt attached, rather than chasing a forwarded email thread at month-end.

What Well does between Gmail and Ramp

One-way: Gmail into Well into Ramp
Sync mode: Real-time webhooks
Events arrive within a minute

Trigger from Gmail

5 events · pick one

Well engine·recipe·When an invoice PDF arrives as an attachment

Source

from email · live webhook

Uber BV

via Gmail

Invoice

When an invoice PDF arrives as an attachment

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from Gmail

6 fields read

VendorUber BV
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entityUber BV
Tax idNL852071589B01
Domainuber.com
Ledger account6251 · Travel

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

reconcile as draft bills

Create a draft bill in Ramp Bill Pay

auto-posted

posted

TypeBill
VendorUber BV
Amount€1,284.00
Ledger6251 · Travel
Source docattached
Confidence97%

audit linkto Ramp

Action in Ramp

1 compatible with this trigger

Create a draft bill in Ramp Bill Pay

What Well does with Gmail invoices on the way to Ramp.

01Featured

Match supplier confirmations to outbound transfers

Payment confirmations arriving in Gmail from a supplier are parsed for amount, reference, and date, then matched against the next Ramp debit window. Above the auto-link threshold the bank line carries the confirmation PDF; below it the queue surfaces the candidate transfer alongside.

Catch double-charge attempts from email

If a Gmail message asks for a second payment that you have already settled out of Ramp, Well flags it before any action. The original Ramp debit is shown alongside the parsed amount and counterparty so finance can refuse the second request with one click.

Anchor inbound wire references

Inbound wire notifications in Gmail carry a free-text reference that Ramp statements often abbreviate. Well harmonises the references so the next Ramp credit collapses onto the right invoice or receivable in the downstream ledger without manual lookup.

10 signals and actions across Gmail and Ramp

When an invoice PDF arrives as an attachment
Pulls from your Gmail inbox. Picks up emails matching has:attachment filename:pdf and runs the document through extraction.
Trigger·Invoice
When an email attachment is processed by Well
Pulls from your Gmail inbox. Receipts, invoices, statements: any PDF attachment is read and captured into your records.
Trigger·Document
When an email with a bill attachment is processed by Well
Pulls from your Gmail inbox. Well's AI extracts the bill from the attached PDF and matches the vendor against your existing records.
Trigger·Invoice
When an email with an invoice attachment is received
Pulls from your Gmail inbox. Well picks up any received email with a PDF attachment; forwarded headers are recovered automatically.
Trigger·Invoice
When an email arrives from a sender domain already in your vendor list
Pulls from your Gmail inbox. The vendor is matched against your existing company records.
Trigger·Invoice
When an email arrives from a sender domain not yet in your vendor list
Pulls from your Gmail inbox. Well prepares a new vendor record from the email and document headers for your confirmation.
Trigger·Invoice
Attach the source document to the Ramp bill
Driven by emailed invoices, receipts, and notifications. The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document
Create a draft bill in Ramp Bill Pay
Driven by emailed invoices, receipts, and notifications. 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
Create a draft vendor credit in Ramp Bill Pay
Driven by emailed invoices, receipts, and notifications. When the forwarded PDF is a vendor credit memo rather than an invoice, Ramp OCR creates a draft vendor credit (a separate record from the bill) with the vendor and credit amount pre-filled for your review.
Action·Invoice

Reference

Field mapping for Gmail → Ramp

3 fields across 1 record type, open to see the full table.

Invoice fields

3 fields flow from Gmail into Ramp.

Gmail field	Label		Ramp field	Label
extracted.invoice_number	Invoice number	→	matched_record.reference	Reference
extracted.total	Total	→	matched_record.amount	Matched amount
extracted.currency	Currency	→	matched_record.currency	Currency

Connect Gmail and Ramp in three steps.

1
Connect Gmail
Click Connect with Google; Google asks which mailbox to scope and returns a refresh token and authorise read access to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Google Workspace.
- AuthConnect
2
Map your accounts
Well discovers the Gmail attachments matching your invoice pattern (invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers) and the the Ramp Bill Pay drafts queue awaiting approval. Tune the parsing prompt once on the first ten records; Well saves the mapping and applies it to every subsequent attachment above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Ramp
Click Connect with Ramp; the Ramp MCP server registers a Well client automatically. Ramp's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First sync~30 min

How Gmail and Ramp stay secure with Well

Well calls Gmail with an OAuth 2.0 token scoped to read-only access. Gmail's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Well's storage region is configured per workspace regardless of where Gmail and Ramp host theirs.

OAuth 2.0Storage region per workspaceGDPR-aligned

Scopes Well requests

Read Gmail records
Scoped to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. No access to anything else in your Gmail account.
granted
Deliver documents to your Ramp inbox
Well forwards the extracted document to your Ramp email-in address; Ramp reads draft bills via email-in at the @ap.ramp.com address, with invoice number, vendor, payment details, and related records from it and you review and post. No write credential to Ramp is requested.
granted
Modify or delete Gmail records
Not granted. Gmail is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

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

Frequently asked questions about Gmail and Ramp on Well

01How often does Gmail data sync to Ramp?: Gmail pushes events to Well in real time via webhooks, so most records land within a minute of the underlying action. Each event is matched immediately and reaches Ramp within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02Will every Gmail record post to Ramp automatically?: Not always. Within seconds of Gmail firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Ramp email-in address and Ramp drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03How does Well match Gmail records to entries in Ramp?: Well parses each Gmail attachment into a structured invoice, then probes your Ramp ledger for an open bill or vendor with the same amount, due date, and supplier name. The probe ranks candidates by counterparty proximity, date window, and total match; above 85% it links the parsed PDF to the existing Ramp entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.
04What happens to historical Gmail data when I first connect to Ramp?: Gmail exposes the last full year through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Ramp ledger, and re-running the backfill is safe because Well tracks the Gmail record IDs and updates existing Ramp entries instead of duplicating them.
05Does Well handle multi-currency records between Gmail and Ramp?: Gmail carries the original transaction currency on every record, but Ramp ledgers in a single base; Well preserves the source currency, attaches the FX rate at the timestamp of the event, and the converted figure and the source amount both travel on the document Well forwards to Ramp, so both sides of the trade are visible when you post.
06How does Well authenticate with Gmail and Ramp?: Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, Well forwards the reconciled document to your Ramp email-in address once it clears the matching threshold; Ramp creates the draft record from it and you confirm and post it. Well holds no write credential to Ramp. Tokens are encrypted at rest and in transit under TLS 1.3. Gmail and Ramp together cover multiple regions; Well's storage region is configured per workspace.