Existing, new and updated files
Inventory the selected folder tree, then emit new files and changed revisions.
Workflow template
Copy existing Dropbox files and subfolders to Google Drive, then copy new files and update changed content in the same Drive file.
How it works
Inventory the selected folder tree, then emit new files and changed revisions.
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
Content revisions update the existing Drive file. Relative subfolders are preserved.
Dropbox sync/ 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.
Try a small text file, a binary file in a nested folder and an empty file. After the initial copy, change the text file and check that its Drive ID stays the same.
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.
Content updates reuse the Drive file matched by its Dropbox business identity and destination folder. Renames and moves are not reconciled.
No. Downloadable Dropbox files are uploaded as ordinary Drive files with their original filename and bytes.
Use the separate Copy new Dropbox files to Google Drive template, which establishes a silent baseline.
Establish a silent Dropbox folder baseline, then copy newly observed files and subfolders to Google Drive. Ignore edits to known files and preserve relative paths.
View template →