Pipedream Zoom → n8n
4 Pipedream Zoom actions and 3 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 slug: zoom.
Actions
| Pipedream action | n8n | Fit |
|---|---|---|
| zoom-create-meeting | Zoom meeting → create | Check output |
| zoom-get-meeting-details | Zoom meeting → get | Direct |
| zoom-list-meetings | Zoom meeting → getAll | Check output |
| zoom-add-meeting-registrant | Http Request | Check output |
Triggers (event sources)
| Pipedream trigger | n8n | Fit |
|---|---|---|
| zoom-meeting-started | Schedule Trigger + polling | Partial |
| zoom-meeting-ended | Schedule Trigger + polling | Partial |
| zoom-recording-completed | Schedule Trigger + polling | Partial |
Credentials
Create a Zoom credential in n8n (type zoomOAuth2Api). 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 Zoom node?+
Yes. 3 of the 4 Pipedream Zoom actions listed here map to a native n8n node; 1 map to n8n's HTTP Request node with the Zoom credential.
Will my Pipedream Zoom connection move to n8n?+
No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Zoom credential in n8n (type zoomOAuth2Api) and select it on the converted nodes.
Are Pipedream Zoom triggers supported in n8n?+
n8n has no trigger node for these Zoom events. Converted workflows use a Schedule Trigger that polls the API, or a Webhook node registered in Zoom.
What happens to code steps that call the Zoom 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.