
The calendar integration brings calendars into Home Assistant: a local calendar, CalDAV, Google Calendar, and more.
An automation can put an event in a calendar with calendar.create_event, and that is where it ends. Calendars that can delete an event do so only when asked from the calendar panel. Spook adds the action to take an event out again.
Deleting an event goes by its uid, an identifier every event has, and calendar.get_events leaves that out of what it returns. So Spook finds events the way an automation can: by their title, in a stretch of time.
Devices & entitiesΒΆ
Spook does not provide any new devices or entities for this integration.
ActionsΒΆ
Spook adds the following new actions to your Home Assistant instance:
Delete eventΒΆ
Delete events from a calendar, found by their title or their uid in a stretch of time.
Action properties | |
|---|---|
Calendar: Delete event π» | |
| |
Yes, | |
Optional, the events deleted | |
Added action | |
Action data parameters | |||
|---|---|---|---|
Attribute | Type | Required | Default / Example |
| No, but this or | Dentist | |
| No, but this or | ||
| No | Now | |
| No, but this or | 2026-10-04 20:00:00 | |
| No, but this or |
| |
| No |
|
Events are looked for from start_date_time, which is now when you leave it out, until end_date_time or for duration, the same way calendar.get_events reads them. Every event in that stretch with exactly that summary, or that uid, or both, is deleted.
An event that repeats is found occurrence by occurrence, and only the occurrences found are deleted. Set whole_series to delete the whole series instead.
When nothing matches, nothing happens. That is not an error: βdelete it if it is thereβ is how an automation tidies up after itself.
The response lists every event deleted, for each calendar, with its uid, recurrence_id, summary, start and end.
Take out the reminder an automation put in earlier today:
1 2 3 4 5 6 7action: calendar.delete_event target: entity_id: calendar.family data: summary: Take the bins out duration: hours: 24
Known limitations
A
summaryor auidis required. A stretch of time alone would delete everything in it, which is how a calendar gets emptied by accident.The title has to match exactly, including capitals.
Only calendars that can delete events can be targeted. A read-only calendar, like a holiday feed, refuses the action.
An event the calendar gives no uid cannot be told apart from any other, so it is left alone.
RepairsΒΆ
Spook has no repair detections for this integration.