Nextcloud n8n integrationAutomate Nextcloud with n8n.

Duplicates a document and leaves the original untouched, so the copy can be edited, shared or archived on its own.

• From Path: the path of the file to copy, starting with a slash, as in /invoices/original.txt. Coming from an earlier node, write it as an expression such as {{ $json.path }}, the n8n syntax for reading a field off the incoming item.
• To Path: where the duplicate lands, also starting with a slash, for example /invoices/copy.txt.

Erases the target from the instance. Nextcloud's own retention rules decide what happens next, and n8n returns no copy of what was removed.

• Delete Path: the path to remove, starting with a slash, for instance /invoices/2019/invoice_1.pdf. The same field accepts a whole folder, which is why a typo here is expensive.

Pulls the file out of Nextcloud and into the workflow, where the next nodes can parse it, attach it to a message or forward it elsewhere.

• File Path: the full path of the file to fetch, starting with a slash, such as /invoices/2019/invoice_1.pdf. Partial paths fail.
• Put Output File in Field: the name of the output binary field that will hold the file. Downstream nodes expect that exact name, so keep it consistent across the workflow.

Changes where a document lives. Nothing is duplicated: the file leaves the old path and only exists at the new one afterwards.

• From Path: the current path of the file, as in /invoices/old_name.txt.
• To Path: the new path. Change the last segment and you have renamed the file instead of relocating it, which is the trick behind most naming conventions.

Opens one document to someone outside the folder, either by link or by naming the recipient.

• File Path: the full path of the file to share.
• Share Type: who receives it, chosen among Public Link, User, Group, Email and Circle.
• User, Group ID, Email or Circle ID: the recipient, matching the type selected above.
• Options: Password protects the share, and Permissions sets what the recipient can do, from Read alone to All.

Writes a document into the instance. This is the operation most workflows end on, because Nextcloud is usually where things get stored rather than where they start.

• File Path: the absolute destination path. The parent folder has to exist already, and an existing file at that path gets overwritten.
• Binary File: on for a real file coming from a previous node, off to write text.
• Input Binary Field: the name of the incoming binary field holding the file.
• File Content: the text to write when Binary File stays off.

Reproduces a directory and what it contains at a second location, original included. Useful when a structure has to exist twice rather than move.

• From Path: the folder to copy, starting with a slash.
• To Path: the destination path, which must not collide with an existing directory unless you intend to write into it.

Adds a directory at the path you give. Run it before any upload that targets a place which may not exist yet.

• Folder: the path to create, starting with a slash, for example /invoices/2019. Only the last level is created: the parent has to be there already, so a deep tree needs one call per level.

Removes a directory and everything under it in one call. There is no dry run and no per-file confirmation.

• Delete Path: the path to remove, starting with a slash. Point it at a directory and the whole subtree goes, which is exactly what makes this operation worth guarding with an IF node before it.

Returns the contents of a directory, one item per entry, which the workflow can then filter, count or loop over.

• Folder Path: the directory to read, starting with a slash, such as /invoices/2019/. Left empty, the node reads the root of the WebDAV URL set in the credential.

Relocates a directory with its contents. The tree keeps its shape, only its parent changes.

• From Path: the current folder path.
• To Path: the new path. Moving a large tree in a single call can take a while, which is why some workflows prefer to list the folder and move its files one by one.

Grants access to a whole directory, so anything added to it later is visible to the recipient without a second share.

• File Path: the full path of the folder to share.
• Share Type: Public Link, User, Group, Email or Circle.
• User, Group ID, Email or Circle ID: whoever receives the access.
• Options: Permissions decides between Read, Create, Update, Delete or All, and Password locks a public link.

Invites someone to the Nextcloud organization. The account is created and the invitation goes to the address you provide.

• Username: the identifier the person will log in with, like john. Every other user operation takes this same value, so decide the naming rule once.
• Email: where the invitation lands.
• Additional Fields: Display Name sets the readable name shown across the instance.

Closes an account on the instance. Run it at the end of an offboarding chain, after the files that account owned have been moved or copied somewhere shared.

• Username: the identifier of the account to remove, not the display name and not the email address. Read it back with a get operation first if the workflow only knows the person by name.

Reads back one account and returns its attributes, which the workflow can then test before doing anything else.

• Username: the identifier to look up. Pass it from a previous node with {{ $json.userId }} when the value comes out of an earlier step.

Walks the account directory and returns the list, one item per user.

• Return All: on, n8n follows the API pages until every account is returned; off, it stops at Limit.
• Limit: the ceiling on how many accounts come back.
• Options: Search narrows the list to matching accounts, and Offset skips the first ones, handy for processing a directory in slices.

Edits attributes on an account that already exists, without touching anything you leave alone.

• Username: the account to edit, for instance john.
• Update Fields: the attributes to change, added one at a time from the option list. An empty collection means the node runs and changes nothing, which is easy to miss when a workflow silently reports success.