Google Calendar: scope and setup

Read access is not two-way sync

Procora’s existing Google connection reads busy intervals and the calendar list. It does not write Google events. Google documents Freebusy as a request for busy intervals; an interval is not a booking confirmation.

Saved Procora bookings, calendar invitations and a subscription feed are separate parts. A calendar client may refresh a feed with a delay. Do not treat a feed as evidence of active two-way synchronisation or conflict-safe booking.

Source: Google Calendar API: Freebusy query

Check prerequisites

The owner’s account needs relevant calendar access. Check booking in the actual plan and configure service duration, buffer, working hours and time zone. Review which information may enter an appointment. Do not share calendar passwords with Procora.

Connect and select the correct calendar

Open the calendar connection in workspace settings. Choose the Google account that owns or may read the calendar, review the displayed permissions and select the relevant calendar. The calendar list must be readable and the connection must be tested with sample data.

If connection is unavailable or Google rejects access, resolve the setup with support. This guide was checked against source on 15 October 2026; it does not establish a working connection for your account.

Test conflicts and confirmation

Create a fictional busy interval in the test calendar and check that it is not offered. Test a free slot and inspect the saved booking reference. Repeat a request to examine duplicates. Wording that says booked without a saved record does not pass.

Handle failures and disconnects

When a connected calendar fails, availability cannot be assumed. Use a human appointment route and check revoked access, selected calendar and time zone before retrying. Disconnect in the workspace and also review app access in Google. Separately establish what happens to saved bookings and imported invitations.

Use the worksheet

Version 15 October 2026. Fill in your own facts; illustrative values are not results or an agreed service.

CALENDAR TEST
Owner / calendar / date / time zone:
Booking access and services checked:
Busy test slot excluded from suggestions:
Revoked access produces no false availability:
Proposed slot / saved booking reference / confirmation checked:
Invitation or feed checked separately:
Daylight-saving and duplicate test:
Disconnect and human recovery route:
Observed result / owner / retest date:

Sources and scope of review

First-party documentation reviewed 15 October 2026. Vendor statements are not independent product tests. Recheck your actual package and agreement.

• Google Calendar API: Freebusy query