WebDAV icon

WebDAV

Interact with WebDAV servers for file operations

Overview

This node allows interaction with WebDAV servers to perform various file operations such as downloading, uploading, listing, creating directories, deleting, moving, and copying files or folders. The "Download File" operation specifically retrieves a file from a WebDAV server and outputs its content as binary data along with metadata.

Common scenarios for this node include:

  • Automating file retrieval from remote WebDAV servers.
  • Integrating WebDAV-hosted documents into workflows.
  • Backing up or processing files stored on WebDAV shares.

For example, you can use the "Download File" operation to fetch a PDF report stored on a company WebDAV server and then pass it to another node for further processing or emailing.

Properties

Name Meaning
Directory Name or ID Select or specify the directory (folder) on the WebDAV server where the target file is located.
File Name or ID Select or specify the exact file name or path within the chosen directory to download.
  • Both properties support choosing from dynamically loaded options or specifying values via expressions.
  • The "Directory" defaults to root if not specified.
  • Paths must be server-relative and start with "/".

Output

The output contains one item per input with the following structure:

  • json:

    • path: The requested file path on the WebDAV server.
    • contentType: MIME type of the downloaded file.
    • contentLength: Size of the file in bytes (if available).
    • lastModified: Last modification date/time of the file (if available).
    • etag: Entity tag for the file version (if available).
    • statusCode: HTTP status code returned by the server.
  • binary:

    • data: The actual binary content of the downloaded file, prepared for downstream nodes that handle binary data.

This structure enables easy access to both file metadata and content for further workflow steps.

Dependencies

  • Requires credentials containing the WebDAV server base URL and authentication details (e.g., username/password or token).
  • The base URL must include the protocol (http:// or https://) and be correctly configured in the credentials.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Invalid Base URL: If the base URL is missing or does not start with http:// or https://, the node will throw an error. Ensure the credential's base URL is correct and includes the protocol.
  • Absolute URLs in Path: Paths must be relative to the server root and start with /. Absolute URLs are not allowed and will cause errors.
  • Host Not Found / Connection Refused: Check network connectivity and server hostname configuration.
  • Timeouts: May indicate slow server response or network issues.
  • Unexpected Data Type: If the server returns JSON instead of binary data for a file download, the node throws an error indicating a possible misconfiguration or unexpected server response.
  • Missing Binary Property: When uploading files, ensure the specified binary property exists in the input data.

To resolve these issues, verify credentials, paths, network access, and input data correctness.

Links and References

Discussion