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 cleanup of files or folders on a remote WebDAV server.
  • Managing remote file storage by programmatically removing outdated or unwanted resources.
  • Integrating WebDAV file management into workflows that require conditional deletion based on other data processing steps.

Example use case: Automatically delete temporary files from a WebDAV server after processing them in a workflow.

Properties

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

Output

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

  • success (boolean): Indicates whether the deletion was successful (HTTP status code 2xx).
  • 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 a successful deletion:

{
  "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, specifically the DELETE method for this operation.

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 are rejected.
  • 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 will result in success being false. Check server permissions and path correctness.
  • Continue On Fail: If enabled, the node will continue processing remaining items even if some deletions fail, returning error messages in the output.

Links and References

Discussion