In this document:
- Video Walkthrough
- Open the Google Developer APIs and Services Dashboard
- 1. Create a New Project
- 2. Searching the API Library
- Already Had a Project and Credentials from a Separate Setup?
- 3. Setting Up the OAuth Consent Screen
- 4. App Registration
- 5. Creating the OAuth Client ID and Client Secret
- 6. Add Your Google Calendar Client ID and Client Secret to SSA
To start syncing with Google Calendar, you’ll need to collect the Client ID and Client Secret from your Google API.
Our other guide covers how to enable and use the Google Calendar Sync with your Appointments and Booking Calendar: Syncing with Google Calendar.
Please note: This process changes all the time. We do our best to keep this up to date, but there’s usually no warning or notification that the process has changed.
Last Updated: April 28, 2021
Open the Google Developer APIs and Services Dashboard
Go to the Google Developer APIs and Services Dashboard.
Make sure you login to the Google account you’d like to sync with. You may also need to accept the Google Cloud Platform Terms of Service.
1. Create a New Project
Once you’re on the dashboard, create a new project or choose an existing one.
If you created a new project, you can Name it “Booking Calendar Sync”, and leave the Location set to No Organization.
Creating a new project may take a moment. You may have to refresh the page to see your new project.
Go back to the APIs and Services Dashboard.
Alternate Screen After Creating a New Project
If you see this screen after making a new project, click on the Explore and enable APIs option under the Getting Started section.
2. Searching the API Library
Inside the Dashboard, press the button that says Library on the left-side panel. That should take you to the Google API Library.
In the Google API Library, search for
calendar. Select the Google Calendar API option.
Within the Google Calendar API page, click the Enable button to add the Google Calendar API to your project.
Already Had a Project and Credentials from a Separate Setup?
This process may start to look a bit different for you at this step if you’re reusing a Project.
You’ll just need to update your OAuth Consent Screen by going to tab in the left-hand side.
If you already set up a prior OAuth Consent Screen, you could either EDIT APP or just create a New Project.
3. Setting Up the OAuth Consent Screen
From here, we can start the path to creating the API credentials. Select the Create Credentials button.
Select the OAuth Consent Screen tab. And then select the Configure Consent Screen button.
After clicking the Configure Consent Screen button, you’ll be asked to choose between an External or Internal app type.
External vs. Internal, more information here:
- External apps allow users outside your organization (@your_organization.com) to also connect SSA to their personal Google Calendar. Available to any test user with a Google Account.
- Internal apps allows only users within your organization (@your_organization.com) to also connect SSA to their personal Google Calendar.
4. App Registration
The SSA plugin is self-hosted, meaning our company never accesses your data. This app is setup as your own, where your website is the host and your are technically the developer.
4A. OAuth Consent Screen
Fill in the following fields:
- App name: “Booking Calendar Sync”
- User Support email: Use your email address
- Application Home Page: Your site domain with http or https – it should be just your domain name, no subdomains or subfolders.
- Authorized domains: Your site domain without http or https
Developer Contact Information:
- Email Addresses: Use your email address
Skip all the other fields and click Save and Continue.
4B. Adding the Scope
Select the Add or Remove Scopes button.
First, add only the Google Calendar API with the …auth/calendar scope, scroll to the end and select Update.
Click Save and Continue.
4C. Test Users
You don’t need to add Test Users for this app.
4D. Summary and Publishing the App
Here you’ll see an overview of all the information you’ve just entered. You can go ahead and click on Back to Dashboard.
In the Dashboard, you’ll get an overview of the app’s publishing status and Test Users. Click on Publish App.
This should show you a pop-up letting you know that the Google Calendar scope you’ve chosen requires verification. But, since you will not exceed 100 test users you won’t have to worry about verification or Youtube videos.
5. Creating the OAuth Client ID and Client Secret
Now, we’ll be able to generate the Client ID and Client Secret for the Simply Schedule Appointments sync settings.
Go to Credentials from the left-side menu. And click on the + Create Credentials button.
From the dropdown, select OAuth client ID.
OAuth Client ID Application
Fill in the following fields:
- Application Type: select Web application
- Name: Type in something like “Booking Calendar Sync”
- Authorized redirect URLs: enter https://
yoursite.com (your URL, no subdomains)
6. Add Your Google Calendar Client ID and Client Secret to SSA
After clicking Create, you should see your Client ID and Client secret. You can directly copy them from the popup.
Or, if you accidentally close it, you can go to Credentials page. Click on the OAuth 2.0 Client ID Name from the list. And, now you should see the Client ID and Client Secret at the top of the page.
Adding the Client ID and Client Secret to SSA
Paste your Client ID and Client Secret to the Google Calendar Sync settings in Simply Schedule Appointments. Click Save and Authorize.
Google will now ask permission for Simply Schedule Appointments to access your calendar. Go through those prompts to accepting the permissions.
If you chose the External app type you may see a screen that says This app isn’t verified. To bypass this, click on the Advanced link and then the link that says Go to yoursite.com (unsafe). That should allow you to see the permission prompts.
Afterward, your Simply Schedule Appointments calendar syncs with Google Calendar. Now, finish setting up Google Calendar in the Appointment Type settings.
File a support ticket with our five-star support team to get more help.