Agiled Docs

Connect a calendar before sharing booking links so Agiled can account for busy events.

Use the calendar account that owns the availability you want customers to book against. For most teams, this should be the user's work calendar, not a shared test calendar or personal account.

Confirm who will maintain the calendar connection. If the host changes roles or leaves, the booking page may need a new calendar owner.

Steps

Open Settings > Apps or the scheduling calendar connection area.
Choose Google Calendar or Outlook Calendar.
Complete OAuth with the provider account.
Return to Agiled and confirm the connection.
Review availability rules.
Create or update event types.
Test the public booking flow.

Connect each host's own calendar when multiple people take bookings. A shared calendar can be useful for visibility, but conflict checks should match the person whose time customers are booking.

If a host has multiple calendars, confirm which calendars should block availability. Personal, holiday, focus-time, and shared team calendars may need different treatment depending on how the provider exposes busy events.

The correct calendar account is connected.
Availability rules match your working hours.
Buffer times are configured on event types.
The test booking creates the expected appointment.

Also confirm timezone, working days, event duration, booking notice, and whether the calendar should create events after a customer books.

Create one busy event in the provider calendar and confirm the public booking page blocks that time before sharing the booking link.

Test The Full Flow

Open the public booking page in a private browser window, choose a time, submit the booking, and confirm:

The appointment appears in Agiled.
Busy times are blocked correctly.
The calendar event appears in the connected provider.
Confirmation email content is correct.
Cancel or reschedule behavior matches your process.

Multi-Host Checks

When several hosts take bookings, test each host or round-robin setup separately. One connected calendar does not prove every teammate's calendar, availability, and conflict checks are working.

For round-robin or pooled events, create test busy blocks for each host and confirm the booking page routes around them. This catches one broken calendar connection before customers book the wrong slot.

If Times Look Wrong

Check timezone settings in Agiled, the connected calendar account, and the customer-facing booking page. Then review event-type availability, buffers, and existing busy events on the provider calendar.

Maintenance

Review calendar connections after:

a teammate changes Google or Microsoft accounts
an admin changes provider app permissions
working hours or timezone changes
event types are reassigned to a new host
customers report seeing unavailable slots

Reconnect the calendar before troubleshooting event types if provider access has expired or the wrong account was approved.

After reconnecting, repeat the full public booking test. A successful OAuth connection does not prove event-type availability is configured correctly.

If a host leaves the team, reassign event types and booking pages before disconnecting or disabling their calendar account.

Troubleshooting Calendar Connections

If bookings ignore busy events, confirm the correct provider account is connected, busy calendars are included, and the event type is assigned to the right host.

If events do not write back to the provider calendar, reconnect the calendar and book a fresh test appointment. Existing appointments may not prove the current connection is healthy.

Connect a Calendar