Overview
This node is designed to interact with CalDAV events, specifically allowing users to delete an event from a calendar. It is useful in scenarios where you want to programmatically remove calendar events based on their unique identifiers (handles). For example, after fetching events, you might want to delete one or more specific events automatically as part of a workflow.
Properties
| Name | Meaning |
|---|---|
| Event Handle | The handle of the event to delete. This is a JSON object containing the event's URL and etag. You can pass this directly from a previous fetch operation that retrieved event details. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the event was successfully deleted or provide relevant status information. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the CalDAV service.
- The node depends on the CalDAV protocol and the corresponding API endpoint to manage calendar events.
- Proper configuration of the CalDAV credentials within n8n is necessary for successful execution.
Troubleshooting
- Common issues:
- Providing an invalid or incomplete event handle (missing URL or etag) will cause the deletion to fail.
- Authentication errors if the API key or credentials are incorrect or expired.
- Network connectivity problems when reaching the CalDAV server.
- Error messages:
- Errors related to "not found" or "event does not exist" indicate the event handle may be outdated or incorrect.
- Authorization errors suggest checking the API key or permissions.
- Resolutions:
- Ensure the event handle is obtained freshly from a fetch operation before attempting deletion.
- Verify API credentials and renew them if necessary.
- Confirm network access to the CalDAV server.
Links and References
- CalDAV Protocol Specification
- CalDAV Overview - Wikipedia
- n8n Documentation on Creating Custom Nodes