Skip to main content
The Google Calendar Find free slots action retrieves free and busy time slots for one or more calendars within a specified time range. Use this read-only action to find common availability across multiple calendars before scheduling meetings. The action supports multiple calendar identifiers including primary calendars, user or resource email addresses, and calendar IDs. It returns both busy intervals with event metadata and calculated free slots between them. If you do not supply start or end datetimes, the action defaults to the current day in UTC.

​
Limitations

  • The action can return free/busy information for at most 50 calendars (calendar_expansion_limit) and can expand at most 100 calendar identifiers for a single group (group_expansion_limit); higher values cause errors.
  • Every entry in Calendar identifiers must be a valid calendar identifier such as primary, a calendar or user email, or a supported calendar ID. If any identifier is invalid or not found, the action returns an error instead of partial results.
  • Each call uses one time zone context for interpreting the start and end datetimes and for computing free slots.

​
Prerequisites

  • Glean action must be enabled for your instance and the Google Calendar action pack must be available.
  • Ensure a connected Google Calendar account exists for the user. The user must have permission to read free/busy information for each calendar identifier included in Calendar identifiers.
  • Google Calendar must be connected as a data source for Glean actions.
  • The user must pass a valid time zone identifier so the action can correctly interpret the requested time window.

​
Supported parameters

NameTypeDescription
Start datetimeDatetimeStart of the time window to analyze. If omitted, the action uses the beginning of the current UTC day as the default start time.
End datetimeDatetimeEnd of the time window to analyze. Must be later than Start datetime when both are provided. If omitted, the action uses the end of the current UTC day by default.
TimezoneTimezoneTime zone used to interpret Start datetime and End datetime and to present computed free and busy slots. Marked as a recommended field in the action schema.
Calendar identifiersArrayList of calendar identifiers to query. Each item must be a valid calendar identifier: primary, a calendar or user email (for example, [email protected]), or a calendar ID ending with a Google Calendar domain. All identifiers are validated and the action returns an error if any entry is invalid or not found. Defaults to ["primary"] when omitted.
Calendar expansion limitIntegerMaximum number of calendars for which the action provides free/busy information. Default is 50; higher values are not allowed and will result in an error.
Group expansion limitIntegerMaximum number of calendar identifiers that can be expanded for a single group. Default is 100; an error is returned if a group contains more members than this value.

​
Usage example

You want to schedule a meeting with three team members and need to find a time when everyone is available next week. Instruction to an agent: “Find a 1-hour time slot next Tuesday or Wednesday when [email protected], [email protected], and [email protected] are all available.” Resulting behavior:
  • Calls Find free slots with:
    • Calendar identifiers set to [“[email protected]”, “[email protected]”, “[email protected]”].
    • Start datetime set to next Tuesday at 9:00 AM (for example, 2025-01-14T09:00:00).
    • End datetime set to next Wednesday at 6:00 PM (for example, 2025-01-15T18:00:00).
    • Timezone set to the user’s local timezone (for example, America/Los_Angeles).
  • Retrieves availability data including:
    • Busy intervals for each calendar with event details (start time, end time, event summary).
    • Calculated free slots between busy periods that are common across all three calendars.
  • Identifies free slots of at least 1 hour duration.
  • Presents the available time slots to the user, for example:
    • Tuesday 1:00-2:00 PM
    • Tuesday 3:30-5:00 PM
    • Wednesday 10:00-11:30 AM
  • User selects a slot and the agent can pass it to Create event to schedule the meeting.
Workflow tip: Combine this action with Create event to build intelligent scheduling agents. Use the returned busy event metadata to filter out lunch hours or focus time blocks. Set appropriate Calendar expansion limit if querying many calendars to avoid exceeding the 50-calendar maximum.

​
Troubleshooting

  • Possible cause: One or more entries in Calendar identifiers are not valid calendar IDs or emails, or refer to calendars the caller cannot access.
  • Fix: Verify that each identifier is primary, a correct email address, or a valid Google Calendar ID such as one ending with @group.calendar.google.com, and that the caller has permission to view its free or busy information.
  • Possible cause: The start date time is equal to or later than the end date time.
  • Fix: Adjust the values so that Start datetime clearly precedes End datetime, or omit one of them to fall back to the default current day window.
  • Possible cause: Internal restriction level or beta status prevents the action from being listed in that context.
  • Fix: Ask your Glean admin to confirm whether this action is enabled for your tenant and whether your environment is configured to surface beta actions.

​
FAQs

If Start datetime or End datetime are omitted, the action defaults to querying the current day in UTC and still enforces that the effective start precedes the end of the window.
Yes. As long as you include valid calendar identifiers such as user or resource email addresses or calendar IDs ending with a supported Google Calendar domain, the action will validate them and include their availability in the response.