Actions4
- Calendar Actions
- Event Actions
Overview
This node interacts with a CalDAV server to manage calendar events. Specifically, the "Delete Event" operation removes a specified event from the calendar on the server. This is useful in scenarios where you want to programmatically clean up or cancel events based on certain conditions or workflows.
For example, if you have an automated system that tracks event cancellations or changes, this node can delete outdated or canceled events directly from the CalDAV calendar, ensuring your calendar stays up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Event URL or ID | The unique identifier of the event to delete. This identifies exactly which event should be removed. It corresponds to the event's URL or ID found in the _handle.URL field when fetching events. |
| Event Version Tag (ETag) | A version tag for the event used to prevent conflicts during deletion. It ensures that the event has not been modified since it was last fetched. This corresponds to the _handle.etag field and helps avoid accidental deletions. |
| Additional Options | Optional settings: • Include Server Response: Whether to include the full server response in the output. Useful for debugging or verifying the deletion status. |
Output
The node outputs JSON data representing the result of the deletion operation. If the "Include Server Response" option is enabled, the output will contain the complete server response, which may include status codes or messages confirming the deletion.
No binary data is produced by this operation.
Dependencies
- Requires access to a CalDAV server.
- Needs appropriate API credentials or authentication tokens configured in n8n to connect securely to the CalDAV server.
- The node depends on internal helper methods and actions defined in the bundled source code to perform the deletion.
Troubleshooting
Common Issues:
- Providing an incorrect or malformed Event URL/ID will cause the deletion to fail because the node cannot locate the event.
- Using an outdated or incorrect ETag value may lead to conflict errors, as the event might have been modified since it was last fetched.
- Network or authentication issues with the CalDAV server can prevent successful deletion.
Error Messages:
- "unknown resource" — indicates the resource parameter is invalid; ensure "event" is selected.
- Conflict or version mismatch errors suggest the ETag does not match the current event version; refetch the event to get the latest ETag.
- Authentication errors indicate missing or invalid credentials; verify API keys or tokens are correctly set up.