Agiled Docs

Google Calendar connects through OAuth and supports bidirectional calendar and event sync.

Use Google Calendar when scheduling availability should respect Google events and Agiled appointments should write back to the connected calendar where supported.

Connect the Google account that owns the host's real meeting availability. If someone else manages the calendar, confirm delegated access before approving the OAuth connection.

Connect Google Calendar

Open Settings > Apps or the scheduling calendar connection area.
Choose Google Calendar.
Start the OAuth connection.
Select the Google account that owns the calendars you want Agiled to use.
Approve the requested calendar access.
Return to Agiled and confirm the connection is active.

Connect calendar accounts one host at a time when setting up a team. Test each host before moving to the next so missing slots can be traced to the correct account, calendar, or event type.

What Syncs

Calendar lists
Calendar events
Availability data used by scheduling
Appointment event updates where supported

If the Google account has multiple calendars, choose which calendar receives new appointments and which calendars should block availability. Personal, holiday, and shared calendars can each affect public slots differently.

Keep blocking calendars intentional. A shared company calendar, holiday calendar, or personal calendar can remove public availability if it is selected as a conflict source.

Before Connecting

Sign in with the Google account that owns the calendars you want Agiled to use.
Confirm your organization allows third-party OAuth apps.
Decide which calendar should receive appointment events.
Review event types and booking pages after connecting.
Confirm the Google account will remain available if the teammate who connected it changes roles or leaves.

Test Calendar Sync

Connect Google Calendar.
Create or choose an event type.
Open the public booking page.
Book a safe test appointment.
Confirm the appointment appears in Agiled.
Confirm the event appears in Google Calendar.
Cancel or reschedule the appointment and confirm the calendar behavior.

Also create one busy event directly in Google Calendar during an available window. Then open the public booking page and confirm Agiled hides that time. This proves conflict checking, not only appointment writeback.

Troubleshooting

If slots are missing, check Google Calendar conflicts, Agiled availability, buffers, and minimum notice.
If events do not write back, reconnect the app and check recent sync runs.
If OAuth fails, ask a Google Workspace admin to review app access.

After reconnecting, book one test appointment and create one busy event in Google Calendar to confirm both writeback and conflict checking.

If only one event type has missing slots, check that event type's availability, buffers, team assignment, and calendar settings before disconnecting the whole integration.

Calendar Selection Review

After connecting, review both write and conflict calendars. The write calendar receives new appointments. Conflict calendars block public availability. Shared, holiday, focus-time, or company-wide calendars should only block bookings when that is intentional.

Ongoing Maintenance

Review the connection after changing event types, booking pages, team members, calendar ownership, or Google Workspace security policies. Calendar sync can be healthy while a specific event type is still configured incorrectly.

When a teammate leaves or changes role, review any event types that used their calendar. Reassign the host or calendar before customers continue booking.

Google Calendar