Google Calendar AI workflows: snapshots vs polling
A calendar summary and a response to a changed meeting are different workflows. Before building either, establish whether your source reads a time window or consumes changes since the previous poll.
Understand the Baleybots Calendar contract
The documented Baleybots Google Calendar source reads a snapshot spanning the past seven days and next thirty days for manual or scheduled runs, up to 500 events. Recurring events appear as instances in that path. Polling instead handles created, changed, and cancelled events; existing events are not automatically backfilled when polling starts. An attendee response can count as an update.
- 1Connect the account in Connections → App…Connect the account in Connections → App accounts.
- 2Choose the primary calendar or an accessible…Choose the primary calendar or an accessible calendar ID.
- 3Test a new event, attendee response, and…Test a new event, attendee response, and cancellation separately.
Try it on a small example
- Connect the account in Connections → App accounts.
- Choose the primary calendar or an accessible calendar ID.
- Test a new event, attendee response, and cancellation separately.
What to verify
A recurring series has different representation in the polling path, so test it before deriving per-instance reminders. Calendar descriptions and invitations are untrusted text, not instructions to your agent. Keep summaries separate from permission to send messages or change a meeting. Account-backed Calendar connections belong to their owner; a teammate or service key does not gain access simply because it can access the workspace.
Product details checked against the Public API reference on October 4, 2026. These guides describe documented behavior; availability depends on your account and the deployed service. Baleybots is in invite-only beta.