Skip to main content
Design availability lookup before event creation. A useful first task answers whether an approved calendar is busy during a specified time window without returning event descriptions.
Google Calendar is absent from the native catalog. Threetone does not provide a Google consent wizard for this workflow. This guide prepares an external integration and its tool contract.

​
Prepare availability and booking

You need an authorized calendar owner, a test calendar, and an application responsible for Google’s OAuth consent and token lifecycle.
1

Request only the required access

Google’s Calendar authorization guide separates free/busy, event-read, and event-write scopes. Choose the narrowest scope that covers the selected calendars. Do not request event-writing access for availability lookup alone.
2

Make the time window explicit

Record the calendar ID, start and end, timezone, and meeting duration. Return availability without exposing titles or attendees unless the task requires them. Treat a failed lookup as unknown availability, never as an empty calendar.
3

Review a booking separately

Before a future event write, confirm the calendar, local date and time, attendees, description, and notification behavior. Recheck availability because the calendar may have changed. After an uncertain response, reconcile with the calendar before retrying creation.
Use tool configuration to keep lookup and booking separate. An auth connection stores supported manual credentials; it does not implement delegated Google consent or release tool execution.

​
Frequently asked questions

Design the lookup to return occupied intervals only. If event details are needed, review the corresponding scope and data access separately.
No. A lookup is a point-in-time result. A confirmed booking needs a separate authorized write and subsequent read-back.