Skip to content
Nappai Documentation

Google Calendar Webhook

Google Calendar Webhook starts a flow every time an event changes in a Google calendar: when a new one is created, when an existing one is modified, or when one is cancelled or deleted.

NappAI checks the calendar about once a minute and, if it finds changes, runs the flow with the details of each event affected. You don’t have to set anything up in Google: the credential and subscribing the flow are enough.

When to use it

  • You want to notify your team by email or messaging when someone books a meeting in the shared calendar.
  • Every new event should be recorded in a spreadsheet or in your CRM.
  • When an appointment is cancelled, you want to free the slot in another system or let the customer know.
  • You want an AI agent to prepare a briefing for every meeting added to the calendar.

Configuration

You need a Google Calendar credential, which connects by signing in with your Google account. See Credentials.

FieldWhat it does
Credential (required)The Google Calendar credential of the account you want to watch.
CalendarThe calendar being watched. Click the refresh button to load the list of your calendars. If you leave it empty, your primary calendar is watched.
EventsThe changes that start the flow: Event Created (an event is created), Event Updated (an event is modified) and Event Deleted (an event is cancelled or deleted). Default: all three. If you choose none, all three are used.
DataTest field. It lets you try the flow with a sample event without waiting for a real change in the calendar. Leave it empty in normal use.

Turn on the subscription

The flow only receives changes when it is subscribed:

  1. Save the flow and publish a version. You need a published version of the flow to subscribe. See Versions and publishing.
  2. In the node’s settings panel, click Subscribe.
  3. In the panel that opens, click Subscribe. The status changes to Synced.

Only changes that happen after you subscribe come through. If you later change the calendar or the events, the status shows Out of sync: subscribe again to apply the changes. From the same panel you can Unsubscribe when you no longer want to receive changes.

Output

The Data output contains one item per event that changed, with the type of change (created, updated or deleted), the event ID (eventId), its title (summary), start and end, its status and the organiser’s email. If several changes arrive at once, they all come out together.

Connect it to Calendar Event to look up or change the event, to an AI agent, or to an email or messaging component.

Example

An agency wants to tell its sales team about every new customer meeting.

  1. Add Google Calendar Webhook, choose the agency’s Google Calendar credential and the Customer meetings calendar in Calendar.
  2. In Events keep only Event Created.
  3. Connect the Data output to an email component that sends the team the meeting title and time.
  4. Publish the flow and click Subscribe.

Good practices

  • Choose only the events you need: the flow runs fewer times and only with what matters to you.
  • If the flow creates or changes events in the same calendar it watches, it will run again with its own changes. Use another calendar or filter inside the flow.