What makes Calendly easy or hard to automate
Calendly turns scheduling into clean events. Each booking has an event type, a host, a start time, the invitee’s name and email, their answers to your booking questions, and UTM parameters if the link carried them. Webhook subscriptions push invitee.created and invitee.canceled events within seconds, and routing forms have their own submission event.
The v2 API is consistent and well documented. Most resources are referenced by URI, so a webhook payload often points to the scheduled event rather than including every detail, and your workflow makes one follow-up call to fetch location, meeting link or host information.
The hard parts are permissions and plans. Webhooks need a paid plan, and the scope of a subscription depends on who created the token. Teams often discover that a webhook built with one rep’s token never fires for anyone else.
The AI layer
A booked meeting is a signal of intent. AI helps you act on it before and after the call:
- Before the meeting. A model combines booking answers, company information and CRM history into a short brief: who this is, what they said they need and what to ask.
- Routing. Routing form answers can be scored against your criteria, so strong prospects reach an account executive and others get a self-serve path.
- After the meeting. Paired with a call recorder, a model writes the CRM note, the action items and a draft follow-up for the host.
The booking itself stays in Calendly. AI never invents availability or moves meetings without the host’s say.
Limits to plan around
- Plan gating. Webhook subscriptions require a paid plan on the subscribing account. Some endpoints, such as data deletion and activity logs, are Enterprise-only.
- Token scope. User-level tokens see only that user. Use an admin or owner token for organization-scoped subscriptions, and store it as a service credential, not one person’s.
- Signature checks. Create subscriptions with a signing key and verify the signature header on each delivery.
- Public URLs. Callback URLs must be reachable from the internet and should use HTTPS, so local testing needs a tunnel.
- Reschedules and duplicates. A reschedule arrives as a cancel plus a new booking. Deduplicate on the invitee email and event, and handle out-of-order deliveries.
How Lumeor typically connects it
We subscribe to Calendly webhooks at the organization level, receive them in n8n, fetch the event details, and run an LLM step for briefs or qualification. Results go to HubSpot or Salesforce and to the host in Slack before the call. The meeting notes to CRM guide covers the after-call half. Practices that need intake forms, packages and HIPAA options often fit Acuity Scheduling better, and agent-led booking usually runs against Google Calendar directly.