Major

Google Calendar Automation: Apps, Agents and API Guide

Build Google Calendar automation on Major with native connectivity, verified API endpoints, stateful scheduling apps, agent judgment, and human approval before invitations change.

Ritvij GautamUpdated
team collaborating on shared documents (Google Calendar AI agents and automations)

Google Calendar automation connects availability, events, and scheduling requests to the work happening in your other systems. This guide covers Google's built-in AI, the Calendar API, and how to build governed scheduling apps, agents, and workflows on Major.

Major's deterministic app layer holds booking state, review queues, and execution history. Agents interpret ambiguous requests, while workflows coordinate approved actions across Calendar and your team's tools.

What Google Calendar does for scheduling teams

Google Calendar holds events, shared calendars, invitations, and availability. Operations leads use that information to coordinate interview panels, customer meetings, project reviews, and executive schedules. The hard part is usually reconciling a request with commitments and context that live elsewhere.

Google's Calendar product page describes shared calendars, working hours and location, meeting rooms, document attachments, appointment booking pages, and Google Meet integration. These are useful foundations for teams whose scheduling needs already fit Calendar's interface.

Recruiting coordinators need panel coverage and candidate-friendly times. Project leads need to know whether an owner is absent before escalating stalled work. Customer-facing teams need the right people and preparation material attached to each meeting, without exposing unrelated private events.

Major fits when those jobs cross systems. An agent can build an app that stores requests and approved policies, then run its repeatable checks as code. It reserves judgment for questions such as whether a proposed substitution fits the meeting's purpose. Calendar remains the scheduling record people already use.

Google Calendar AI and its built-in scheduling help

Google's native AI deserves the first look for tasks contained within Workspace. The official Calendar page names Help me schedule in Gmail, where Gemini uses email context and Calendar availability to suggest meeting times. It also describes Gemini detecting event details in email and offering an Add to Calendar button.

Those features shorten the path from an email conversation to a calendar entry. Availability depends on the relevant Workspace plan and feature eligibility, so verify access for the actual users before designing around them.

Appointment booking pages, focus time, and Time Insights are also native Calendar capabilities. They handle booking, protected work periods, and schedule analysis respectively. They should not all be relabeled as generative AI features simply because they appear alongside Gemini.

An agent on Major adds value when scheduling depends on an ATS stage, an Asana dependency, a customer escalation, or an approval policy. It can interpret that context and recommend a plan. The app preserves the recommendation and evidence, and the workflow waits for approval before changing invitations. Native Google features and Major address different parts of the same process.

How Google Calendar connects to Major

Major has a native Google Calendar connector, identified as googlecalendar in its connector catalog. IT sets up the connector once, with centrally stored, scoped credentials in the connector vault. Credentials belong neither in application code nor in agent prompts.

Google's authentication overview explains OAuth 2.0 user authorization and access tokens, with refresh tokens for access beyond a single token's lifetime. API keys are for public data, not a substitute for authorization to private calendars. Service accounts with domain-wide delegation are an administrator-controlled option for user data, not the default assumption for every connection.

Choose the calendar population and permitted operations before granting access. A preparation assistant may need event reads; a scheduling coordinator may also need narrowly controlled event writes. Calendar access permissions still constrain what the authorized identity can see or change.

Major orchestrates Google Calendar; it never replaces it. Major's SSO, RBAC, and audit logs cover the apps, agents, and workflows around that connection. A shared connector does not mean every agent should receive every operation the underlying credential permits.

Google Calendar API guide for practical automation

The API reference uses the base URL https://www.googleapis.com/calendar/v3. The paths below retain Google's calendarId and eventId placeholders. Substitute real identifiers when making requests.

Authorization, paging, and operating limits

Google's scope guide lists exact scope URIs. Use https://www.googleapis.com/auth/calendar.events.readonly for event reads, https://www.googleapis.com/auth/calendar.events for event editing, and https://www.googleapis.com/auth/calendar.calendarlist.readonly to discover subscribed calendars. The availability scope https://www.googleapis.com/auth/calendar.events.freebusy supports a narrower availability-only use case. Check each method's accepted scopes rather than assuming one permission covers every operation.

For event listing, pass pageToken from the returned nextPageToken until pagination ends. maxResults defaults to 250 and cannot exceed 2,500. Persist nextSyncToken from the final page and use syncToken for incremental synchronization. The sync guide requires a new full synchronization after an invalid token produces HTTP 410.

Google's usage limits document 10,000 requests per minute per project and 600 per minute per user per project for the newer quota model. Previously active projects may retain earlier quotas. The page describes 1,000,000 daily requests as a billing threshold, not a universal hard stop. Confirm the project's actual console limits. Calendar-specific remaining-quota response headers are not documented publicly on that page; monitor HTTP 403 or 429 and the response's error reason instead.

Google recommends a separate test-only Cloud project with artificially reduced quotas. The Python quickstart provides a testing-oriented OAuth setup. Use isolated calendars and test attendees, not live interview panels.

Notifications are change signals, not event payloads

The push guide supports watches on events, calendar lists, ACLs, and settings. Calendar notifications have no message body containing the changed event, so fetch changes afterward.

Validate X-Goog-Channel-ID and X-Goog-Resource-ID against stored channel records. Configure a secret channel token and compare the echoed X-Goog-Channel-Token. This is channel-token verification, not a documented HMAC body signature. Never put OAuth credentials in that token.

The guide documents exponential-backoff retries for 500, 502, 503, and 504 responses in its client-library scenario, but also warns that notifications can be dropped. Renew channels before their returned expiration and reconcile on a schedule. Do not design around guaranteed delivery or a guessed retry duration.

Discover calendars: GET /calendar/v3/users/me/calendarList

Returns the calendars on the authorized user's list, including access roles.

  • App: Store an administrator-approved calendar directory and selection screen.
  • Agent: Read that directory to interpret which team calendar a request means.
  • Workflow: Refresh the directory before onboarding a new scheduling group.

Read a collection: GET /calendar/v3/calendars/calendarId/events

Returns events, with time filters, recurring-instance expansion, pagination, and incremental synchronization options.

  • App: Maintain an event cache keyed by calendar and event identifier.
  • Agent: Review permitted meeting context to explain a proposed scheduling conflict.
  • Workflow: Fetch changed events after a notification and update the cache.

Inspect one event: GET /calendar/v3/calendars/calendarId/events/eventId

Retrieves an event by its Google Calendar event ID.

  • App: Show the current event beside a proposed change in the review queue.
  • Agent: Read the latest agenda before recommending a shorter meeting.
  • Workflow: Re-read the event before applying an approved modification.

Check availability: POST /calendar/v3/freeBusy

Returns busy intervals for a set of calendars, with a maximum calendar expansion of 50.

  • App: Calculate overlapping open windows without storing unrelated event descriptions.
  • Agent: Rank eligible windows against a requester's expressed preferences.
  • Workflow: Recheck panel availability immediately before attempting a booking.

Create a booking: POST /calendar/v3/calendars/calendarId/events

Creates an event with required start and end information and optional attendees.

  • App: Record the approved booking and returned event identifier.
  • Agent: Draft an agenda and attendee rationale for the reviewer.
  • Workflow: Create the event only after approval and availability revalidation.

Review sendUpdates explicitly. Google warns that choosing none can cause synchronization problems for some attendees; suppressing notifications is not an approval mechanism.

Modify an event: PATCH /calendar/v3/calendars/calendarId/events/eventId

Applies partial updates, but supplied arrays replace existing arrays and each patch consumes three quota units.

  • App: Render the exact time, description, and attendee differences for approval.
  • Agent: Explain why a reschedule is preferable to dropping an attendee.
  • Workflow: Apply only the approved changes to the intended event copy.

Watch changes: POST /calendar/v3/calendars/calendarId/events/watch

Creates a notification channel for changes to a calendar's events collection.

  • App: Store the channel ID, resource ID, token reference, and expiration.
  • Agent: Interpret the fetched changes to identify which requests need attention.
  • Workflow: Register replacement channels before existing channels expire.

Stop a channel: POST /calendar/v3/channels/stop

Stops watching a resource using the channel ID and resource ID.

  • App: Display subscription status and retain the retirement record.
  • Agent: Explain which dependent scheduling processes would lose notifications.
  • Workflow: Retire an old channel after its replacement becomes active.

Google Calendar automation use cases on Major

These patterns combine Calendar with business context, rather than treating every free interval as an equally good booking. Start with read-only recommendations, measure review outcomes, and add tightly scoped writes afterward.

Interview coordination with Greenhouse, Gmail, and Calendar

  • App: Keep candidate scheduling requests, panel requirements, proposed slots, and approval outcomes in managed tables.
  • Agent: Interpret candidate preferences and flag panel substitutions that need recruiter judgment.
  • Workflow: Start from an approved interview request, query availability, seek recruiter approval, create the booking, and record the handoff.
  • Calendar methods: Freebusy query, event insert, and event get from the linked API guide above.

Keep hiring decisions separate from scheduling. A declined invitation must never become an inferred candidate rejection.

Launch-readiness review with Asana, Slack, and Calendar

  • App: Store task-to-owner mappings, known absences, and review history.
  • Agent: Combine overdue work and permitted absence information to recommend whether ownership needs review.
  • Workflow: Run a scheduled readiness check and route recommendations to the lead in Slack before changing assignments.
  • Calendar methods: Event list and freebusy query.

An open calendar is not proof of spare capacity. The agent should explain that limitation alongside its recommendation.

Meeting preparation with Gmail, Google Drive, and Calendar

  • App: Track preparation status, approved source links, and event versions.
  • Agent: Read authorized email and documents to draft a relevant agenda and unresolved-question list.
  • Workflow: Find upcoming meetings, queue internal briefs, and request approval before adding material to a shared invitation.
  • Calendar methods: Event list, event get, and event patch.

Never copy a private document's contents into an invitation simply because the organizer can read it. The brief and invitation may have different audiences.

How to build the architecture on Major

Google Calendar and Gmail flow through a Major workflow, scheduling agent, approval decision, and stateful app

Figure 1. Calendar signals enter a governed scheduling process on Major.

Use the app as both the operator's control surface and the execution layer the agent runs through. The database keeps requests, source mappings, event versions, proposals, approval records, notification channels, and operation results. None of that durable state should depend on a conversation remaining open.

  1. Connect: IT authorizes Google Calendar and the necessary context tools, with reads and writes separated by policy.
  2. Synchronize: A workflow receives a change signal or runs on a schedule, fetches current records, and deduplicates work.
  3. Calculate: App code handles time-zone conversion, duration checks, overlap calculations, and approved working-hour rules.
  4. Judge: The agent interprets an ambiguous request, ranks valid options, and explains tradeoffs.
  5. Review: The app presents an exact proposal to the named approver.
  6. Execute: The workflow revalidates current state, applies the authorized action, and records the result.

Agents build repeatable checks into deterministic apps instead of reasoning through identical calculations on every request. Judgment remains with the agent; policy enforcement and records remain inspectable software. Reason once. Run forever.

A worked scheduling example with numbers

For example, consider an illustrative recruiting team coordinating 100 interview bookings each month. Suppose a coordinator currently spends 12 minutes per booking checking availability, reconciling email preferences, proposing times, and recording the outcome.

That is 100 × 12 = 1,200 minutes, or 20 hours of coordination. These are planning assumptions, not a customer result or a measured Major performance claim.

With the proposed system, 80 straightforward requests might require three minutes of review each. The remaining 20 exceptions might take ten minutes each because of panel substitutions, ambiguous time zones, or candidate changes.

Review time would be 80 × 3 + 20 × 10 = 440 minutes, or seven hours and 20 minutes. Add 40 minutes for queue maintenance and reconciliation, giving eight hours total and an illustrative difference of 12 hours per month.

The agent reads the request and recommends eligible slots. The app calculates overlap and stores evidence. A recruiter approves the booking, and the workflow rechecks availability before creating it. Track actual review time, failed bookings, and exception frequency before claiming that the assumed improvement has occurred.

Governance and failure handling before calendar writes

Calendar and Gmail scheduling proposals split into internal drafts or a Major review queue before approved booking

Figure 2. Internal drafts proceed without an external write; invitations require owner approval.

Allow internal drafts and read-only calculations to proceed within granted permissions. Require approval for external invitations, attendee changes, reschedules, cancellations, and anything that exposes information to a new audience. The agent must never silently reinterpret a reviewer's approval as permission for a materially different event.

Google's error guide distinguishes invalid requests, expired credentials, rate limits, and conflicting state. Back off with jitter for transient failures and rate-limit responses. Do not repeatedly retry an unchanged bad request. If refreshing authorization fails, pause affected work and request reconnection rather than expanding access.

Use a stable request identity and an operation ledger to prevent duplicate bookings on retries. If a create request times out, reconcile its outcome before issuing another create. Treat duplicate notifications and overlapping watch channels as expected inputs.

Persist calendar event IDs separately from business request IDs. Re-read the event and availability after approval, and return changed proposals for renewed approval. An availability check is not a reservation or a transaction across multiple calendars.

Record the source data version, agent recommendation, approver, exact write, and response. Google's push documentation warns that notifications can be missed, so scheduled reconciliation is part of correctness, not an optional monitoring feature.

Google Calendar AI Apps, Agents and Workflow Automations

Every published Major use case that works with Google Calendar, newest first. Each one names the Google Calendar API objects involved and shows the app, agent and workflow split.

Frequently asked questions

Can Google Calendar be automated?

Yes. Google Calendar's API supports reading events, checking availability, creating bookings, editing events, and watching changes. On Major, an app holds scheduling state, an agent interprets requests, and a workflow coordinates approved operations.

Does Google Calendar have AI scheduling?

Google describes Gemini's Help me schedule in Gmail and an Add to Calendar action for event details detected in email. These help with Workspace scheduling; an agent on Major adds cross-system context, durable review state, and approval routing.

Does Major have a native Google Calendar connector?

Yes. Major's catalog lists a native Google Calendar connector identified as googlecalendar. IT sets it up once with centrally stored, scoped credentials, then controls which apps, agents, and workflows can use it.

Can I automate scheduling without reading private event descriptions?

Yes, when availability is sufficient. Google's freebusy query returns busy intervals, and its documented availability scopes support a narrower access pattern than full event reading. Review the chosen method, granted scope, and calendar permissions together.

Do Google Calendar webhooks include the changed event?

No. Calendar push notifications signal a change without an event body. Fetch current changes afterward, verify the configured channel identifiers and token, renew expiring channels, and reconcile periodically because notifications can be missed.

Can an agent reschedule meetings automatically?

It can propose a reschedule, but a governed design requires approval before changing someone else's commitments. Recheck the event and availability after approval, and ask again if the proposed time or attendees materially change.

Sources

These official Google pages support the capabilities and implementation details above. The method pages document each HTTP path and its accepted parameters. The guides explain the authorization and synchronization behavior that determines whether a scheduling process remains correct after retries, missed notifications, or expired access.

Start building on Major

Build a scheduling app with a durable request queue, an agent that interprets meeting constraints, and a workflow that requires approval before invitations change.

About the author

Ritvij Gautam is Head of Growth at Major.

Last reviewed November 20, 2026 by Ritvij Gautam.

Frequently asked questions

Can Google Calendar be automated?
Yes. Google Calendar's API supports reading events, checking availability, creating bookings, editing events, and watching changes. On Major, an app holds scheduling state, an agent interprets requests, and a workflow coordinates approved operations.
Does Google Calendar have AI scheduling?
Google describes Gemini's Help me schedule in Gmail and an Add to Calendar action for event details detected in email. These help with Workspace scheduling; an agent on Major adds cross-system context, durable review state, and approval routing.
Does Major have a native Google Calendar connector?
Yes. Major's catalog lists a native Google Calendar connector identified as googlecalendar. IT sets it up once with centrally stored, scoped credentials, then controls which apps, agents, and workflows can use it.
Can I automate scheduling without reading private event descriptions?
Yes, when availability is sufficient. Google's freebusy query returns busy intervals, and its documented availability scopes support a narrower access pattern than full event reading. Review the chosen method, granted scope, and calendar permissions together.
Do Google Calendar webhooks include the changed event?
No. Calendar push notifications signal a change without an event body. Fetch current changes afterward, verify the configured channel identifiers and token, renew expiring channels, and reconcile periodically because notifications can be missed.
Can an agent reschedule meetings automatically?
It can propose a reschedule, but a governed design requires approval before changing someone else's commitments. Recheck the event and availability after approval, and ask again if the proposed time or attendees materially change.