Limited time discount Spring Deals Are in Full Bloom
Up to 50%Off
Grab now
Sign In
Help Center
EN
Get started

How do I set up Google Calendar integration in Amelia using the advanced method

The advanced Google Calendar setup allows you to connect Amelia with Google Calendar by creating OAuth credentials in the Google Cloud Console. This method is intended for users who need full control over authentication, branding, or organizational Google accounts. While the setup involves several steps, it is a one-time configuration and ensures reliable synchronization between Amelia and Google Calendar when completed correctly.

Important note about Google app verification

When using the advanced setup, you are creating your own Google application in Google Cloud Console. In this case, you are considered the developer of the integration, not Amelia.

Because the application is newly created and not verified by Google, users may see a Google hasn’t verified this app warning when connecting employee calendars.

This warning is expected and does not prevent the integration from working. It simply means that the application has not gone through Google’s optional verification process.

You can safely continue by choosing Advanced → Go to your app, since the credentials were created by you.

If desired, you can also submit the application for verification through Google Cloud Console, but this is not required for the Amelia integration to function normally.

If you decide to verify the app, check the section below for the next steps.

Alert Please note

Google frequently updates and reorganizes the Google Cloud Console interface. While menu labels and navigation paths may change over time, the core configuration steps described below remain the same.

How do I prepare Amelia for the advanced Google setup?

Before starting the advanced setup, make sure the standard Google connection is not active.

If the Sign in with Google method was previously used, disconnect it first, as this method disables manual configuration by locking the Client ID and Client secret fields.

Once disconnected, open Amelia → Features & Integrations → Integrations → Google Calendar & Google Meet → Set up, and switch to the General tab.

This is where you will later paste the credentials generated in Google Cloud Console.

What needs to be configured in Google Cloud Console?

The advanced setup requires creating or configuring a Google Cloud project and allowing it to communicate with Amelia. Regardless of interface changes in Google Cloud Console, the setup always includes these core steps:

  1. Create or select a Google Cloud project
    You can either create a new project or use an existing one. The project acts as a container for all Google APIs and credentials used by Amelia.
  2. Enable the Google Calendar API
    Inside the selected project, the Google Calendar API must be enabled. Without this, Amelia cannot create or manage calendar events.
  3. Create OAuth 2.0 credentials
    You must create OAuth credentials for a Web application. These credentials are used to authenticate Amelia when it communicates with Google.
  4. Add the Redirect URI from Amelia
    Google requires a redirect URL to confirm secure authorization. Copy the Redirect URI shown in Amelia’s Google integration settings and paste it into the OAuth configuration in Google Cloud Console.
  5. Copy the Client ID and Client secret into Amelia
    After creating the credentials, copy the generated Client ID and Client secret and paste them into the matching fields in Amelia’s General tab.
  6. Publish the app
    The OAuth app must be published so Google allows real users to authenticate. Unpublished apps may work only for test users or fail during employee connections.

How do I create a new Google Cloud Project?

  1. Go to the Google Cloud Console.
  2. Click on the Project Picker in the top left (next to the “Google Cloud” logo) or press CTRL+O.
  3. In the pop-up, click NEW PROJECT in the top right corner.
  4. Select No Organisation (if you’re using a free Google account) or your company profile (if you’re using Google Workspace).
  5. Enter the project name (e.g., Amelia GCal Integration) and click CREATE.
Creating a new Google Cloud project for integration with Amelia
Info Tip
For business accounts, make sure you select your company’s organization. For personal accounts, “No Organisation” will be the default.

How do I enable the Google Calendar API?

  1. Once the project is created, click Select Project from the notification in the top right of the page (or open the Project Picker again with CTRL+O and select the project you just created).
  2. Open the menu (☰ in the top left, or just press “.” on your keyboard).
  3. Go to APIs & Services → Library.
  4. Type google calendar api in the search bar.
  5. Click Google Calendar API, then click Enable.
Enabling Google Calendar API in Google Cloud Console

How do I create my OAuth Credentials?

  1. After enabling the API, click Create Credentials in the top right corner of the screen;
  2. Alternately, go to APIs & Services → Credentials and click the mid-screen + Create Credentials drop-down → OAuth client ID;
  3. Choose:
    • Google Calendar API;
    • User Data
    • Click Next.
Creating OAuth credentials for Google Calendar
  1. Enter an App name (e.g., Amelia GCal).
  2. Choose your own email for both the User support email and the Developer contact information.
  3. Click Save and Continue.
OAuth consent screen developer information in Google Cloud Console

How do I define the OAuth Client ID?

Don’t make any changes on the next step (Scopes) unless you plan to submit the application for verification – just click on Save and Continue again. This will bring you to the OAuth Client ID:

  1. Under “Application type”, choose Web Application.
  2. Give it a name (e.g., Amelia GCal).
  3. Scroll down to Authorized redirect URIs, click + Add URI, and paste the Redirect URI from Amelia → Features & Integrations → Integrations → Google Calendar & Google Meet → Set up → General tab.
    • Example: https://yourdomain.com/wp-admin/admin.php?page=wpamelia-employees
  4. (Optional but helpful) If you’re using the front end Employeepanel, click the + Add URI button and add the full panel URL (e.g., https://yourdomain.com/staff-portal/). Don’t forget the trailing /.
  5. Click Create.
Defining Redirect URI in Google Cloud Console
Info Important

Make sure to add the Authorized Redirect URI, not the Authorized JavaScript origins (screenshot above).

Your website must use HTTPS (HTTP will not work).

Do not leave the app in “Testing” mode. It will disconnect employees every 1–2 days. Make sure to publish it to Production.

Optional: Submitting the app for Google verification

If you want to remove the “Google hasn’t verified this app” warning when employees connect their calendars, you can submit the OAuth application for verification in Google Cloud Console.

To prepare the application for review, you will need to configure the following scopes in the OAuth consent screen:

  • /auth/calendar.readonly
  • /auth/calendar.events

App verification is not an automated process and is handled entirely by Google. The review may require additional information about how the application uses Google data.

For complete instructions on submitting an app for verification, follow Google’s official guide.

Please note that verification is optional. Even without verification, the integration will work normally; Google will only display a warning during the authorization step.

How do I acquire my Client ID and Client Secret?

While still on the Credentials screen, copy the Client ID and paste it into the corresponding field in Amelia → Features & Integrations → Integrations → Google Calendar & Google Meet → Set up → General, and then click Done (in Google Cloud console).

Copy the Client ID from Google Cloud Console into Amelia

If you accidentally skip this step, you can still access the Client ID when fetching the secret:

  1. Open the menu (☰ in the top left, or just press “.” on your keyboard).
  2. Go to APIs & Services → Credentials.
  3. Under OAuth 2.0 Client IDs, click the name of your app.
  4. On the right, you’ll see your Client ID and a hidden Client Secret (click the copy button).
  5. Paste these values into the corresponding field in Amelia → Features & integrations → Integrations → Google Calendar & Google Meet → Set up → General.
Copying Client ID and Secret for Amelia

How do I publish the app?

  1. Open the menu (☰ in the top left, or just press “.” on your keyboard).
  2. Go to APIs & Services → OAuth consent screen → Audience.
  3. Under Publishing Status, click Publish app.
  4. Confirm when asked “Push to production?”.

That’s it! Amelia is now connected to Google Cloud!

Publishing the Google app into production

What should I keep in mind when using the advanced setup?

  • The advanced setup is intended for users who require full control over OAuth credentials or branded Google authorization screens.
  • The Redirect URI must match exactly. Any mismatch will prevent authentication.
  • After the connection is established, employees can link calendars according to the rules explained in the Google Calendar settings article.
  • This setup is a one-time configuration. You do not need to repeat it unless credentials are revoked or the domain changes.
  • Advanced setup does not work on localhosts as Google prevents adding http:// in Redirect URI fields.