Pipedream Dropbox → n8n
5 Pipedream Dropbox actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: dropbox.
Actions
| Pipedream action | n8n | Fit |
|---|---|---|
| dropbox-upload-file | Dropbox file → upload | Check output |
| dropbox-create-folder | Dropbox folder → create | Check output |
| dropbox-download-file-to-tmp | Dropbox file → download | Check output |
| dropbox-search-files-folders | Dropbox search → query | Check output |
| dropbox-list-file-folders-in-a-folder | Dropbox folder → list | Check output |
Triggers (event sources)
| Pipedream trigger | n8n | Fit |
|---|---|---|
| dropbox-new-file | Schedule Trigger + polling | Partial |
| dropbox-all-updates | Schedule Trigger + polling | Partial |
Credentials
Create a Dropbox credential in n8n (type dropboxOAuth2Api). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.
What "Fit" means
Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.
Questions
Does n8n have a Dropbox node?+
Yes. 5 of the 5 Pipedream Dropbox actions listed here map to a native n8n node.
Will my Pipedream Dropbox connection move to n8n?+
No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Dropbox credential in n8n (type dropboxOAuth2Api) and select it on the converted nodes.
Are Pipedream Dropbox triggers supported in n8n?+
n8n has no trigger node for these Dropbox events. Converted workflows use a Schedule Trigger that polls the API, or a Webhook node registered in Dropbox.
What happens to code steps that call the Dropbox API?+
Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.