WebDAV icon

WebDAV

Interact with WebDAV servers for file operations
Join our community

Actions7

Overview

This node enables interaction with WebDAV servers to perform file operations such as deleting files or directories, uploading, downloading, moving, copying, and listing files or directories. Specifically, the "Delete Resource" operation deletes a specified file or directory on the WebDAV server.

Common scenarios for this node include:

  • Automating file management tasks on remote WebDAV servers.
  • Cleaning up files or folders after processing.
  • Integrating WebDAV storage into workflows for backup or synchronization purposes.

For example, you can use this node to delete temporary files created during a workflow or remove outdated documents from a shared WebDAV folder.

Properties

Name Meaning
Path The path to the file or directory to delete on the WebDAV server. Must start with "/". Spaces and special characters are automatically URL-encoded.

Output

The output is an array of JSON objects, each corresponding to an input item processed. For the Delete operation, each output object contains:

  • success (boolean): Indicates whether the deletion was successful (HTTP status code in the 200 range).
  • statusCode (number): The HTTP status code returned by the WebDAV server.
  • path (string): The path of the resource that was requested to be deleted.

Example output JSON for one item:

{
  "success": true,
  "statusCode": 204,
  "path": "/path/to/resource"
}

No binary data is output for the delete operation.

Dependencies

  • Requires credentials containing the WebDAV server base URL and authentication details (e.g., API key or username/password).
  • The base URL must include the protocol (http:// or https://) and be correctly configured in the credentials.
  • The node uses HTTP methods defined by the WebDAV protocol to communicate with the server.

Troubleshooting

  • Invalid Base URL: If the base URL in credentials is missing or does not start with http:// or https://, the node will throw an error. Ensure the URL includes the protocol and is correct.
  • Absolute URLs in Path: Paths must be server-relative starting with /. Absolute URLs in the path parameter cause errors.
  • Connection Errors: Common network errors like host not found, connection refused, or timeout may occur if the server is unreachable or credentials are incorrect.
  • HTTP Errors: Non-success HTTP status codes indicate failure. The node reports these with the status code and message.
  • Continue On Fail: If enabled, the node continues processing other items even if some fail, returning error messages per item.

Links and References

Discussion