Help Center


Google Calendar Sync

You can integrate Bookly with Google Calendar so that all new bookings created in Bookly Calendar will be automatically copied to the Google Calendar, and vice versa.

Bookly offers three modes of Google Calendar synchronization:

Before you select the synchronization mode, please read carefully the following instructions to set up the connection between two calendars (this instruction can also be found in Bookly menu > Settings > Google Calendar).

gc-settings-backend.png

Open Google Calendar tab in Bookly menu > Settings. Enter your Client ID and Client secret.

To find your client ID and client secret, do the following:

1. Go to the Google Developers Console and select a project, or create a new one.

2. Make sure that a Calendar API is enabled. Click on APIs and Services (on the left), look for Google Calendar API and enable it.

3. Click on Credentials on the left sidebar menu, and go to the OAuth consent screen. Give a name to the product and click Save.

4. Go back to the Credentials tab, click on Create credentials and select OAuth client ID in a drop-down menu.

google-sync-01.png

5.  Select Web application and provide the necessary information to create your project’s credentials.

6.  For Authorized redirect URIs enter the Redirect URI (can be found in Bookly menu > Settings > Google Calendar). Then click Create.

google-sync-02.png

7.  In a pop-up window, you’ll see your client ID and client secret. Use them to fill up the form in Bookly settings. Click Save.

google-sync-04.png

 

After you’ve configured the settings, go to Staff Members tab, select your employee and click Connect to synchronize staff member’s appointments with Google Calendar.

google-sync-03.png

 

The following video explains how to find the Google Calendar ID:

https://www.youtube.com/watch?v=m_ph_hYT_SY

Finally, log in to your Google account and give the permission for plugin to access your Google Calendar.

 

For current users, if experiencing syncing issues after adding new staff members:

Go to Bookly Settings > Google Calendar > Redirect URI. Copy the updated link and paste it in your Google API Console > Credentials > Web Application > Authorized Redirect URIs.

You did it in the past, and as the URI may change with regular updates of the plugin, you will occasionally need to tell Google API what new URI to authorize.

Doing this will most likely solve the sync issue. If it persists, please let us know at support@bookly.info.

 

Bookly allows you to set up the way your booking information will be displayed in Google Calendar.

Template for event title

Choose details for Google Calendar event description that is created via Bookly. Available codes are {service_name}, {staff_name} and {client_names}.

Appointment section

Use available shortcodes for the appointment-related information that will be displayed in Google Calendar.

Customer section

Use available shortcodes for the customer-related information that will be displayed in Google Calendar.

 

One-way sync

If you enable this type of sync, all new appointments created in Bookly Calendar, including custom fields, and any further changes will appear in Google Calendar.

 

Two-way front-end only

If you enable this type of sync, all updates in Bookly will automatically appear in your Google Calendar. Events that were initially created in Google Calendar will not be copied and displayed in your Bookly Calendar. Google Calendar events will be taken into account when offering available time slots to clients in your booking form. So if you have an event in Google Calendar, then the corresponding time slot won’t be available for booking because Bookly will consider this time slot as busy.

Please note that it can take some time to sync all appointments between two calendars which can result in a delay when loading the Time step in a booking form. We recommend that you limit the number of fetched events related to this feature as too many events in Google calendar may lead to a lack of memory in PHP when Bookly tries to fetch all events.

 

Two-way sync

If you enable this type of sync (available with installed Advanced Google Calendar add-on), you’ll get a full two-way synchronization which allows keeping all your Bookly calendar data and any further schedule updates in sync with Google Calendar. All new bookings created or updated in Bookly Calendar will be automatically reflected in the Google Calendar, and vice versa.

Important: it is necessary to configure settings in Google Calendar first, before selecting this type of sync and clicking Save. Your website must use HTTPS.

Please read the following instructions carefully, and visit this page for more details about the implementation of calendar data "incremental synchronization".

Bidirectional sync consists of two stages:

1. Initial full sync is performed once at the very beginning in order to fully synchronize the client’s state with the server’s state. The client will obtain a sync token that it needs to persist.

The first stage of the initial full sync will be performed at the time of the two-way sync activation. When you click Save, all appointments from Bookly will be copied to Google Calendar, and all appointments from Google Calendar will be copied to Bookly.

In the Sync appointments history field, you can specify how many days of past calendar data you wish to sync. For example, if you enter 1 in this field, both calendars will sync appointments history starting from yesterday.

Note: Initial sync may take a long time depending on the number of events to be synchronized.

2. Incremental sync is performed repeatedly and updates the client with all the changes that happened ever since the previous sync. Each time, the client provides the previous sync token it obtained from the server and stores the new sync token from the response.

Incremental sync starts functioning after initial full sync has been performed. Bookly triggers incremental sync when Google Calendar informs your Bookly Calendar about changes by push notifications.

Registering your domain

You must register the domain for any URLs you plan to use to receive push notification messages. In addition, before you register a domain, you must first verify that you own it. This step is an abuse-prevention measure to stop anyone from using push to send messages to someone else’s domain.

Step 1: Verify that you own the domain

Before you can register your domain, you need to verify that you own it. Complete the site verification process using Search Console. For more details, see the site verification help documentation.

Step 2: Register your domain

To register a verified domain name as one of the allowed domains for your project, do the following:

1. Go to the Domain verification page in the API Console.

2. Click Add domain.

3. Fill in the form, then again click Add domain.

At this point, the Google API Console checks all domains in the list against the ones that you have verified in Search Console. Assuming that you properly verified all the domains, the page updates to show your new list of allowed domains. You now can use any of these domains to receive push notifications.

 

If you want to get more technical information, follow these links:

https://developers.google.com/calendar/v3/sync

https://developers.google.com/calendar/v3/push

 

Manual synchronization

You can force a new incremental sync by clicking on the Google Calendar button on the top right of the Bookly Calendar.

manual-sync.png

NOTE: When you create All day event in Google Calendar, its status is set to Free by default. You should change its status to Busy to display this event in Bookly Calendar.

02.png

 

DEMOVIDEO TUTORIALMAIN BOOKLY SETTINGSFAQADD-ONS

 

See these articles for troubleshooting the most common issues with Google Calendar sync:

I am unable to connect a staff member to Google Calendar

There are discrepancies between my website and Google Calendar. What can I do?

Google Calendar sync has stopped working properly after an update. How do I fix it?

My google calendar synchronization is not working. I see this error in Staff Members tab: “Could not json decode the token.”

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk