Newly observed files
Record existing Dropbox file IDs without copying them; webhook-triggered processing then emits previously unseen identities.
Workflow template
Start with a silent Dropbox folder baseline, then copy newly observed file identities and subfolders to Google Drive. Ignore edits to known files.
How it works
Record existing Dropbox file IDs without copying them; webhook-triggered processing then emits previously unseen identities.
Read authenticated file bytes from Dropbox. A revision-qualified path pins the version being processed.
Reuse or create the matching folder hierarchy beneath your chosen Drive destination.
Use a business identity to reuse the Drive file across repeated deliveries.
Upload the downloaded bytes to that Drive file ID without converting them to a native Google document.
The result
Existing files and later edits to known IDs do not generate automatic copies. A file moved into the watched tree from elsewhere counts as newly observed.
Dropbox new files/ Example.txt Projects/ Report.pdf
Fictional filenames. Empty folders are not created unless a copied file needs them.
Before activation
Grant file metadata and content read access. Enter an absolute Dropbox folder path. Include subfolders is enabled by default; turn it off to watch direct children only.
Connect Google Drive in all three Drive actions. Set Start in folder in Find or Create Folder, and choose the destination prefix while preserving the mapped relative directory. Do not use a folder monitored by an opposite-direction workflow.
Activate with a small existing folder and let the silent baseline finish. Add new files in the root and a subfolder, then verify that editing an older file does not create another copy. Manual step tests intentionally copy their selected sample.
One-way file content copying. No deletion propagation, rename/move reconciliation, permissions, comments or revision history. Old destination paths can remain after source moves. Unsupported or non-downloadable entries are skipped; ordinary files retain their bytes.
Transfer and folder bounds. This FastHook path supports files up to 25 MiB and at most nine nested source directory levels beneath the destination prefix. These are FastHook limits, not provider API limits. Empty files are supported; empty folders are not copied.
Initial inventory, webhooks and safety checks. The initial folder inventory continues in bounded checkpointed jobs. Verified Dropbox webhooks wake each folder source using its own cursor; periodic safety reconciliation catches missed notifications. New-only tracking retains at most 10,000 file IDs, including removed identities. An invalidated cursor or full identity ledger produces a visible error and requires deliberate intervention.
Yes. Relative paths are preserved by default. Turn off Include subfolders to copy only files directly inside the selected source folder.
No automatic copy is emitted for an identity already seen by the trigger. A manual action test can still copy its selected sample.
No. Downloadable Dropbox files are uploaded as ordinary Drive files with their original filename and bytes.
Use the separate Sync existing, new and updated Dropbox files to Google Drive template.
Copy existing Dropbox files and subfolders to Google Drive, then copy new files and update changed content in the same Drive file. Deletions are not propagated.
View template →