Dropbox n8n integrationAutomate Dropbox with n8n.

Writes a second copy of a file at another path and leaves the original exactly where it was.

• From Path: the path of the file to copy, written in full, like /invoices/original.txt, often {{ $json.path }} when an earlier node already carries it.
• To Path: the destination path, file name included, like /invoices/copy.txt.

Removes whatever sits at the path you give it. The field accepts a single file or a whole folder, so the blast radius depends entirely on how precise the path is.

• Delete Path: the path to delete, such as /invoices/2019/invoice_1.pdf. Build it from a value the workflow already knows rather than typing it by hand.

Pulls the file content into the workflow as binary data, so the next node can parse it, attach it to an email or push it somewhere else.

• File Path: the full path of the file, root included, like /invoices/2019/invoice_1.pdf.
• Put Output File in Field: the name of the output binary field the file lands in. The next node has to read that same name.

Changes where a file lives, and renames it in the same call when the new name is part of the destination path.

• From Path: where the file is now, like /invoices/old_name.txt.
• To Path: where it should end up, like /invoices/new_name.txt. Naming it from workflow data is how files get a consistent name.

Writes a file into Dropbox at the path you choose. The content comes either from binary data produced by an earlier node or from text written in the node itself.

• File Path: the full path, parent folder included. That parent has to exist, and an existing file at the same path gets overwritten.
• Input Binary Field: the name of the incoming binary field holding the file.
• Binary File: on, the data comes from a binary field; off, File Content holds the text to write.

Duplicates a folder to a second path. The original keeps its place in the tree and both paths exist afterwards.

• From Path: the folder to copy, written from the root of whatever the app has access to.
• To Path: the destination path of the copy.

Makes one folder at the path you write. The parent has to exist already, so building two levels means running the operation twice, outer level first.

• Folder: the folder to create, such as /invoices/2019, commonly assembled from workflow data like a date or a client name.

Takes a folder path out of the account. Because the path field also accepts a single file, the difference between removing one document and removing a branch is one line of text.

• Delete Path: the path to delete. A list step before it is the cheapest safety net, since it shows what is actually in there.

Returns the files and folders in a given folder, one item per entry, which is how most Dropbox workflows find out what they have to process.

• Folder Path: the path whose content gets listed, like /invoices/2019/.
• Return All: on, n8n pages through every entry; off, Limit caps how many come back.
• Recursive: in Filters, includes the content of every subfolder instead of the top level only.

Relocates a folder, everything under it following the path change. Renaming works the same way, since the last segment of the destination is the new name.

• From Path: the folder as it is filed today.
• To Path: the new path, which is also where a rename gets expressed.

Searches the account for a string and returns what matches, which saves guessing at a path when the file name is only half known.

• Query: the string to search for. It can match across several fields depending on the other arguments.
• File Status: active, or deleted to look through what was removed.
• File Categories: in Filters, narrows the results to types such as pdf, spreadsheet or image, which keeps a common word from returning half the account.
• Folder: in Filters, one path instead of the entire Dropbox.