Calendly automations
Productivity · 11 integrations
Scheduling automation with Calendly typically focuses on syncing new bookings into CRMs, triggering follow-up sequences on cancellations, and routing form submissions to the right sales rep or workflow. Most teams automate Calendly because manually copying invitee data into Pipedrive, HubSpot, or Salesforce after every call is error-prone and slow. Choosing the right platform matters because Calendly's webhook and API constraints behave differently across Zapier, Make, n8n, Power Automate, and Pipedream.
What it costs to automate Calendly
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Calendly integrations
Each page compares all five platforms for that pair.
Calendly triggers & actions by platform
Which capabilities each platform supports for Calendly.
| Capability | Zapier | Make | n8n | Pipedream | Power Automate |
|---|---|---|---|---|---|
| Triggers | |||||
| Event Cancelled | ✓ | ✓ | ✓ | ✓ | — |
| Event Created | ✓ | ✓ | ✓ | ✓ | — |
| Invitee Canceled | ✓ | — | ✓ | ✓ | ✓ |
| Invitee Created | ✓ | — | ✓ | ✓ | ✓ |
| Event Canceled | ✓ | — | ✓ | ✓ | — |
| HTTP Webhook | — | ✓ | — | — | ✓ |
| New Event Scheduled | ✓ | — | — | ✓ | — |
| Schedule Trigger | — | ✓ | ✓ | — | — |
| Calendly Event Canceled | ✓ | — | — | — | — |
| Calendly Trigger | — | — | ✓ | — | — |
| Actions | |||||
| Create Customer | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create Invoice | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create Contact | ✓ | ✓ | ✓ | ✓ | — |
| Create Draft Order | ✓ | ✓ | — | ✓ | — |
| Create Record | ✓ | ✓ | ✓ | — | — |
| HTTP Request | — | ✓ | ✓ | — | ✓ |
| Update Record | ✓ | ✓ | ✓ | — | — |
| Add Contact to Sequence | — | ✓ | — | ✓ | — |
| Create a Customer | — | ✓ | — | — | ✓ |
| Create Deal | ✓ | ✓ | — | — | — |
Things to know about automating Calendly
Webhooks Require Paid Plan
Real-time triggers via webhooks are only available on Calendly's Standard plan ($10/user/month) or higher — free accounts cannot use webhooks at all. This affects every platform: Zapier, Make, n8n, Power Automate, and Pipedream will all fail to register a webhook subscription on a free Calendly account.
Three Webhook Events Only
Calendly supports exactly three webhook event types: invitee.created, invitee.canceled, and routing_form_submission.created. Reschedules are not a separate event — Calendly fires an invitee.canceled followed by a new invitee.created, so any automation handling reschedules must explicitly account for both triggers to avoid duplicate or missing records.
Webhooks Disable Silently
If your endpoint fails to return a 2xx response within 10 seconds, Calendly retries up to 25 times with exponential backoff over 24 hours — after which the webhook is permanently disabled with no alert sent to you. The only way to detect a dead webhook is to manually poll the /webhook_subscriptions endpoint and check the status field.
Rate Limit: 60 Requests/Minute
Non-Enterprise plans are capped at 60 API requests per minute; Enterprise doubles this to 120. Pagination is cursor-based with a maximum page size of 100 records, meaning any bulk data pull against a large organization will exhaust rate limits quickly across polling-heavy platforms like Power Automate or n8n using HTTP Request nodes.
n8n Node Uses Deprecated V1 Endpoints
As of August 27, 2025, Calendly's V1 API is permanently shut down, but n8n's built-in Calendly node still routes webhook registration to the v1 /hooks endpoint and sends the deprecated X-TOKEN auth header instead of Authorization: Bearer. Teams using n8n should replace the native node with HTTP Request nodes pointed at the V2 API and authenticate with a Personal Access Token as a Bearer token.
New Scheduling API Enables Direct Booking
A newly released Scheduling API with a Create Event Invitee endpoint allows booking Calendly meetings programmatically without iframes, redirects, or the Calendly-hosted UI. This resolves a long-standing limitation and opens the door to conversational AI booking flows and native in-app scheduling on any platform that supports HTTP requests, including Pipedream, Make, and n8n.
What breaks at scale
At 60 requests per minute on Free, Standard, or Teams plans, a single automation that polls List Scheduled Events and then fetches full invitee detail records for each result will exhaust your rate limit in seconds during busy booking windows. Calendly returns HTTP 429 with a Retry-After header, but platforms like Make and Power Automate will not automatically honor that header without custom error-handling logic, causing cascading failures that can fall back to polling loops and make the problem worse. Enterprise at 120 req/min buys headroom but does not eliminate the problem for large organizations pulling paginated data across hundreds of events.
Calendly permanently disables a webhook after 25 failed delivery attempts or 24 hours of endpoint failures — and sends you no notification when this happens. If your receiving endpoint has a deployment window, a timeout spike, or a misconfigured SSL certificate, your entire booking-to-CRM pipeline silently stops working and you will not find out until a rep notices a missing contact in Salesforce or HubSpot days later. The only mitigation is a daily polling job against the /webhook_subscriptions endpoint checking for a non-active status field, which itself consumes rate limit budget and must be built manually on every platform including Zapier, Make, n8n, Power Automate, and Pipedream.
Cursor-based pagination caps out at 100 records per request, and there are no bulk endpoints — pulling membership data for a 500-person organization requires at minimum 5 sequential API calls, each counting against the 60 req/min quota. Simultaneously, user creation via the REST API is invitation-only: POST /organizations/{uuid}/invitations sends an email but leaves the user inactive until they manually accept, making immediate automated provisioning impossible without SCIM, which itself requires an Enterprise contract (minimum ~$15,000/year, 30+ users) and an active SSO configuration on Okta, Entra ID, or OneLogin — Google Workspace is explicitly not supported as a SCIM identity provider.
Frequently asked questions
How do I automate Calendly with a CRM like HubSpot or Salesforce?
The standard approach is to use a webhook trigger on invitee.created to fire whenever a meeting is booked, then pass the invitee data to your CRM via a subsequent action step. Zapier and Make have native Calendly triggers that handle this out of the box, while n8n, Power Automate, and Pipedream require you to configure a webhook listener and use HTTP Request nodes to call the Calendly V2 API for additional invitee details. All platforms require at least a Calendly Standard plan ($10/user/month) for webhook access.
Why is my Zapier Calendly integration not working on a free account?
Zapier's Calendly integration relies on webhook subscriptions, which Calendly restricts to paid plans (Standard or higher). Free Calendly accounts will produce a 'Problem creating Webhook Subscription' error when you try to activate a Zap. Upgrading to Calendly Standard at $10/user/month resolves this, and the same plan requirement applies if you switch to Make, n8n, Power Automate, or Pipedream.
Does n8n work with the Calendly API in 2025?
n8n's built-in Calendly node has a known compatibility issue: it targets Calendly's V1 API endpoints and uses the deprecated X-TOKEN authentication header, both of which stopped working when Calendly permanently shut down V1 on August 27, 2025. The recommended workaround is to bypass the native node entirely and use n8n's HTTP Request node with the V2 API base URL and a Personal Access Token passed as a Bearer token — the same manual approach required in Make and Power Automate for advanced Calendly operations.
Can Calendly automations handle rescheduled meetings correctly?
Calendly does not emit a dedicated rescheduled event — instead, it fires an invitee.canceled event for the original booking immediately followed by an invitee.created event for the new time. Any automation built on Zapier, Make, n8n, Power Automate, or Pipedream must subscribe to both event types and include logic to correlate the cancellation with the new booking (typically via a shared invitee email or event UUID) to avoid incorrectly marking a rescheduled meeting as a lost lead.