How often does Dropbox data sync to Ramp?

Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Ramp write happens at the end of the window, never mid-sync.

How does Well match Dropbox records to entries in Ramp?

Well parses each Dropbox 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.

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

Dropbox 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.

Can I customise which Dropbox fields are sent to Ramp?

The default mapping turns every parsed Dropbox attachment into a Ramp-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Ramp field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Ramp entries.

What happens if a Dropbox record fails to post to Ramp?

When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Dropbox record. Nothing silently drops.

How does Well authenticate with Dropbox and Ramp?

Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; 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. Dropbox and Ramp together cover multiple regions; Well's storage region is configured per workspace.

Dropbox to Ramp

AvailableNative · DropboxNative · Ramp

Connect Dropbox to Ramp with Well

Anchor Dropbox payment notifications against the next Ramp debit, so the bank line carries the original supplier reference.

Connect both toolsView all integrations

Dropbox

Source

The Dropbox connection lets Well write processed documents into your Dropbox folder.

Ramp

Target

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

Why this pair

Connect Dropbox to Ramp through Well so records flow without manual rework.

What Well does between Dropbox and Ramp

One-way: Dropbox into Well into Ramp
Sync mode: Polling every 15 minutes
Up to 4 syncs/hour

Trigger from Dropbox

1 events · pick one

Well engine·recipe·When an invoice file lands in the watched Dropbox folder

Source

from upload · 15-min poll

Orange Business

via Dropbox

Invoice

When an invoice file lands in the watched Dropbox folder

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

Extract

6 fields read from Dropbox

6 fields read

VendorOrange Business
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 entityOrange Business
Tax idFR47380129866
Domainorange.com
Ledger account6262 · Telecom

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
VendorOrange Business
Amount€1,284.00
Ledger6262 · Telecom
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 Dropbox invoices on the way to Ramp.

01Featured

Match supplier confirmations to outbound transfers

Payment confirmations arriving in Dropbox 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 Dropbox 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 Dropbox 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.

7 signals and actions across Dropbox and Ramp

When a supplier is detected on a parsed Dropbox file
Extracts the supplier named on a parsed file and matches it against your existing companies.
Trigger·Company
When an invoice file lands in the watched Dropbox folder
Reads the new PDF from the watched Dropbox folder and parses it into a structured invoice with supplier, amount, date, and tax.
Trigger·Invoice
When a document file lands in the watched Dropbox folder
Picks up a new receipt or supporting document from the watched folder and stores it as a Well document for matching.
Trigger·Document
Attach the source document to the Ramp bill
The forwarded PDF is stored on the Ramp draft bill as the source document.
Action·Document
Create a draft vendor credit in Ramp Bill Pay
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
Create 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
Resolve 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

Reference

Field mapping for Dropbox → Ramp

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

Invoice fields

4 fields flow from Dropbox into Ramp.

Dropbox field	Label		Ramp field	Label
parsed.total_amount	Total amount	→	matched_record.amount	Matched amount
parsed.currency	Currency	→	matched_record.currency	Currency
parsed.invoice_number	Invoice number	→	matched_record.reference	Reference
file.id	File id	→	matched_record.id	Source id

Connect Dropbox and Ramp in three steps.

1
Connect Dropbox
Click Connect with Dropbox; you authorise the folder Well watches through Apideck's file-storage connection and authorise read access to supplier-invoice and document files read from a watched folder via Apideck file-storage. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Dropbox.
- AuthConnect
2
Map your accounts
Well discovers the Dropbox attachments matching your invoice pattern (supplier-invoice and document files read from a watched folder via Apideck file-storage) 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 Dropbox and Ramp stay secure with Well

Well calls Dropbox with an OAuth 2.0 token scoped to read-only access. Dropbox'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 Dropbox and Ramp host theirs.

OAuth 2.0Storage region per workspaceGDPR-aligned

Scopes Well requests

Read Dropbox records
Scoped to supplier-invoice and document files read from a watched folder via Apideck file-storage. No access to anything else in your Dropbox 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 Dropbox records
Not granted. Dropbox 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 Dropbox’s admin panel.

Frequently asked questions about Dropbox and Ramp on Well

01How often does Dropbox data sync to Ramp?: Well polls the Dropbox API every fifteen minutes for new records; new activity reaches the downstream target on the next polling cycle. Records collected during a polling window are matched in a batch, then ranked by confidence; the Ramp write happens at the end of the window, never mid-sync.
02How does Well match Dropbox records to entries in Ramp?: Well parses each Dropbox 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.
03Does Well handle multi-currency records between Dropbox and Ramp?: Dropbox 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.
04Can I customise which Dropbox fields are sent to Ramp?: The default mapping turns every parsed Dropbox attachment into a Ramp-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Ramp field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Ramp entries.
05What happens if a Dropbox record fails to post to Ramp?: When a record fails to post to Ramp (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Dropbox record. Nothing silently drops.
06How does Well authenticate with Dropbox and Ramp?: Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; 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. Dropbox and Ramp together cover multiple regions; Well's storage region is configured per workspace.