Respond to Event

Controlled node

Overview

The Respond to Event node allows you to respond to Google Calendar event invitations programmatically. You can accept, decline, mark as tentative, or reset the response status for any event you have access to.

For recurring events, you can choose whether your response applies only to a specific instance or to the entire series. This is particularly useful for automating RSVP workflows or building scheduling assistants that can automatically respond to meeting requests based on specific criteria.

Connection Required

This node requires a Google Calendar connection to be configured in the properties panel. The connection determines which Google account will be used to send the response.

Inputs

Input	Type	Description	Default
Event ID	Text	The unique identifier of the calendar event to respond to.	-
Response Status	Enum	The response status to set for the event. Options: accepted, declined, tentative, needsAction.	accepted
Respond to Recurring	Enum	For recurring events, determines whether to respond to this event only or all events in the series.	all
Calendar ID	Text	The ID of the calendar containing the event. Use primary for the user's primary calendar.	primary
Run	Event	Fires when the node starts running.	-

Outputs

Output	Type	Description
Result	Data	Contains the response from Google Calendar API, including the updated event details or error information.
Done	Event	Fires when the node has finished processing the response.

Runtime Behavior and Defaults

When the node executes, it validates that an eventId and responseStatus are provided. If the event is part of a recurring series and respondToRecurring is set to all, the node automatically responds to the master event (the recurring series parent) so that the response applies to all instances.

The node handles the following response statuses:

• accepted: Confirms attendance to the event
• declined: Declines the event invitation
• tentative: Marks attendance as tentative/maybe
• needsAction: Resets the response status to "needs action" (removes previous response)

If the event is not found or the user lacks permission to respond, the result output will contain error details.

Example Usage

Scenario: Automatically accept meeting invitations from your team.

1. Connect a List Events node to find new events with specific criteria (e.g., containing "Team Meeting" in the title).
2. Connect the events output to a For Each node to process each event individually.
3. Inside the loop, connect to the Respond to Event node:
   • Set Event ID to the event's id field
   • Set Response Status to accepted
   • Set Respond to Recurring to all (if you want to accept the entire series)
   • Ensure the connections property is set to your Google Calendar connection
4. Connect the done event to trigger follow-up actions, such as sending a confirmation email or logging the acceptance to a database.

Note: When responding to recurring events, if you select this for respondToRecurring but the event ID provided is actually a recurring series master (not an instance), the node will respond to the master event as a fallback.