All Collections
Google Workspace Calendar Integration
Google Workspace Calendar Integration

This document provides instructions for PeopleForce users on how to integrate Google Calendar using Google Service Accounts.

Updated over a week ago

This document provides instructions for PeopleForce users on how to integrate Google Calendar using Google Service Accounts. This will allow your platform to interact with Google Calendar API and perform operations such as creating events in user calendars and checking availabilities for one-on-one meetings and interviews, without manual user intervention.


Integrating Google Calendar with PeopleForce offers a range of advantages:

  1. Streamlined Interview Scheduling: By automating the interview scheduling process, you can save valuable administrative time.

  2. Real-time Employee Availability: With the integration, you can easily check the real-time availability of your employees. This simplifies the process of scheduling one-on-one meetings and team events, as you can identify suitable time slots based on individual and team calendars.

  3. Enhanced Collaboration: By creating events directly in user calendars, the integration ensures that all relevant parties are informed about scheduled meetings and tasks. By integrating Google Calendar with PeopleForce:


  • Google Cloud Platform (GCP) account;

  • Basic understanding of Google Cloud Console and APIs;

  • Super Administrator access for your Google Workspace domain.

⚠️ Please note that Google Workspace is not a free service and must be purchased for company use.

Step 1: Create a Google Cloud Project

  1. Create a new project by clicking on the project dropdown and selecting "New Project"

Step 2: Enable Google Calendar API

  1. In the Google Cloud Console, select your project.

  2. From the left panel, click ''API & Services > Library.''

3. In the quick search, search for "Google Calendar API".

4. Click on the API card and then click on "Enable".

Step 3: Create a Service Account

  1. Navigate to "IAM & Admin > Service Accounts" in the Cloud Console.

2. Click on "Create Service Account".

3. Input a name and description for the service account.

4. Click on "Create and continue" and then "Done"

Step 4: Generate a key for the service account

  1. Go back to the ''Service Accounts'' page.

  2. Click on the service account you just created.

  3. Go to the "Keys" section and click on "Add Key".

4. Select "JSON" for the key type.

5. Click "Create". This will generate a JSON key file and download it to your computer. Make sure to keep this file secure and accessible, as you'll need it for your application to authenticate with Google.

Step 5: Delegate Domain-Wide Authority to Your Service Account

  1. As a super administrator, go to your Google Workspace domain's Admin console .

2. Go to ''Security > API Controls''.

3. In the Domain-wide delegation pane, select "Manage Domain-Wide Delegation".

4. Click ''Add new.''

5. In the "Client ID" field, enter the client ID found in your service account JSON key file.
6. In the ''0auth scopes'' field, enter the following four values:

7. Click the ''Authorize'' button.

Step 6: Use the Service Account in PeopleForce

Now, in the PeopleForce platform, you can input the path to the downloaded JSON key file. To configure this integration, follow these steps: Navigate to Settings, select Integrations, and choose Google Calendar. Next, simply paste the JSON key file from your account into the designated field and click the Install button.


All actions performed by a service account will appear as if they were done by a user whose email is specified during the "delegating domain-wide authority" process. Please make sure to use the service account responsibly and abide by the terms of use set out by Google.


What will happen if existing customers uninstall the integration and then attempt to reinstall it?

Existing customers who have integrated before, will stay with the original implementation as work as normal, however if they uninstall the integration, when they try to install it again, it will now ask for the JSON key using the new method of integration.

Did this answer your question?