- 01What Dropbox data does Well pull into Melio?
- Well watches Dropbox for attachments matching the configured invoice and receipt filters, extracts supplier-invoice and document files read from a watched folder via Apideck file-storage, and forwards the structured output to Melio as bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture, with the original email message ID stored on every record for audit.
- 02How often does Dropbox data sync to Melio?
- 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 Melio write happens at the end of the window, never mid-sync.
- 03What happens to historical Dropbox data when I first connect to Melio?
- Dropbox 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 Melio ledger, and re-running the backfill is safe because Well tracks the Dropbox record IDs and updates existing Melio entries instead of duplicating them.
- 04How does Well prevent duplicates when posting Dropbox records to Melio?
- Every Dropbox message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Melio entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Melio.
- 05What happens if a Dropbox record fails to post to Melio?
- When a record fails to post to Melio (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 Melio?
- 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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted at rest and in transit under TLS 1.3. Dropbox and Melio together cover multiple regions; Well's storage region is configured per workspace.