How often does Dropbox data sync to Freshbooks?

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 Freshbooks write happens at the end of the window, never mid-sync.

How does Well match Dropbox records to entries in Freshbooks?

Well parses each Dropbox attachment into a structured invoice, then probes your Freshbooks 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 Freshbooks entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.

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

Dropbox carries the original transaction currency on every record and Freshbooks natively ledgers in multiple currencies. Well preserves the original amount, applies your Freshbooks chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Freshbooks, so the Freshbooks entry you post keeps both sides of the trade.

Can I customise which Dropbox fields are sent to Freshbooks?

The default mapping turns every parsed Dropbox attachment into a Freshbooks-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 Freshbooks field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Freshbooks entries.

What happens if I disconnect Dropbox or Freshbooks?

Disconnecting Dropbox stops the flow at the source. Well calls the Dropbox OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything you already reviewed and posted in Freshbooks is Freshbooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Dropbox and Freshbooks?

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 Freshbooks email-in address once it clears the matching threshold; Freshbooks creates the draft record from it and you confirm and post it. Well holds no write credential to Freshbooks. Tokens are encrypted at rest and in transit under TLS 1.3. Dropbox and Freshbooks together cover multiple regions; Well's storage region is configured per workspace.

Dropbox to Freshbooks

AvailableNative · DropboxNative · Freshbooks

Connect Dropbox to Freshbooks with Well

Dropbox attachments are parsed inside Well for vendor, amount, VAT, and due date, then the documents arrive at Freshbooks as drafts with the original message ID attached.

Connect both toolsView all integrations

Dropbox

Source

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

Freshbooks

Target

The FreshBooks connection delivers extracted documents into FreshBooks through its email-in address.

Why this pair

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

What Well does between Dropbox and Freshbooks

One-way: Dropbox into Well into Freshbooks
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

Atlassian B.V.

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

VendorAtlassian B.V.
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 entityAtlassian B.V.
Tax idNL824921788B01
Domainatlassian.com
Ledger account6064 · SaaS

Confidence97%

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

Post

post as expenses and bills

Create a bill in FreshBooks (Select plan)

auto-posted

posted

TypeBill
VendorAtlassian B.V.
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Freshbooks

Action in Freshbooks

1 compatible with this trigger

Create a bill in FreshBooks (Select plan)

What Well does with Dropbox invoices on the way to Freshbooks.

01Featured

Capture supplier invoices from email

Well watches Dropbox for attachments matching invoice patterns, extracts amount, VAT, supplier, and due date in Well, then forwards the PDF to Freshbooks's email-in inbox. The original message ID stays on the document so the audit trail traces from Freshbooks back to the email that delivered the invoice.

Deduplicate forwarded receipts

Forwarded copies of the same receipt are caught by counterparty-plus-amount matching inside Well before delivery. If two team members forward the same supplier invoice from Dropbox on the same day, Well keeps the first copy as canonical and tags the second as a duplicate so Freshbooks only receives one document.

Route personal-card vs supplier receipts

Receipts arriving in Dropbox from employee personal cards are kept on the expense-reimbursement path inside Well, while supplier invoices route to the supplier-bill path. The category is decided from the sender domain plus the invoice format, so the right document type lands at Freshbooks rather than a mixed pile.

Resolve a new vendor from the invoice header

When an invoice arrives from a vendor Well does not recognise, the header (legal name, tax ID, bank IBAN) is parsed and a vendor record is proposed inside Well. The matched document is then forwarded to Freshbooks with the proposed match so Freshbooks's OCR can resolve it on arrival.

7 signals and actions across Dropbox and Freshbooks

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
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
Create a bill in FreshBooks (Select plan)
On the FreshBooks Select plan, the same email-in feature also creates a bill (with line items) instead of an expense.
Action·Invoice
Create an expense in FreshBooks
Well forwards the receipt PDF to your FreshBooks email-in address; FreshBooks creates an expense with merchant, total, and tax populated.
Action·Transaction
Resolve a FreshBooks merchant from the receipt
FreshBooks reads the merchant name off the forwarded receipt and matches it on the expense (or bill). You confirm or correct the merchant on first sight.
Action·Company
Attach the receipt to the FreshBooks record
The forwarded PDF is stored on the expense or bill as the source.
Action·Document

Reference

Field mapping for Dropbox → Freshbooks

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

Invoice fields

7 fields flow from Dropbox into Freshbooks.

Dropbox field	Label		Freshbooks field	Label
parsed.total_amount	Total amount	→	amount	Total
parsed.currency	Currency	→	currency_code	Currency
parsed.invoice_date.issue_date	Invoice date	→	create_date	Issue date
parsed.due_date	Due date	→	due_date	Due date
parsed.invoice_number	Invoice number	→	invoice_number	Invoice number
parsed.tax_total.tax	Tax total	→	vat_amount	Tax total
file.id	File id	→	external_id	External id

Connect Dropbox and Freshbooks 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 FreshBooks expense or bill queue. 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 Freshbooks
Click Connect with FreshBooks; FreshBooks asks for the account to authorise and returns a refresh token and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your FreshBooks.
- AuthConnect
- First syncup to an hour

How Dropbox and Freshbooks 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 Freshbooks 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 Freshbooks inbox
Well forwards the extracted document to your Freshbooks email-in address; Freshbooks reads expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated from it and you review and post. No write credential to Freshbooks 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 Freshbooks on Well

01How often does Dropbox data sync to Freshbooks?: 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 Freshbooks write happens at the end of the window, never mid-sync.
02How does Well match Dropbox records to entries in Freshbooks?: Well parses each Dropbox attachment into a structured invoice, then probes your Freshbooks 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 Freshbooks entry, otherwise the parsed invoice queues for sign-off with the candidates surfaced.
03Does Well handle multi-currency records between Dropbox and Freshbooks?: Dropbox carries the original transaction currency on every record and Freshbooks natively ledgers in multiple currencies. Well preserves the original amount, applies your Freshbooks chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Freshbooks, so the Freshbooks entry you post keeps both sides of the trade.
04Can I customise which Dropbox fields are sent to Freshbooks?: The default mapping turns every parsed Dropbox attachment into a Freshbooks-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 Freshbooks field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Freshbooks entries.
05What happens if I disconnect Dropbox or Freshbooks?: Disconnecting Dropbox stops the flow at the source. Well calls the Dropbox OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything you already reviewed and posted in Freshbooks is Freshbooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Dropbox and Freshbooks?: 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 Freshbooks email-in address once it clears the matching threshold; Freshbooks creates the draft record from it and you confirm and post it. Well holds no write credential to Freshbooks. Tokens are encrypted at rest and in transit under TLS 1.3. Dropbox and Freshbooks together cover multiple regions; Well's storage region is configured per workspace.