Delete Event: Google Calendar action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Calendar ID calendar_id	string	Required	Use 'primary' for the user's main calendar, or a specific calendar ID
Event ID event_id	string	Required	The unique identifier of the event to delete
Send Notifications sendUpdates	options	Optional	Whether to send cancellation notifications to attendees

Sample request

{
  "calendar_id": "primary",
  "event_id": "e.g. abc123def456",
  "sendUpdates": "{{trigger.sendUpdates}}"
}

Returns

{
  "success": true,
  "deleted_event_id": "abc123def456"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Delete Event.

What does the Delete Event action do in Google Calendar?

Deletes an event from a Google Calendar by ID. Pass sendUpdates=all to notify attendees of the cancellation; recoverable from Calendar trash.

What inputs does Delete Event require?

Required: Calendar ID, Event ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Google Calendar returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Event support batch operations?

Yes. Run Delete Event inside a Loop node to process arrays. Tiny Command handles Google Calendar's rate limits automatically so you don't have to throttle manually.

More actions