Google Calendar integration: interviews, 1:1s and time off

What the integration adds to your calendars

Scheduling in PeopleForce is enough: nobody copies a meeting into a calendar or pastes a video link by hand. More than 500 companies have the integration connected.

Workflows can add events too, with the Create a calendar event step: for example, a welcome meeting in a new hire's first week.

Interviews with a Google Meet link

When you schedule an interview, it goes into your Google Calendar with the interviewers invited, plus the candidate unless you untick Invite candidate. The event carries the vacancy, candidate details, CV and, for the Google Meet method, a Meet link. Over the past year, more than 110,000 interviews reached Google Calendar this way.

Recurring 1:1s with their talking points

A weekly or monthly 1:1 becomes one recurring event in the organiser's calendar, with the employee invited, a Google Meet link and the talking points that aren't private. A 1:1 added outside the repeat gets an event of its own.

Approved time off in the employee's calendar

Once a request is approved, the time off appears in the employee's own calendar, all day or for the requested hours. The leave policy decides how it shows: busy for non-working leave, free for working leave such as work from home. Withdrawing the request removes the event.

Free slots from everyone's calendars

The time picker checks the calendars of the interviewers, or of both people in a 1:1, and lists only the slots when they are all free, in 15- or 30-minute steps. It reads when people are busy, not what their events are.

Mechanics

What moves between PeopleForce and Google Calendar

Almost everything moves one way. PeopleForce creates each event a moment after something is scheduled or approved, and keeps interviews and 1:1s up to date as they change. What comes back is the Google Meet link, which PeopleForce shows as a Join button, and busy time for the time picker.

What is transferred	Direction	When	Data
Interviews Scheduled in Recruit	PeopleForce Google Calendar	when scheduled updated on reschedule, removed on cancel	subject as title, time, location, interviewers, candidate if invited, vacancy and candidate details, CV, Google Meet link
1:1s Set up in Perform	PeopleForce Google Calendar	when set up one recurring event for weekly and monthly 1:1s	"1:1: name <> name", time, attendees, talking points except private ones, Google Meet link
Approved time off Leave requests	PeopleForce Google Calendar	on approval removed if withdrawn	leave type as title, dates or hours, busy or free, public or private
Workflow events Create a calendar event step	PeopleForce Google Calendar	when the step runs	title, description, time or all day, location, guests, busy or free
Google Meet link Interviews and 1:1s	Google Calendar PeopleForce	when the event is created or when an interview is switched to Google Meet	the Meet link, shown as Join on the interview and the 1:1
Busy time For the time picker	Google Calendar PeopleForce	while picking a slot	busy periods per person on the chosen day, without event details

Move an event in Google Calendar and PeopleForce keeps the original time. Reschedule the interview or 1:1 in PeopleForce, and the calendar follows.

Scheduling interviews in Recruit?

See how the time picker, Meet links and invitation templates work together

See interview scheduling

Setup

How the connection is set up

One connection covers the whole company. A Google Workspace super admin authorises a key, someone with access to PeopleForce's Integrations settings installs it, and nobody has to connect their own calendar.

Step 1 · Google Workspace

Create a key and authorise it

The authorisation needs a Google Workspace super admin.

Create a service account in Google Cloud with the Google Calendar API enabled, and download its JSON key. In Cloud organisations created on or after 3 May 2024, an Organization Policy Administrator first has to allow key creation
Authorise its client ID for domain-wide delegation with the scope https://www.googleapis.com/auth/calendar, under Security → Access and data control → API controls
Delegation can take up to 24 hours to apply, and a second super admin confirms it if multi-party approval is on

Step 2 · PeopleForce

Paste the key and install

Settings → Integrations → Google Calendar, by a PeopleForce administrator or anyone whose role includes the Integrations settings.

Paste the contents of the JSON key into the JSON field and click Install
PeopleForce tests the key on the installer's own calendar, so the installer's PeopleForce email must be an account in that Workspace
Everyone whose PeopleForce work email is in your Workspace is then covered

Integration conditions

Whose calendars it reaches, what the access is used for, and which side stays the source of truth.

It works with Google Workspace accounts

People are matched by their PeopleForce work email, so an address outside your Workspace, such as personal Gmail, is not covered. It covers the Google Workspace organisation whose super admin authorised the key.

What the key gives access to

The calendar scope and domain-wide delegation give the key full Google Calendar access for every account in your Workspace. PeopleForce uses it only to add, update and remove its own events, read busy time for the time picker and test the connection on the installer's calendar. Interview and 1:1 events are private by default; our team can make them public on request.

PeopleForce stays the source of truth

Changes made in Google Calendar are not brought back. Nothing is copied over when you connect: items are added as they're scheduled or approved from then on, and a recurring 1:1 set up earlier is added the next time its settings are edited. Imported time off is never added, and disconnecting leaves existing events in place.