Calendly
Calendly organizes scheduling around users, organizations, event types, and scheduled events. URIs (not UUIDs) identify resources. Resolve the current user first to obtain user_uri and organization_uri for most operations.
Data Model
- Current user — returns user_uri and organization_uri anchors for nearly every subsequent step.
- Event types — templates (duration, location, questions) that generate booking links.
- Availability — combines host busy blocks with event-type rules; requires the event type’s canonical URI.
- Scheduled events — confirmed meetings plus invitee rosters.
- Availability schedules — weekly rules describing when hosts accept meetings.
- Routing forms — questionnaires that map respondents to the right event type; submissions are queryable for automation.
- Webhooks — subscriptions for lifecycle topics such as event.booked and event.canceled.
Gotchas
- URIs, not bare UUIDs: Copy full resource URI strings from listing responses into follow-up parameters — never pass bare UUIDs alone.
- Organization scope: Org-level operations need the current_organization payload from the authenticated user profile response.
- Activity log: Enterprise-only; expect 403s on smaller plans.
- Availability prerequisites: Never compute open slots without first selecting an event type URI from the catalog response.
- Recurring vs one-off event types use different create shapes: Standard event types require owner (user URI) and duration (minutes). One-off event types require host (user URI), duration, and date_setting — do not swap owner/host between them. color on create/update must be #RRGGBB hex.
- Event type description writes: Create and update bodies use Calendly field description (plain string). Tools accept description_plain or description_html and map to description upstream; read responses still expose description_plain / description_html.
- Booking page vs org branding: Event type API can set name, color, description, locations, and custom questions. Organization logo, profile photo, and Admin Center brand colors are UI-only — not available on the scheduling API.
- Enterprise-only reads: Activity log and outgoing communications return HTTP 403 on non-Enterprise plans — the tool answers {available: false, reason: calendly_enterprise_required}; not a broken credential.
- Pattern A reads: Omit resource ids on list-style read tools to list; pass an id from a prior row to fetch one resource.
