This section connects Easy Booking to a Google Calendar. The connection uses Google OAuth, a secure authorisation method that lets you grant access to a specific Google account without sharing its password.
The setup has two parts:
- Create Google credentials in Google Cloud.
- Add these credentials to WordPress and authorise the connection.
Keep the Easy Booking Google Calendar settings page open in a separate browser tab throughout this setup. You will need to copy the redirect URI shown there.
1. Open the Google Calendar connection settings
In your WordPress administration area, open the Easy Booking > Google Calendar Sync settings page.
Locate the following information:
- the Redirect URI (also called Authorised redirect URI);
- the fields for the Client ID and Client secret;
- the button used to connect or authorise Google Calendar.
Copy the Redirect URI exactly as displayed. Do not change it, add a trailing slash or spaces, or use your website homepage instead.
2. Create a Google Cloud project
- Go to the Google Cloud Console.
- Sign in with the Google account that will manage the connection.
- At the top of the page, open the project selector.
- Click New Project.

- Enter a clear name, for example
My Website - Easy Booking. - Choose an organisation or location if Google asks you to do so.
- Click Create.

- Make sure the newly created project is selected in the project selector.

3. Enable the Google Calendar API
The Google Calendar API allows the plugin to read and create calendar events.
- In Google Cloud Console, open the main menu at the top left of the page.
- Go to APIs & Services → Library.

- Search for
Google Calendar API. - Open Google Calendar API from the results.

- Click Enable.

If the page displays Manage instead of Enable, the API is already enabled and you can continue.
4. Configure the Google consent screen
Before Google can ask for permission to access a calendar, the project needs a consent screen. This is the screen you will see when you connect your Google account.
- In Google Cloud Console, go to APIs & Services > OAuth consent screen. You can also search Google Auth Platform in the search bar ar the top.
- If Google Auth Platform has not yet been configured, click Get started.

Branding
Complete the requested application information:
- App name: use a name that you will recognise, such as
My Website Booking Calendar. - User support email: select your email address.
Click Next.
Audience
Choose the audience that matches your situation:
- Internal: choose this option only if you use Google Workspace and every Google account that will connect a calendar belongs to your organisation (for example,
name@yourcompany.com). This is the recommended option for a company-only setup. - External: choose this option if you use a personal Gmail account, or if calendars may be connected by people outside your Google Workspace organisation. This is the recommended option for most Easy Booking installations.
Choosing External does not list your application publicly or make it discoverable to all Google users. It only allows Google accounts outside a single Workspace organisation to complete the authorisation when they use your website’s connection process.
Click Next.
Contact information
Enter an email address where Google can contact you.
Finish
Click Create or Save to finish the initial configuration.

Add test users when using an External app
For a personal setup or an app that has not been published, Google normally keeps an External app in Testing mode.
- Open the Audience section.
- Under Test users, click Add users.
- Add the Google email address that you will use to connect the calendar.
- Click Save.

In Testing mode, only the email addresses listed as test users can complete the authorisation. Google may also require you to reconnect periodically. This is normal during testing.
Google’s interface may use the sections Branding, Audience, and Contact information rather than the older “OAuth consent screen” page. Google’s current guidance is available in its OAuth consent configuration documentation.
5. Create OAuth credentials
You now need to create credentials that identify your WordPress website to Google.
- In Google Cloud Console, open Google Auth Platform → Clients.
- Click Create client.

- For Application type, select Web application.
- Give the client a recognisable name, for example
Easy Booking - My Website. - Under Authorised redirect URIs, click Add URI.
- Paste the Redirect URI copied from the plugin settings page in step 1.
- Click Create.

Google will display a Client ID and a Client secret.
- Copy both values.
- Store the Client secret securely.
- Do not publish the Client secret in a screenshot, email, public repository, or support request.

6. Add the credentials to WordPress
Return to the Easy Booking Google Calendar settings page in WordPress.
- Paste the Google Client ID into the Client ID field.
- Paste the Google Client secret into the Client secret field.
- Click the Save changes button at the bottom.
- Only after saving settings: Click the button to connect or authorise Google Calendar.

7. Authorise your Google account
Google opens a sign-in and permission screen.
- Sign in with the Google account that owns or can manage the calendar you want to use.
- If prompted, select the Google account.
- Review the permissions requested by the plugin.
- Click Allow to grant access.
- You will be redirected back to your WordPress administration area.
If Google displays a warning that the application has not been verified, this usually means that the Google Cloud project is still in Testing mode. Make sure the connecting account has been added as a test user, then use the available option to continue.

8. Confirm that the connection is complete
Back in WordPress, the plugin should show that the Google account is connected.
Check that:
- the correct Google account is displayed;
- the calendar list can be loaded;
- the calendar you intend to use is available for selection.
Select the required calendar(s), then save the settings.

Your Google Calendar connection is now ready. Continue with the next section to configure how the plugin uses the connected calendar.
9. Publish the Google app to production
At this stage, the Google app is usually still in Testing mode.
Testing mode is useful while setting up the connection, but it is not suitable for normal use:
- only listed test users can connect;
- Google displays an “unverified app” warning;
- authorisation expires after seven days, so the calendar connection must be renewed regularly.
To keep the connection active, publish the app to production.
- Return to Google Cloud Console.
- Open Google Auth Platform → Audience.
- In the Publishing status section, click Publish app.
- Confirm that you want to move the app to In production.
After publishing, your app is available to Google accounts outside the test-user list.
Important: Google verification
Google Calendar permissions are considered sensitive permissions. Once the app is in production, Google may display an “unverified app” warning until the Google Cloud project has completed OAuth verification.
For a personal installation or a small private team, you can normally continue through this warning. However, if the plugin is used by many different people, the Google project owner should submit the app for Google verification.
To request verification:
- Open Google Auth Platform → Verification Center.
- Complete the branding details, including your website homepage, privacy policy, and support contact details.
- Confirm the Google Calendar permissions requested by the plugin.
- Click Prepare for verification and follow Google’s instructions.
- Submit the request.
Google may request additional information, such as a short video showing how the plugin uses Google Calendar.
Recommendation: Use a separate Google Cloud project for testing and another one for your live website. Once the production project is configured, update the Client ID and Client secret in WordPress, then reconnect the calendar.
Google documents the production publishing status and the seven-day Testing-mode authorisation limit in its Audience documentation. Its verification guide explains the information Google may request.

