Actions7
Event → Delete Event
AI-generatedOverview
This node integrates with Zoho Calendar to manage calendar events programmatically. Specifically, the Delete Event operation allows users to remove an event from a specified calendar by providing the unique identifiers of both the calendar and the event.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or canceled events.
- Synchronizing external systems by removing events that no longer exist elsewhere.
- Managing calendar data in bulk workflows where events need to be deleted based on certain conditions.
For example, you could use this node in a workflow that listens for cancellations in a booking system and automatically deletes the corresponding event from Zoho Calendar.
Properties
| Name | Meaning |
|---|---|
| Calendar UID | The unique identifier (UID) of the calendar from which you want to delete the event. |
| Event UID | The unique identifier (UID) of the event you want to delete from the specified calendar. |
Output
The output JSON contains a field named zohoResponse which holds the response from the Zoho Calendar API after attempting to delete the event. This typically includes status information about the deletion request.
No binary data is output for this operation.
Example output structure:
{
"zohoResponse": {
// API response details confirming deletion or error info
}
}
Dependencies
- Requires an active Zoho Calendar API OAuth2 authentication credential configured in n8n.
- The node makes HTTP requests to Zoho Calendar's REST API endpoints.
- Timezone handling uses the
moment-timezonelibrary internally but is abstracted away from the user.
Troubleshooting
Common issues:
- Providing incorrect or non-existent Calendar UID or Event UID will cause the API to fail to find the event.
- Missing required properties (
calendarIdoreventId) will result in validation errors before the request is sent. - Authentication failures if the OAuth2 token is expired or invalid.
Error messages:
- Errors returned from the Zoho API will be included in the node’s error output.
- If the event does not exist, the API may return a 404 Not Found error.
- If the ETag header used for concurrency control is missing or stale, deletion might fail; however, the node fetches the current ETag before deleting to avoid this.
Resolution tips:
- Double-check the UIDs for accuracy.
- Ensure the OAuth2 credentials are valid and have necessary permissions.
- Review API rate limits or quota restrictions on your Zoho account.