Google Actions
Delete Calendar Event
Cancel a pending event by command
Bot /cancel → delete event stored in vault → confirm
Telegram Bot
Bot Update
userID
Delete Calendar Event
eventId
{{vault.PENDING_EVENT}}
error
Telegram Bot
Send Message
chatId
userID
text
Event canceled
Delete an event from your primary Google Calendar by id. Attendees are notified by email — Google handles the cancellation message on its side.
Inputs
| Input | Type | Description |
|---|---|---|
| eventId | string | Required. The event id (returned by Create / List / Get Event). |
Outputs
| Output | Type | Description |
|---|---|---|
| error | string | Empty on success. Contains Google's error message when status is ERROR. |
Idempotent behaviour
If the event is already gone (Google returns 410 Gone), the action is treated as success — your intent ("make this event go away") is satisfied. Only 404 Not Found for an id that never existed surfaces as ERROR.
Permissions required
Same scope as other Calendar actions — Manage Calendar events (calendar.events). If unchecked in the wizard, the run fails with 403.
Example use cases
- Cancel after rejection — flow watches for a
cancelTelegram command, looks up the user's pending event by id stored in vault, deletes it. - Cleanup after test runs — automation flow creates a probe event, runs checks, then deletes via the saved
eventId. - TTL-style events — scheduled flow lists events older than X days with a known tag in
summary, deletes them one by one.
Errors you might see
error output | Meaning |
|---|---|
eventId is required | The eventId input was empty / whitespace. |
Not Found | No event with that id on the primary calendar. |
Insufficient Permission | Connection lacks calendar.events. Reconnect with the box checked. |
Google connection has been revoked — reconnect it from the Connections page. | The user revoked Fainflow on Google's side, or refresh token expired. |