Google Calendar
Run an automation when a Google Calendar receives a new or updated event.
What it does
Watches a Google Calendar via OAuth and fires the workflow when events are added or modified. Compared to the generic ICS trigger, this version supports private calendars, gets richer event data (organizer, attendees, status, links), and authenticates as a specific user instead of via a public feed.
The integration requires a one-time OAuth connection. After connecting, the integration remembers the calendar list and lets you pick which one to watch.
What you configure
| Field | What it controls | Required | Notes |
|---|---|---|---|
| OAuth connection | The Google account whose calendar you watch. | required | Click Connect to run the OAuth flow. The token is stored encrypted and refreshed automatically. |
| Calendar | Which of the connected account's calendars to watch. | required | Populated from the OAuth account; pick from the dropdown. |
| Poll interval | How often to check for new events, in milliseconds. | optional | Default is 60 000 (once per minute). |
| Output name (memory output) | Where the event data is stored. | required | Includes id, summary, description, start, end, location, status, link, organizer, attendees. |
📷 SCREENSHOT: The Google Calendar trigger configuration mid-OAuth: the "Connect to Google" button replaced by a "Connected as patrick@example.com" badge.
Example scenario
Auto-create meeting notes documents. Every time a meeting with at least three attendees is added to the team calendar, a workflow creates a pre-formatted meeting-notes file with the title, attendees, and date filled in, and emails the link to the organizer the morning of the meeting.
Recommendations
- ✅ Use a dedicated Google account for the AI Kit. Personal accounts mean the workflow breaks when the owner leaves.
- ✅ Share the relevant calendar with that dedicated account explicitly. Owning the account is not the same as having the calendar visible.
- ✅ Treat the OAuth connection as a credential. If the user revokes access on Google's side, the trigger stops firing — you will see it in the Trigger Monitor.
- ⚠️ Read-only scope is requested by default. Granting wider scopes manually does not enable wider operations from the workflow.
- ❌ Do not connect the same Google account from multiple AI Kit installations simultaneously. Token-refresh races can drop one of the connections.
What to do next
- For generic calendars: Calendar (ICS).
- To act on the events the trigger emits: LLM Prompt, Send E-Mail, File Writer.