--- title: "Nextcloud Integration" description: "Manage files, folders, shares, and users on your own Nextcloud server from FlowRunner agents through the WebDAV and OCS APIs, authenticated with a scoped app password." url: https://flowrunner.ai/integrations/nextcloud date_modified: 2026-08-07T17:20:23-07:00 --- # Nextcloud [Storage](https://flowrunner.ai/integrations/category/storage) Manage files, folders, shares, and users on your own Nextcloud server from FlowRunner agents through the WebDAV and OCS APIs, authenticated with a scoped app password. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 15 actions · Basic auth · available [Nextcloud website](https://nextcloud.com/) · [Platform Documentation](https://docs.nextcloud.com/server/latest/developer_manual/client_apis/WebDAV/) · Capability data verified 2026-07-14 1. A flow produces a document that belongs on the Nextcloud server 2. Agent reads the file into the flow 3. Agent uploads the file to a remote path, creating parent folders as needed 4. Agent confirms the upload by listing the destination folder 5. Agent checks whether a cleanup step targets a folder with contents 6. Agent assembles the path and a count of what a delete would remove 7. A person confirms a recursive folder delete before it removes the contents ## What This Integration Enables The Nextcloud connector spans files, shares, and users. On files, agents upload from a source URL, download into FlowRunner file storage, list a folder's immediate contents, create folders, and move, copy, or delete items, with folder operations working recursively. On shares, agents create shares with a user, group, email, or public link, with an optional password and expiration, and they list, read, update, and delete shares. On users, agents read the current account, read a specific user, and list users for auditing or provisioning, subject to the account's permissions. The service talks WebDAV for file operations and OCS for shares and users, and parses both natively with no external dependencies. Some of these actions read and some destroy or expose; the connector supplies all of them, and the surrounding flow decides which need a person. ### Without FlowRunner **Files copied to the server by hand**: Documents get moved onto the server manually with no consistent structure **Public links created ad hoc**: Share links get made without a password or expiration and rarely revisited **Deletes run recursively unguarded**: A cleanup step can remove a folder and everything under it with no second look ### With FlowRunner **Files uploaded in the flow**: Documents land at a defined path, with parent folders created automatically **Public links scoped**: Share links carry a password and expiration and pause for review when external **Recursive deletes gated**: Folder deletion pauses for confirmation before it removes the contents ## Use Case Scenarios ### Archive to a Self-Hosted Server An agent finishes generating an invoice and uploads it to the Nextcloud server with Upload File at a path under the client's folder. Parent folders are created automatically if they do not exist, and the file overwrites cleanly on a re-run. The document lands on infrastructure the team controls, with no manual copy to the server. ### Password-Protected Public Link A flow needs to share a file with someone outside the team. The agent proposes a public link with a password and an expiration, waits for approval, then calls Create Share to generate it and posts the link and password through separate channels. The recipient gets access that expires on its own, and the share stays scoped. ### Pull for Processing The agent calls Download File to bring a document from the server into FlowRunner file storage, runs it through a parsing step, and records the extracted details in a knowledge base. The file stays on the team's own server as the source of record, and only a copy travels into the flow. ## Human-in-Loop Highlight Uploading, listing, and downloading files are safe operations a flow runs on its own. Deleting is different: a delete against a folder removes every file and subfolder under it recursively, and while the items land in the trash bin, a wrong delete can sweep away far more than intended. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) at the boundary between routine file work and a recursive removal. Before deleting a folder with contents, the agent pauses, assembles the path and a count of what the delete would remove, and routes to a person through their preferred channel. The message is specific: "This would delete the folder Projects/2024-Archive and all 214 files and subfolders under it. Confirm the deletion, or cancel?" The agent handles the uploads, the organization, and the sharing; a person owns the delete that clears a folder's contents. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 15 actions ### Files 7 - **Upload File** Uploads a file to Nextcloud via WebDAV from a source URL, creating parent folders as needed and overwriting any existing file. - **Download File** Downloads a file from Nextcloud via WebDAV into FlowRunner file storage and returns a URL to the stored copy. - **List Folder** Lists the immediate contents of a folder via a WebDAV PROPFIND, with each child's name, path, type, size, and last-modified time. - **Create Folder** Creates a new folder via WebDAV. The immediate parent folder must already exist. - **Delete** Deletes a file or folder via WebDAV, removing folder contents recursively. The item moves to the trash bin per the account's retention settings. Folder deletes with contents route through human confirmation. - **Move** Moves or renames a file or folder via WebDAV to a new full path, overwriting an existing item at the destination by default. - **Copy** Copies a file or folder via WebDAV to a new full path, duplicating folder contents recursively. ### Shares 5 - **Create Share** Creates a share for a file or folder via the OCS Sharing API, with a user, group, email, or public link, and optional password and expiration. - **List Shares** Lists the shares created by the account, optionally filtered by a specific file or folder path. - **Get Share** Retrieves the details of a single share by its numeric share ID. - **Update Share** Updates an existing share by ID, changing permissions, password, expiration, or note. - **Delete Share** Removes a share by its numeric ID, revoking recipient access without deleting the underlying file. ### Users 3 - **Get Current User** Returns the profile of the authenticated account, useful as a connection check. - **Get User** Returns the profile of a specific user by ID. Requires permission to view the user. - **List Users** Lists user IDs on the instance, optionally filtered by a search term. Requires permission to list users. ## Frequently Asked Questions ### What can FlowRunner do with Nextcloud? FlowRunner agents can run Upload File, Download File, and List Folder in Nextcloud, plus 12 more actions. ### Does connecting Nextcloud to FlowRunner require OAuth? No. Nextcloud connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Nextcloud trigger a FlowRunner workflow automatically? Nextcloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Nextcloud?** This integration exposes Nextcloud to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/nextcloud. Site index: https://flowrunner.ai/llms.txt