Agiled Docs

Apple Calendar uses manual credentials in Agiled. You need your Apple ID and an app-specific password from Apple.

Use Apple Calendar when the calendar source is tied to iCloud or an Apple Calendar account instead of Google or Microsoft. This connection is different from OAuth-based calendar apps because you enter manual credentials.

Because this connection uses manual credentials, treat password changes and app-specific password rotation as part of calendar maintenance.

Connect Apple Calendar

Create or confirm an Apple app-specific password.
Open Settings > Apps.
Choose Apple Calendar.
Enter your Apple ID.
Enter the app-specific password.
Save the connection.
Run sync if the action is available.

What Syncs

Apple Calendar is configured for bidirectional calendar and event sync when the connection is active.

Use it for scheduling conflict checks, appointment writeback, and keeping Agiled appointments aligned with the Apple calendar account where supported.

Choose the Apple calendar account that actually owns the availability you want Agiled to respect. If your team uses a shared calendar, confirm that the Apple ID has access to that calendar before connecting it.

Before Connecting

Confirm the Apple Account has two-factor authentication enabled.
Generate a dedicated app-specific password for Agiled.
Confirm you are connecting the Apple Account that owns the calendar.
Store the app-specific password securely; Apple only shows it when it is created.

If you change or reset the Apple Account password, Apple may revoke existing app-specific passwords. Generate a new one and update the connection in Agiled.

Do not reuse the same app-specific password across multiple tools. A dedicated password makes it easier to revoke Agiled access without disrupting other calendar or email integrations.

Test the Connection

Save the Apple Calendar connection.
Run sync if available.
Create a safe test appointment from a booking page.
Confirm the appointment appears in Agiled.
Confirm the event appears on the Apple calendar.
Cancel or reschedule the test appointment and confirm the calendar reflects the change where supported.

If the test event appears on the wrong calendar, review the connected Apple ID and default calendar selection. If the event does not appear at all, generate a new app-specific password, reconnect, then run one small sync test before booking real customers.

Also create a busy test event in Apple Calendar and confirm Agiled no longer offers that slot on the booking page. Writeback and conflict checking should both be tested.

Choose the Calendar Scope

Decide which Apple calendar should receive Agiled appointments and which calendar should be checked for conflicts. Some teams use one calendar for customer meetings and another for internal focus time. If both affect availability, make sure the connected account exposes both calendars and that busy events are marked correctly.

Use a short test event name such as Agiled calendar test so it is easy to find and remove from Apple Calendar after verification. Avoid testing with a real customer appointment until the owner, write calendar, timezone, and conflict checks are confirmed.

Ongoing Maintenance

Review the connection after Apple password changes, device security changes, calendar ownership changes, or recurring sync failures. Calendar problems often show up as missing availability or duplicate events, so compare Agiled appointments with Apple Calendar before editing booking-page rules.

If a teammate leaves or changes role, review whether their Apple Calendar connection still owns any booking pages or event types.

After replacing an app-specific password, revoke the old password in Apple ID settings. App-specific passwords should be treated like credentials: do not share them in chat, tickets, or documents, and do not reuse the same password for multiple tools.

Apple Calendar