Connect Nextcloud with n8n: Automate files, folders, and sharing

n8n connects to Nextcloud via a dedicated node for files, folders, and user accounts, as well as via the HTTP-Request node for everything this node does not cover. For organizations that do not want to host their document storage with Microsoft or Google for data protection reasons, the combination is the obvious self-hosted alternative to SharePoint workflows, since both systems run on their own or European infrastructure, and automation remains completely under your own control. Typical use cases are automatic receipt filing, sharing with external partners, and connecting to forms or email mailboxes. Status: August 2026.

What Nextcloud operations does the n8n node support?

The native Nextcloud node supports three resources: files, folders, and users.

• Files: Copy, delete, download, move, share, and upload.
• Folders: Copy, create, delete, retrieve contents, move, and share.
• Users: Invite, delete, retrieve individual or multiple user data, and edit attributes.

The node can also be used as a tool for AI agents, allowing an agent to independently decide which Nextcloud operation to perform. For anything not covered by this list, such as Talk messages or advanced sharing settings, the documentation recommends the HTTP-Request node with the same credentials as a fallback.

How do you set up Nextcloud credentials in n8n?

n8n supports two authentication methods for Nextcloud credentials: Basic Auth and OAuth2.

• Basic Auth: WebDAV URL from your Nextcloud domain plus /remote.php/webdav/, username, and an app password instead of your regular account password.
• OAuth2: Authorization and access token URLs from your Nextcloud instance, client ID and client secret from the administrator security settings, and n8n's OAuth callback URL as the redirection URI.

The WebDAV URL differs depending on whether Nextcloud runs at the domain root or in a subdirectory. In practice, this is one of the most common stumbling blocks during initial setup, even before actual credential errors.

What is the most common reason for connection failures in practice?

According to reports in the n8n forum, the most common cause of errors is rarely authentication itself, but rather the WebDAV URL and HTTP methods blocked by an upstream reverse proxy.

• 405 errors when listing or uploading files because the proxy in front of Nextcloud blocks the PUT method.
• ECONNREFUSED on port 443, usually with self-signed certificates or incorrect port mapping between Docker containers.
• 404 errors when moving files if the destination path does not exactly match the WebDAV structure.

The official documentation describes both authentication methods but does not mention these error patterns. For practical troubleshooting, it is worth taking an additional look at the n8n community section before adjusting your credentials.

How do you implement sharing and notifications?

File and folder sharing works through the native share operation, which creates a shared link or direct user share. Nextcloud Talk is not supported by the node, however, because Talk is not one of the three supported resources. To send notifications to Talk channels, you must rebuild them using the HTTP-Request node and the general Nextcloud API without the convenience features of a dedicated node. For setting up a complete, GDPR-compliant automation workflow around n8n and Nextcloud, NordFlux supports implementation.

Frequently asked questions about n8n and Nextcloud

Can n8n automate Nextcloud Talk?

Not directly via the dedicated node, as it only covers files, folders, and users. Talk messages can be controlled via the HTTP-Request node and the Nextcloud API, but with more manual configuration effort than the natively supported operations.

Do I need OAuth2 or is Basic Auth sufficient?

For most internal automations, Basic Auth with an app password is sufficient. OAuth2 makes sense if multiple applications access the same Nextcloud instance and access rights need to be revoked individually without changing the central password.

Why do I get a 405 error when uploading?

This almost always indicates a reverse proxy blocking or rewriting the HTTP PUT method. Check the proxy configuration in front of Nextcloud first, not your n8n credentials, as that is where the cause lies in most reported cases.

Can I control Nextcloud completely without the dedicated node?

Yes, via the HTTP-Request node with the same credentials. This is the documentation-recommended approach for anything not covered by the Nextcloud node, such as advanced sharing settings or Talk.