How to sync WordPress bookings with a calendar

Decide what should happen when a booking is made and when staff add events to their calendar. One-way sync sends website bookings to a calendar. Two-way sync also reads busy periods from the external calendar and blocks those slots on your booking form.

Use two-way sync when staff already manage their availability in Google Calendar or Outlook. If the calendar is only for viewing bookings, one-way sync is simpler.

Open your booking plugin’s settings and look for Calendar, Integrations, Google Calendar, Outlook Calendar or iCal. WordPress itself does not contain a booking engine or a calendar synchronisation service, so the available method depends on the plugin handling your bookings.

Check whether it supports appointment times or only whole-day dates, whether it sends cancellations and reschedules, and whether external busy events can block new bookings. These differences matter more than the word ‘sync’ in the feature list.

For a basic manual route, copy the booking calendar’s iCal export URL into Google Calendar, Outlook or Apple Calendar. If the plugin also accepts external iCal feeds, copy the calendar’s private iCal URL back into the relevant booking calendar and map imported events to unavailable or booked time.

This route is fine for simple availability sharing and rental-style calendars. It is not real-time: the booking plugin or calendar service may refresh feeds periodically, and iCal usually does not provide reliable instant conflict prevention. Keep the feed private because anyone with its URL may be able to read calendar data.

For live two-way syncing, use the booking plugin’s Google or Outlook integration rather than relying on an iCal feed. The setup normally requires an OAuth application: create a project or app in the relevant provider portal, enable calendar access, add the redirect URL shown by the WordPress integration, then copy the client ID and secret into the plugin.

Grant only the calendar permissions the integration requests. If the provider leaves the app in a testing state, connecting staff accounts may fail until those accounts are added as test users or the app is moved through the provider’s publishing or verification process. Google integrations commonly require the Calendar API and OAuth credentials.

Connect the calendar belonging to each person, resource or room that can receive a booking. Select the destination calendar, then choose whether the connection is one-way or two-way. Configure the event title, description and location if the integration provides placeholders for customer, service, staff and appointment details.

Do not assume the administrator’s connection covers every staff member. Many booking systems require each staff member to authorise their own calendar and select their own calendar. Existing busy events normally block availability without appearing as normal booking records in WordPress.

Create a test booking and confirm that it appears in the correct calendar with the correct duration. Then create a busy event directly in the external calendar and check that the matching website slot becomes unavailable. Also test a cancellation and reschedule from WordPress.

Set the WordPress timezone and each connected calendar to the same named region, such as America/New_York, rather than relying on a fixed UTC offset. A mismatch can shift appointments by an hour around daylight-saving changes. If sync fails on a Friday, check expired authorisation, the selected calendar, background task or cron activity, provider permissions and the integration’s debug log before reconnecting every account.