Quick answer: To connect AI to Google Calendar, use one of three routes: the calendar owner’s OAuth consent, a Workspace service account with domain-wide delegation, or a booking layer such as Calendly. For a calendar the account owns, grant calendar.freebusy plus calendar.events.owned, not full calendar access. The AI runs freeBusy, then events.insert with an explicit time zone. A self-built app left in Google’s Testing mode loses access after 7 days.
This page covers the Google side of the connection: access, OAuth scopes, the two API calls behind every booking, and the Workspace settings that block it. Every Google fact comes from Google’s own developer, Cloud, Workspace Admin or Calendar help pages, read on 28 October 2026. For what each voice-agent vendor’s calendar tools can do (reschedule, cancel, double-booking), see how deep AI agent calendar booking integrations go. For choosing between a calendar assistant, a booking page, an AI receptionist and a messaging agent, see how to use AI to schedule appointments.
Where Zian fits in a Google Calendar booking setup
Zian AI is the platform pick when the bookings start as phone calls or messages rather than clicks on a booking page. Its agents answer inbound calls 24/7 as an AI receptionist, qualify and book, and set appointments from inbound and outbound voice, SMS, email, WhatsApp, Instagram DM and Facebook Messenger conversations, with an Appointment Show-Specialist for follow-up and 30+ languages. zian.ai lists connections to “CRM, comms, calendars, knowledge bases, and more” plus an API, and names HubSpot, Salesforce, HighLevel and Zapier integrations; the home and Features + Integrations pages we read do not name Google Calendar specifically as at 28 October 2026, so ask which calendar route your account will use and run the eight checks against it. Zian has set 64,521+ qualified sales appointments. It is in a partnership-application beta: each of its three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application, and no prices are published. For a done-for-you service, LeadsNow.ai runs on Zian, charges per result and answers leads in under 60 seconds, 24/7.
How to connect AI to Google Calendar: the three ways in
There are three practical ways for an AI booking tool to reach Google Calendar, and the route decides who has to click “Allow”, what breaks the connection, and how much data the tool can touch. Google’s Calendar API scopes page says to “choose the most narrowly focused scope possible and avoid requesting scopes that your app doesn’t require”, and the three routes differ mainly in who makes that choice.
| Route | Who grants access | Fits when | Google’s catch | Google source |
|---|---|---|---|---|
| 1. OAuth user consent | Each calendar owner signs in and approves the scopes on Google’s consent screen | One to a handful of calendars; personal Google accounts or Workspace; most off-the-shelf AI tools | Refresh tokens stop working for six listed reasons (a seventh applies only to Cloud Platform scopes); a Testing-mode app’s tokens expire in 7 days; an unverified app is capped at 100 new users | Using OAuth 2.0 to Access Google APIs |
| 2. Service account with domain-wide delegation | A Workspace super administrator, once, for the whole domain | An in-house build that books into many staff calendars inside one Google Workspace domain | Google says it grants access “without requiring their consent”; changes can take up to 24 hours; a service account needs delegation to add attendees | Control API access with domain-wide delegation |
| 3. A booking layer the AI books through | The calendar owner connects Google once to the scheduler or CRM; the AI only talks to that layer | You want buffers, minimum notice and conflict calendars enforced by a scheduler (Calendly, a CRM calendar) rather than by the AI’s prompt | The layer’s own Google connection is still OAuth (route 1), so it can be revoked or under-granted; Google’s own appointment schedules default to a 4-hour minimum lead time | Create an appointment schedule |
The practical rule: use a tool on route 1 or 3 unless you are building in-house for one Workspace domain with a super administrator willing to own the delegation. When the booking should land in a CRM first, route 3 fits; the trade-offs between native, Zapier and API connections are covered in AI agent CRM integration patterns.
Your day-one setup, whichever route you pick:
- Pick the one calendar the AI books into, and list every calendar that makes the person busy (personal, team, secondary).
- Find that calendar’s ID. Google’s events.insert page says to call calendarList.list for IDs, or use the keyword “primary” for the signed-in user’s main calendar.
- Choose the narrowest scopes from the scope chooser below and confirm the tool requests nothing more.
- Connect the account (consent screen, delegation, or the scheduler’s Connect button).
- Run the eight-check booking connection test further down.
You are finished when a test booking lands on the right calendar at the right local time, a retried request does not create a second event, and a revoked connection makes the AI hand over to a person instead of confirming a booking that does not exist.
Which Google Calendar scope does an AI booking agent need?
An AI booking agent needs two permissions: read busy time, and write one event. Google’s scopes page lists 20 Calendar scopes as at 28 October 2026. The broadest is the full calendar scope, which Google describes as “See, edit, share, and permanently delete all the calendars you can access”. The scope chooser below maps each booking job to the narrowest scope Google accepts for the call that does it.
| What the AI needs to do | Minimum scope (Google’s own wording) | What it exposes if the token leaks | Google source |
|---|---|---|---|
| Check whether a slot is free (freeBusy) | calendar.freebusy: “View your availability in your calendars”, or calendar.events.freebusy: “See the availability on Google calendars you have access to” |
Busy start and end times only; no event titles | Freebusy: query |
| Find the calendar ID to book into | calendar.calendarlist.readonly: “See the list of Google calendars you’re subscribed to” |
Calendar names and the account’s access role on each | CalendarList |
| Read the calendar’s default time zone | calendar.calendars.readonly: “See the title, description, default time zone, and other properties” |
Calendar properties; no events | Choose Google Calendar API scopes |
| Create, move or cancel bookings on a calendar the account owns | calendar.events.owned: “See, create, change, and delete events on Google calendars you own” |
Every event on calendars the account owns, readable and editable | Events: insert |
| Create bookings on a calendar shared with the account (not owned) | calendar.events: “View and edit events on all your calendars” |
Every event on every calendar the account can edit | Events: insert |
| Write bookings only to a dedicated calendar the app creates | calendar.app.created: “Make secondary Google calendars, and see, create, change, and delete events on them”, plus a free/busy scope for the person’s other calendars |
Write access confined to calendars the app made | Choose Google Calendar API scopes |
| Not needed for booking | calendar: “See, edit, share, and permanently delete all the calendars you can access” |
Sharing settings and permanent deletion of whole calendars | Choose Google Calendar API scopes |
Least privilege for an AI receptionist booking one person’s own calendar is calendar.freebusy plus calendar.events.owned. The dedicated-calendar pattern (calendar.app.created) is narrower still for writes, at the cost of bookings sitting on a separate calendar that staff must have switched on. Google’s verification policy makes the same point from the other side: you must give “an explanation why narrower scopes would not work”, and Google may direct you “to request a narrower scope to proceed with verification”. None of the Calendar scopes appears on Google’s restricted-scope list, which as at 28 October 2026 covers Gmail, Drive, Fit, Chat, Google Health, Photos ambient and data-portability scopes, so a calendar-only app does not face the annual security assessment that restricted scopes require.
What the AI must check before it books: freeBusy, then events.insert
A booking is two Google API calls a few seconds apart, and double-bookings, wrong times and silent failures can start in that gap. Google’s events.insert reference describes no availability check, so the free/busy check is the AI’s job.
- Query free/busy for the whole window, buffers included.
POST https://www.googleapis.com/calendar/v3/freeBusytakestimeMinandtimeMax“formatted as per RFC3339” and a list of calendar IDs. Google capscalendarExpansionMaxat 50 calendars andgroupExpansionMaxat 100 group members per query. The response contains only busy periods, so working hours and buffers are rules your tool applies: widen the window by your buffer on each side. - Set the response time zone. For freeBusy, Google says the
timeZonefield is “Optional. The default is UTC.” An AI that reads busy times without setting it is comparing UTC times with a caller’s local “2pm”. - Read the per-calendar errors. Each calendar in the response can carry an
errors[]list with reasons such asnotFoundortooManyCalendarsRequested. An empty result from a calendar that errored is easy to misread as a free day, so treat any error as “unknown”, not “free”. - Remember the boundaries. Google defines each busy period’s start as inclusive and its end as exclusive, so a 2:00 to 2:30 meeting leaves 2:30 free. Back-to-back is allowed unless your buffer says otherwise.
- Insert the event with an explicit offset and zone.
POST https://www.googleapis.com/calendar/v3/calendars/calendarId/events. Forstart.dateTime, Google says “A time zone offset is required unless a time zone is explicitly specified in timeZone”, and thetimeZonefield takes an IANA name such as Australia/Sydney. Send both. - Keep the booking blocking.
transparencydefaults toopaque, which Google says “does block time on the calendar”. An event set totransparent“does not block time”, so it will not stop the next booking. - Make retries safe. You may supply your own event
id: lowercase letters a to v and digits, 5 to 1,024 characters, unique per calendar. If a retried insert reuses the ID, Google’s error guide documents a409“The requested identifier already exists”. Google also warns that “we cannot guarantee that ID collisions will be detected at event creation time”, so the client ID reduces duplicates rather than ruling them out; re-run freeBusy after a timeout before any new ID. - Decide who gets the invitation.
sendUpdatesacceptsall,externalOnlyornone. Google warns thatnone“can have significant adverse effects, including events not syncing to external calendars or events being lost altogether for some users”. For a caller who should receive an invite, useall.
Here are the two request bodies for 2pm on Thursday 5 November 2026 in Sydney. Sydney is on daylight time then: the NSW Department of Communities and Justice says daylight saving “begins at 2am on the first Sunday in October”, so the offset is +11:00 and 2pm Sydney is 11am in Perth.
freeBusy request body
{
"timeMin": "2026-11-05T13:45:00+11:00",
"timeMax": "2026-11-05T14:45:00+11:00",
"timeZone": "Australia/Sydney",
"items": [ { "id": "YOUR_CALENDAR_ID" } ]
}
events.insert request body (query: sendUpdates=all)
{
"id": "3f2a9c0e7b1d4e5f8a6b2c9d0e1f7a3b",
"summary": "Consultation (booked by AI receptionist)",
"start": { "dateTime": "2026-11-05T14:00:00+11:00", "timeZone": "Australia/Sydney" },
"end": { "dateTime": "2026-11-05T14:30:00+11:00", "timeZone": "Australia/Sydney" },
"transparency": "opaque"
}
The freeBusy window adds a 15-minute buffer either side of the 30-minute slot. Replace YOUR_CALENDAR_ID with the ID from calendarList, and add the caller as an attendee if the tool collects an email address. One limit applies to route 2: Google’s insert reference says “Service accounts need to use domain-wide delegation of authority to populate the attendee list.”
Building your own connector: Testing mode, the 100-user cap and verification
If you build your own AI-to-Google Calendar connector instead of using a vendor’s, three Google rules decide whether it survives its first fortnight. They apply to route 1 apps whose consent screen is set to External.
- Testing mode expires access after 7 days. Google’s App Audience page says a project with a publishing status of Testing is “limited to up to 100 test users”, and that a test user’s authorisation “will expire seven days from the time of consent”, including any refresh token. The only exception is an app requesting nothing beyond sign-in scopes (name, email address, profile), which rules out any calendar app.
- Unverified apps stop at 100 users. Google’s unverified-apps page caps apps that show the unverified-app screen at “100 new users in total”. The App Audience page adds that the cap “applies over the entire lifetime of the project, and it cannot be reset or changed”, and does not apply once you request only approved scopes. Google notes the quotas “might be adjusted for specific apps”.
- Verification takes time. Verification needs a privacy policy, a homepage on a domain you have verified in Search Console and, for sensitive or restricted scopes, a demonstration video showing the OAuth grant and a written justification for each scope (Google’s own example justification in that section is a Calendar scope). Google’s own page warns that “verification might require several months for the app to complete”, depending on the data requested.
Google lists five cases where verification is not required: personal-use apps with fewer than 100 users, development or testing projects, apps that touch only their own service-account data, internal apps used only inside your Workspace or Cloud Identity organisation (organisation-owned project, consent screen set to internal), and apps an administrator has trusted or installed from the Google Workspace Marketplace. For a business booking into its own staff calendars, the internal route is the one to use: Google says such an app “will not be subject to the unverified app screen or the 100-user cap”.
Refresh tokens can also stop working for reasons that have nothing to do with your code. Google lists six that can hit a calendar app (a seventh, Google Cloud session control, applies only to apps requesting the Cloud Platform scope): the user revoked access; the token has not been used for six months; the user changed password and the token includes Gmail scopes; the account exceeded its maximum number of live refresh tokens (100 per Google Account per OAuth client ID, with the oldest invalidated “without warning”); time-based access expired; or an administrator set a requested service to Restricted, which returns admin_policy_enforced. HighLevel’s support article lists a password change as a cause of a broken Google Calendar sync; Google’s page ties password changes to tokens that include Gmail scopes.
The honest cost of a do-it-yourself build: a Google Cloud project, a consent screen, a privacy policy, the token and error handling below, a verification wait Google says can run to months, and someone to re-connect calendars when tokens lapse. That suits a developer with one Workspace domain. For a small business that just wants calls booked, it is more plumbing than most need, which is the case for routes 1 or 3 through an existing vendor. The phone side of a self-built agent is covered in how to build an AI receptionist, and when not to.
Google Workspace admin settings that silently block the connection
On Google Workspace, an administrator’s app-access settings can block an AI tool even when the scopes and code are right. Three settings under Security, Access and data control, API controls matter.
- Unconfigured third-party apps. The default is “Allow users to access any third-party apps”. An administrator can instead allow only apps requesting basic sign-in information, or choose “Don’t allow users to access any third-party apps” until each app is configured; either way, a staff member connecting an AI calendar tool is refused.
- Calendar set to Restricted. Google’s example is exact: “if you set Calendar access as Restricted, only internal and third-party apps configured with a Trusted or Specific Google data access setting can access Calendar data. Internal and third-party apps with a Limited access setting can’t access Calendar data.” Changing a service to Restricted means previously installed apps that are not trusted “stop working”.
- Domain-wide delegation entries. Only a super administrator can add a service account’s client ID and its scopes, and Google advises keeping them “appropriately narrow”. If multi-party approval is on, a second super administrator must approve.
Google says app-access and delegation changes “can take up to 24 hours but typically happen more quickly”, so a connection that fails minutes after an admin change may not have propagated yet. Google’s server-to-server page adds that service accounts “aren’t subject to domain policies set by Google Workspace administrators”, one more reason to give a delegated service account the narrowest scope that books.
Want the bookings without the plumbing? Zian AI answers inbound calls 24/7 as an AI receptionist and books appointments from calls and messages. Apply For Partnership
Common Google Calendar connection failures and Google’s own error codes
Seven Google responses explain the common ways an AI calendar connection breaks. The meaning column quotes Google’s Calendar error guide and OAuth documentation; the fix column combines Google’s suggested action with what to check in a booking setup.
| Symptom in the AI tool | Google’s response | What Google says it means | Fix |
|---|---|---|---|
| Worked for a week, then every booking fails | 401 authError, or invalid_grant on refresh |
“The access token you’re using is either expired or invalid”; the refresh token stopped working | Refresh the access token; if that fails, send the owner through consent again; move the project out of Testing |
| Not-found error on a calendar you can see | 404 notFound |
The resource never existed, or “a calendar that the user can not access” | Check the calendar ID from calendarList and that the connected account is the one with access |
| Busy day shows as completely free | freeBusy errors[] with notFound |
Free/busy computation failed for that calendar | Treat as unknown, not free; fix the ID or sharing |
| Booking request rejected immediately | 400 such as timeRangeEmpty |
A required field is missing or invalid; “do not retry” | Fix the request (end after start, offset present) |
| Bookings fail at busy times | 403 userRateLimitExceeded; 403 or 429 rateLimitExceeded |
A Developer Console quota was reached (userRateLimitExceeded), or the maximum request rate per calendar or per authenticated user (rateLimitExceeded) | Exponential backoff; stop re-polling freeBusy in loops |
| Bookings fail all day on one calendar | 403 quotaExceeded, “Calendar usage limits exceeded” |
One of the Google Calendar limits “in place to protect Google users and infrastructure” | Slow down writes to that calendar; check Google’s usage limits |
| Retry created a second event, or failed | 409 duplicate |
“An instance with the given ID already exists” | Treat as already booked; use update, not a new insert |
On quotas, Google’s usage-limits page changed on 1 May 2026. Projects created on or after that date get 10,000 requests per minute per project, 600 requests per minute per user per project, and a daily billing threshold of 1,000,000 requests per project; projects that used the API between November 2025 and April 2026 “will continue with their previously set usage quotas”. At two requests per booking (one freeBusy, one insert), one connected user would need 300 bookings a minute to reach the 600-per-minute figure; an agent that re-polls availability in a loop multiplies its request count. On route 2 the arithmetic changes: Google says a domain-wide delegated service account is by default charged against the per-user quota itself, “and not the user you’re impersonating”, so every staff calendar shares one 600-per-minute allowance unless the code sets the quotaUser parameter. Two other quiet failures come from vendors’ documentation rather than Google’s: Vapi’s Google Calendar tools take a timeZone that “defaults to UTC” and a calendarId that “defaults to the primary calendar”, and HighLevel shows a “writer access” error when the connected account lacks “Make changes to events” on the chosen calendar.
The booking connection test: eight checks before launch
The eight-check booking connection test proves the Google connection itself, before you test the conversation. Run it with a test account and calendar; any result other than the expected one points to a setting, not the AI’s prompt.
| # | Check | How to run it | Expected result | Google source |
|---|---|---|---|---|
| 1 | Consent matches configuration | Connect with a fresh test account | Consent screen lists only the scopes you chose; no unverified-app screen on a verified or internal app | Unverified apps |
| 2 | Partial grant is caught | On the granular consent screen, untick the calendar permission | Tool reports the missing permission at connection time, not at the first booking | Granular permissions |
| 3 | Right calendar, right role | List calendars for the connected account | Target calendar present with accessRole writer, writerWithoutPrivateAccess or owner |
CalendarList |
| 4 | Busy time is seen | Create a busy test event on a second calendar, then ask for that slot | Slot refused; freeBusy returns the event in busy[] with no errors[] |
Freebusy: query |
| 5 | Time zone survives | Book 2pm Thursday 5 November 2026 on a Sydney calendar | Event reads 2:00 pm in Sydney and 11:00 am for a viewer set to Perth | Events: insert |
| 6 | A retry does not double-book | Force a timeout and let the tool retry the same booking | One event on the calendar; any repeat insert with the same ID returns 409 |
Handle API errors |
| 7 | Revoked access fails safely | Remove the tool’s access in the Google Account, then try to book | Booking fails visibly; the AI takes a message or hands to a person and never confirms a booking it did not make | Using OAuth 2.0 |
| 8 | No 7-day or admin time bomb | Check the project’s publishing status; on Workspace, check the app’s access setting | Status is In production or Internal; app is Trusted or Specific Google data if Calendar is Restricted | Manage App Audience |
Check 7 is the one that matters most to a caller: a disconnected calendar should produce a message or a call-back, not a confident “you’re booked”. Once all eight pass, test the conversation itself, including reschedules and cancellations, using the behaviour checks in the guide to scheduling appointments with AI.
How AI tools document their Google Calendar connection
Methodology and disclosure: each row quotes that tool’s own help or developer documentation, read 28 October 2026, and records which of the three routes it uses; rows are not scored. Zian is listed first as the platform pick and described from its published configuration and zian.ai pages only. LeadsNow.ai is Zian’s sister company and runs on Zian. zian.ai publishes this table and Zian appears in it.
| Tool | Route | What its own page says about the Google Calendar connection | What to set or check |
|---|---|---|---|
| Zian AI (platform pick) | Calendars, CRM and API connections | zian.ai: “Connect Zian AI to your CRM, comms, calendars, knowledge bases, and more. Use our API for custom workflows.” Integrations: HubSpot, Salesforce, HighLevel, Zapier | Which calendar route your account uses; run the eight checks |
| LeadsNow.ai (done-for-you) | Managed service running on Zian | Pay-per-result AI appointment setting; leads answered in under 60 seconds, 24/7 | For operators who want booked appointments without running the connection |
| Vapi | 1. OAuth user consent | Dashboard, Integrations, Google Calendar, Connect; two tools, Create Event and Check Availability; timeZone “defaults to UTC”; calendarId “defaults to the primary calendar” (Vapi docs) |
Set timeZone and calendarId on both tools |
| Calendly | 3. Booking layer | Settings, Scheduling, Calendars, Connect; choose “Calendars to check for conflicts” and one calendar to add events to: “Calendly won’t add events to any other calendar” (Calendly Help) | Put every calendar that makes you busy in the conflict list |
| HighLevel | 3. Booking layer (CRM calendar) | “Two-way sync”; “You must allow full calendar access”; integrations “are tied to individual user profiles”; one Linked Calendar for bookings and others as Conflict Calendars (HighLevel Support) | Each staff member connects their own Google account with write access |
| Zapier | 1. OAuth, used inside automations | Searches include “Find Busy Periods in Calendar” and actions include “Create Detailed Event”; its help page says dates sent this way “must be in MM/DD/YYYY format” (Zapier Help) | Reformat Australian DD/MM dates before they reach the event step |
Read the HighLevel row beside the scope chooser: full calendar access is broader than a booking needs, but the sync depends on it, and it is granted to the CRM once per staff member, not to the AI. That is the route 3 trade: the scheduler or CRM holds the Google token and the AI holds none.
Ready to have calls and messages booked for you? Zian AI books from voice, SMS, WhatsApp, Instagram and Messenger conversations, in 30+ languages. Apply For Partnership
Frequently asked questions
How do I connect AI to Google Calendar?
Choose one of three routes: sign in to the AI tool with Google and approve its calendar permissions, have a Workspace super administrator grant a service account domain-wide delegation, or connect Google to a scheduler such as Calendly that the AI books through. Then confirm the tool checks free/busy before it creates each event, with an explicit time zone.
What Google Calendar permission does an AI booking agent need?
Usually two narrow scopes: calendar.freebusy to see busy times and calendar.events.owned to create, change and delete events on calendars the account owns. Use calendar.events only when the booking calendar is shared rather than owned. Google’s Calendar API scopes page lists each scope and advises choosing “the most narrowly focused scope possible”.
Why does my AI calendar connection stop working after 7 days?
Your Google Cloud project is probably still in Testing. Google’s App Audience help page says authorisations by a test user “will expire seven days from the time of consent”, including refresh tokens. Publish the app to production, or set it to internal if only your Workspace organisation uses it.
Can an AI book into Google Calendar without each person logging in?
Yes, inside one Google Workspace domain. A super administrator can grant a service account domain-wide delegation with named scopes, and the service account then makes calls as the user it names. Google says this grants access “without requiring their consent”, changes can take up to 24 hours, and a service account needs delegation to add attendees.
How many people can use my own Google Calendar AI app before verification?
An unverified app that shows Google’s unverified-app screen is capped at 100 new users over the project’s lifetime, and the cap cannot be reset. Testing mode allows up to 100 test users. Internal Workspace apps are exempt from the screen and the cap.
Why can the AI see my calendar but not book into it?
Check three things: the connected account’s access role on that calendar must be writer, writerWithoutPrivateAccess or owner, the tool must hold a write scope such as calendar.events.owned or calendar.events, and on Workspace an administrator may have set Calendar to Restricted, which blocks apps that are not Trusted or set to Specific Google data.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| 20 Calendar API scopes and their meanings | Google for Developers | developers.google.com/workspace/calendar/api/auth | 28 October 2026 |
| freeBusy: 50 calendars, 100 group members, UTC default | Google for Developers | Freebusy: query | 28 October 2026 |
| Event ID 5 to 1,024 characters (a to v, 0 to 9) | Google for Developers | Events: insert | 28 October 2026 |
| Error codes 400, 401, 403, 404, 409, 429 | Google for Developers | Handle API errors | 28 October 2026 |
| 10,000 and 600 requests per minute; 1,000,000 per day; 1 May 2026 change; delegated service accounts charged per-user quota unless quotaUser is set | Google for Developers | Usage limits | 28 October 2026 |
| Testing tokens expire in 7 days; six months unused; 100 refresh tokens per account per client | Google for Developers | Using OAuth 2.0 to Access Google APIs | 28 October 2026 |
| Up to 100 test users; test authorisations expire in seven days; lifetime user cap | Google Cloud Help | Manage App Audience | 28 October 2026 |
| 100 new users for unverified apps; verification “several months” | Google Cloud Help | Unverified apps | 28 October 2026 |
| Narrow-scope justification, demonstration video, homepage and privacy policy; annual security assessment for restricted scopes only | Google Cloud Help | Verification requirements | 28 October 2026 |
| Personal use fewer than 100 users; five verification exemptions | Google Cloud Help | When is verification not needed | 28 October 2026 |
| Restricted-scope list (no Calendar scopes) | Google Cloud Help | Restricted Scopes | 28 October 2026 |
| App-access changes up to 24 hours; Calendar Restricted behaviour | Google Workspace Admin Help | Control which apps access Google Workspace data | 28 October 2026 |
| Delegation changes up to 24 hours; super administrator required | Google Workspace Admin Help | Control API access with domain-wide delegation | 28 October 2026 |
| Appointment schedules: 4-hour default minimum lead time | Google Calendar Help | Create an appointment schedule | 28 October 2026 |
| Daylight saving from 2am on the first Sunday in October (so +11:00 on 5 November 2026; 2pm Sydney = 11am Perth, our arithmetic) | NSW Department of Communities and Justice | Daylight saving | 28 October 2026 |
| Vapi time zone defaults to UTC; calendar defaults to primary | Vapi | docs.vapi.ai/tools/google-calendar | 28 October 2026 |
| Zapier: dates “must be in MM/DD/YYYY format” | Zapier | Zapier Help | 28 October 2026 |
| 64,521+ qualified sales appointments set | Zian AI (first-party) | zian.ai | 28 October 2026 |
| Leads answered in under 60 seconds, 24/7 | LeadsNow.ai (first-party) | leadsnow.ai | 28 October 2026 |