Which Calendly events can n8n react to?

The Calendly Trigger fires on Event Created and Event Canceled (invitee.created and invitee.canceled), scoped to the organization or a user.

Why does the trigger not fire for events in my Google Calendar?

It only sees bookings made through Calendly. Events created directly in Google Calendar or Outlook never reach Calendly's webhooks.

Do I need a paid Calendly plan?

Yes. The n8n docs note that Calendly webhooks are only available on paid plans, and the trigger depends on them. The current trigger version also needs an OAuth2 credential; a Personal Access Token works only with version 1.

What about Pipedream's Calendly actions?

n8n has no Calendly action node. List Events, Get Event, Cancel Event and the invitee actions become HTTP Request calls to the Calendly API v2.

Pipedream Calendly steps in n8n

Updated 2026-10-21 · 2 min read · n8n: Calendly Trigger (Native n8n node)

Calendly workflows on Pipedream start with a booking: a new invitee is added to a CRM, gets a Zoom link or a Slack ping, a cancellation updates the deal. n8n covers the start with the Calendly Trigger; Pipedream's Calendly actions become HTTP requests.

The n8n side

Calendly Trigger (n8n-nodes-base.calendlyTrigger, version 2 by default): webhook-based.

Scope: Organization or User.
Events: Event Created (invitee.created), Event Canceled (invitee.canceled).

The payload contains the invitee (name, email, answers to questions), the scheduled event URI and tracking (UTM) data.

n8n has no Calendly action node.

What maps where

Pipedream (app `calendly_v2`)	In n8n	Status
New Invitee Created (source)	Calendly Trigger, Event Created	manual, 1 node
New Invitee Canceled (source)	Calendly Trigger, Event Canceled	manual, 1 node
New Event Scheduled (source)	Calendly Trigger, Event Created + HTTP Request for event details	manual
New Routing Form Submission Created	Calendly webhook `routing_form_submission.created` → n8n Webhook	manual
List Events, Get Event	HTTP Request → `/scheduled_events`	manual
Cancel Event	HTTP Request → `POST /scheduled_events/{uuid}/cancellation`	manual
List Event Invitees, Get Event Invitee	HTTP Request → invitees endpoints	manual
Create a Scheduling Link	HTTP Request → `/scheduling_links`	manual
Create Invitee No Show	HTTP Request → `/invitee_no_shows`	manual

Calendly is not in the converter's mapped list: the trigger becomes a Manual Trigger with a note naming the source, and actions arrive as placeholders with their props.

Calendly credentials in n8n

The n8n docs describe two options:

Personal Access Token: Calendly → Integrations → API and webhooks.
OAuth2: an app in the Calendly developer portal with scopes users:read, webhooks:read, webhooks:write, scheduled_events:read.

The current trigger (version 2) accepts only OAuth2; a Personal Access Token works only with the older version 1 of the trigger. HTTP Request nodes can use either credential for API calls.

Typical migration: booking to HubSpot

Pipedream: Calendly New Invitee Created → HubSpot create or update contact → Slack message. n8n: Calendly Trigger (Event Created) → HubSpot → Contact → Create or Update (email, name, answers) → Slack → Message → Send.

Calendly migration pitfalls

Public HTTPS URL. Calendly only delivers to public HTTPS endpoints. When testing a local n8n, use a tunnel (ngrok, Cloudflare Tunnel).
Reschedules arrive as a cancel plus a new booking; check the rescheduled flag before marking a deal lost.
Webhook subscriptions. Pipedream's sources created subscriptions in Calendly; delete them (HTTP Request GET /webhook_subscriptions, then DELETE) so events are not handled twice.
Paid plan. On a free Calendly plan the trigger cannot register.

How to move your Calendly workflows

Export from Pipedream.
Upload on /convert; the free report lists the Calendly trigger and every action with its props.
Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the webhook guide. Related: Zoom, Google Calendar, HubSpot.

FAQ

Which Calendly events can n8n react to?: The Calendly Trigger fires on Event Created and Event Canceled (invitee.created and invitee.canceled), scoped to the organization or a user.
Why does the trigger not fire for events in my Google Calendar?: It only sees bookings made through Calendly. Events created directly in Google Calendar or Outlook never reach Calendly's webhooks.
Do I need a paid Calendly plan?: Yes. The n8n docs note that Calendly webhooks are only available on paid plans, and the trigger depends on them. The current trigger version also needs an OAuth2 credential; a Personal Access Token works only with version 1.
What about Pipedream's Calendly actions?: n8n has no Calendly action node. List Events, Get Event, Cancel Event and the invitee actions become HTTP Request calls to the Calendly API v2.