Help center
HelpIntegrationsConnecting Google Calendar.
Connecting Google Calendar.
How the calendar integration schedules human rounds, what permissions we ask for, and what we never write back.
Last reviewed 22 June 20263 min read

Google Calendar is the scheduling integration we ship at V1. It is used to book human rounds with finalists, and to surface a hiring-manager availability hint to the candidate before the AI interview.

Permissions we ask for.

  • Read free-busy data on the connected calendars. We do not read event titles, attendees, or descriptions.
  • Create events on the connected calendar (the human-round invite, with the candidate attached).
  • Update or cancel events we created (for reschedules).

We never read calendar events we did not create. We never write to a different calendar than the one the user authorised. Tokens are stored encrypted at rest and rotated on the standard Google refresh cycle.

What appears on the candidate side.

Once a finalist is advanced, the candidate sees a Calendly-style picker showing the next two weeks of available slots, drawn from the connected hiring-manager calendars. The slots are filtered to working hours and to the role timezone. When the candidate picks one, we create the event and send the calendar invite to both sides.

Microsoft 365 Calendar ships in the first 90 days post-launch. iCloud Calendar is not on the V1 roadmap.

What to do next: connect the calendar of every teammate who runs human rounds, and confirm the working-hours setting per teammate.

google calendarschedulingoauthpermissions
Still stuck?
One email gets a human reply inside 24 hours.
Email help@picked.aiStatus page
Connecting Google Calendar. | Help · Picked.ai