Pipedream Calendly → n8n

3 Pipedream Calendly actions and 7 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slugs: calendlycalendly_v2.

Actions

Pipedream action	n8n	Fit	Notes
calendly_v2-create-scheduling-link	Http Request	Check output	No n8n Calendly action node (only Calendly Trigger) -> HTTP Request. PD actually sends max_event_count/owner/owner_type as QUERY params on POST /scheduling_links; the template sends them as the documented JSON body. calendlyOAuth2Api has a fixed hidden scope…
calendly_v2-list-events	Http Request	Check output	HTTP Request fallback to the exact endpoint (GET https://api.calendly.com/scheduled_events). PD throws if more than one of organization/user/group is set.
calendly_v2-get-event	Http Request	Check output	HTTP Request fallback, exact endpoint GET /scheduled_events/{uuid}; scheduled_events:read is in the n8n OAuth scope.

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
calendly-invitee-created	Calendly Trigger	Check output	App `calendly` (API key, v1 API) was removed from the registry 2023-11-01 (commit e9828d81 'Calendly deprecation'); the Calendly v1 API is sunset. v1 hooks were user-level -> scope 'user'. PD deduped on event.uuid+invitee.uuid.
calendly-invitee-canceled	Calendly Trigger	Check output	Removed app `calendly` (2023-11-01). See calendly-invitee-created.
calendly-new-event	Calendly Trigger	Partial	Polling source of the removed `calendly` app. Approximated with the webhook Calendly Trigger (invitee.created; one execution per invitee, no backfill). Alternative: Schedule Trigger + HTTP Request GET https://api.calendly.com/scheduled_events + Remove…
calendly_v2-invitee-created	Calendly Trigger	Direct	Both create a webhook_subscription (scope 'user'\|'organization', same option values) and verify the Calendly-Webhook-Signature. n8n Calendly Trigger v2 only supports calendlyOAuth2Api and requires an https:// webhook URL. PD dedupes on…
calendly_v2-invitee-canceled	Calendly Trigger	Direct	Both create a webhook_subscription (scope 'user'\|'organization', same option values) and verify the Calendly-Webhook-Signature. n8n Calendly Trigger v2 only supports calendlyOAuth2Api and requires an https:// webhook URL. PD dedupes on…
calendly_v2-new-event-scheduled	Calendly Trigger	Check output	PD source is POLLING (GET /scheduled_events on a timer, sort created_at:desc, emits recent events on first run); n8n has no polling Calendly node, so the closest equivalent is the webhook Calendly Trigger on invitee.created. Differences: n8n fires once per…
calendly_v2-routing-form-submission-created	Schedule Trigger + polling	Partial	n8n Calendly Trigger only offers invitee.created / invitee.canceled. Options: Webhook node (n8n-nodes-base.webhook) + a one-off HTTP Request POST https://api.calendly.com/webhook_subscriptions {url, events:['routing_form_submission.created'], organization,…

Credentials

Create a Calendly credential in n8n (type calendlyOAuth2Api). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a Calendly node?+

Not for these actions. They map to n8n's HTTP Request node, which calls the same Calendly API with an n8n credential.

Will my Pipedream Calendly connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Calendly credential in n8n (type calendlyOAuth2Api) and select it on the converted nodes.

Are Pipedream Calendly triggers supported in n8n?+

6 of the 7 Pipedream Calendly event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the Calendly API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana ClickUp Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini Google Sheets All apps →