How to Connect Website Bookings to Google Calendar
A practical guide to Niwa's Google Calendar connection, including administrator and staff authorization, busy-time checks and sync verification.
Connect website bookings to Google Calendar through the booking system's authorized calendar integration. With Niwa on WordPress, the administrator can connect a Google account for booking visibility, and staff can connect their own calendars so external busy time affects their appointment availability.
Make the distinction clear during setup: the website saves the booking, while the calendar connection handles busy-time access and synchronization. Test both outcomes before your team relies on the connection.
Identify whose calendar needs to connect
Start with the people who provide the appointments. Decide whether the owner needs an overview of all bookings and which staff members also need their personal work commitments checked.
Niwa's administrator calendar receives bookings for oversight. A team member's connection serves a different purpose: their Google busy time can block appointments for that member. Connecting only the owner's account should not be treated as proof that every employee's external commitments are included.
The inspected Niwa connection uses the account's primary Google calendar. If your process depends on several secondary or shared calendars, discuss that requirement explicitly before adopting this setup. Do not assume an account connection automatically includes every calendar visible in the Google interface.
Open Niwa's calendar controls
In WordPress, open Niwa's Lead Capture area and its Scheduler tab. The Administrator calendar card contains the Google connection controls and the required data-control confirmation.
Read the connection notice. Configure the relevant AI provider accounts to exclude calendar data and derived results from generalized training, then save the account-specific confirmation in Niwa. Follow the instructions shown for the provider you actually use.
This confirmation applies to the calendar connection. Local booking and other Niwa assistance can operate without connecting Google. The Niwa setup guide provides the broader installation foundation.
Before authorizing, check that you are signing into the account the business intends to connect. A browser can contain several Google sessions, and an owner's personal account may be an unintended destination for work appointments.
Authorize the administrator and staff accounts
Choose Connect with Google in the Administrator calendar card. Review the authorization request, approve the intended connection and return to Niwa. Check the account shown in the connection status.
For a staff member, save their record and email address first. Use Send calendar connection link beneath that member's settings. The member follows the private link, chooses Connect with Google and approves their own account.
Treat that link as private. If it expires or the member needs to reconnect, use the administrator controls to send a current link. Do not circulate one employee's authorization link among the whole team.
The Niwa booking overview explains how staff assignments determine which member's availability is relevant to a service.
Verify busy time with a controlled example
Choose a service assigned to the connected staff member. In that person's connected primary calendar, create a clearly identified future test event marked as busy during otherwise available working hours.
Check the website's available times for the same service and date. The appointment should respect the external busy period as well as the local service duration, working hours and buffer.
Confirm the timezone on both sides. A nine o'clock calendar event and a nine o'clock website appointment can refer to different moments if the interfaces show different zones.
Remove the test event through the same account and allow the availability check to refresh. If the result is unexpected, inspect the account and member assignment before changing service hours to compensate.
Check the saved booking and its synchronized event
Make a controlled website reservation at a valid time. Inspect the Niwa appointment record first, including the service, staff member, date and customer details.
Then check the connected administrator and relevant staff calendar. Calendar synchronization runs separately from the local reservation and can take additional processing time. A missing event should lead to a connection or sync investigation, not an automatic second booking.
Test the change operations your business intends to use. Do not assume that dragging an event in Google edits the website appointment or that every external calendar change is imported into Niwa. Establish the supported direction of each action and tell staff where to make appointment changes.
Keep Google's own booking pages separate
Google also offers appointment schedules that generate their own booking page. Its setup guide explains that product. Linking such a page from your website is a separate route from synchronizing a Niwa appointment.
Choose one clear customer booking destination for a given service. Two independently managed reservation pages can leave staff unsure which system owns the appointment.
Record the connected account and the person responsible for monitoring it. When access is revoked or an account changes, review the public booking flow as well as the connection status.
Bring your calendar arrangement to a Niwa demo. Include staff assignments and any secondary-calendar requirements so the proposed setup can be checked against the schedule you actually use.
