Google Calendar
Source-reviewed capability blueprint for Google Calendar: Use Google Calendar busy time to prevent conflicts and write Hoop bookings to one linked calendar. Confirm Hoop availability before setup.
This source-reviewed capability blueprint describes expected behavior and vendor requirements. It does not confirm that Hoop has enabled this connection for your account.
Overview
This profile describes the expected connection path if it is enabled in Hoop. Google Calendar supports two distinct calendar roles in Hoop. Conflict calendars contribute busy time only. One linked calendar can receive Hoop bookings, changes, and cancellations. Optional full two-way mode can also turn Google events into Hoop appointments and workflow activity.
Expected data flow
Google busy time to Hoop
Expected when enabled: A busy event on a selected linked or conflict calendar can block the matching time in Hoop availability.
Hoop booking to Google
Expected when enabled: A new booking, reschedule, or cancellation can update the selected primary linked Google Calendar.
Google event to Hoop appointment
Expected when enabled: When optional full two-way mode is enabled, an eligible Google event can become a Hoop appointment, create guest contacts, and start configured workflows.
Expected capabilities
- Expected when enabled: Block availability from selected busy Google events
- Expected when enabled: Write new Hoop bookings, reschedules, and cancellations to one primary calendar
- Expected when enabled: Use additional calendars for conflict checking
- Expected when enabled: Optionally create Hoop appointments and workflow activity from Google events
Expected setup
- 01
Expected setup step when enabled: A Google account with Calendar access
- 02
Expected setup step when enabled: The connection configured for each Hoop user
- 03
Expected setup step when enabled: Read or free-busy access for conflict calendars
- 04
Expected setup step when enabled: Writer permission on the selected write-back calendar
- 05
Expected setup step when enabled: Explicit full two-way mode if Google events should become Hoop appointments
Expected requirements and limits
- Expected constraint for this path: Conflict calendars are availability-only and do not receive Hoop bookings.
- Expected constraint for this path: Events marked Free do not block availability.
- Expected constraint for this path: Full two-way mode can create appointments, guest contacts, and workflow activity, so it should be enabled deliberately.
- Expected constraint for this path: Showed and No Show statuses do not write back to Google.
- Expected constraint for this path: Selecting multiple write-back paths can create duplicate calendar events.
- Authentication
- Expected authentication if this path is enabled: Connect the Google account, then approve Calendar read and write access plus the requested profile and email permissions.
- Account requirements
- Setup assumptions only; confirm Hoop access first. A Google account with Calendar enabled and a Hoop user who can manage calendar connections.
Sources
The linked sources and profile copy were reviewed on Aug 9, 2026. These sources document the connected service's rules and APIs; they do not confirm that the connection is enabled in Hoop or in a particular account. The next source review is due Nov 9, 2026.
