All nodes/Integrations/Files

WebDAV Config

Picks a saved WebDAV connection of this workspace (Nextcloud, ownCloud, Yandex.Disk, …) as the store for File Glob/Read/Write/Tool. Credentials live in workspace settings, never on the node.

Try it

When to use it

The node connects file nodes to a disk outside the platform: Nextcloud, ownCloud, Yandex.Disk or any server that speaks WebDAV. Internal files are WS Store; a directory on the server is Local FS Config, and only in development.

There is a second reason to pick it. A lazy file reference only turns into bytes for a connection-backed store, so an image or a PDF that has to reach a model or be attached to a reply can be delivered by File Read from WebDAV, but not from the built-in store.

How it works

All that stays on the node is the chosen connection. The address, the login and the password live in Settings → Integrations and are substituted at run time, bypassing the graph: the password appears neither in the node’s output nor in the run log.

The store root is the connection’s address plus its own root path. Every path and glob pattern on the file nodes is measured from there, and the Subfolder field on the file node itself does not apply in external mode — narrow the area in the connection or in the path instead.

The server’s answer is translated into a clear code: 404 is “not found”, 401 and 403 are “access denied”, 413 is “file too large”.

Common mistakes

• An account password instead of an app password. Yandex.Disk always rejects the account password, and Nextcloud does too once two-factor authentication is on.
• The site address instead of the DAV collection address. Nextcloud and ownCloud keep files under /remote.php/dav/files/<user>/, and the Yandex.Disk address looks like https://webdav.yandex.ru/. Pick the provider in the connection form and the address is filled in.
• Writing into a folder that does not exist. On WebDAV the node does not create collections: create the folder on the store first.
• Expecting the files in the Files tab. This is someone else’s disk; the tab shows the workspace store only.
• One node for two disks. It holds a single connection; a second server needs a second node.

Inputs

—

Outputs

Configuration