Appearance
Zoom
Manage meetings, webinars, and users with the Zoom API. Schedule meetings, manage participants, and access recordings.
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.zoom.us/v2 |
| Authentication | OAuth2 |
| Endpoints | 7 |
| Connector key | zoom |
Using Zoom in a workflow
- Go to Connections and click New Connection.
- Pick Zoom from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /users | List users |
GET /users/{userId} | Get a user |
POST /users/{userId}/meetings | Create a meeting |
GET /users/{userId}/meetings | List meetings for a user |
GET /meetings/{meetingId} | Get meeting details |
DELETE /meetings/{meetingId} | Delete a meeting |
GET /meetings/{meetingId}/recordings | Get meeting recordings |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /users
List users
| Detail | Value |
|---|---|
| Operation ID | comm.listUsers |
| Method | GET |
| Path | /users |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
page_size | query | integer | No |
page_number | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.listUsers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
GET /users/{userId}
Get a user
| Detail | Value |
|---|---|
| Operation ID | comm.getUser |
| Method | GET |
| Path | /users/{userId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
userId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.getUser. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
POST /users/{userId}/meetings
Create a meeting
| Detail | Value |
|---|---|
| Operation ID | comm.createMeeting |
| Method | POST |
| Path | /users/{userId}/meetings |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
userId | path | string | Yes |
Request Body
| Field | Type |
|---|---|
topic | string |
type | integer |
start_time | string |
duration | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.createMeeting. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
GET /users/{userId}/meetings
List meetings for a user
| Detail | Value |
|---|---|
| Operation ID | comm.listMeetings |
| Method | GET |
| Path | /users/{userId}/meetings |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
userId | path | string | Yes |
type | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.listMeetings. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
GET /meetings/{meetingId}
Get meeting details
| Detail | Value |
|---|---|
| Operation ID | comm.getMeeting |
| Method | GET |
| Path | /meetings/{meetingId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
meetingId | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.getMeeting. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
DELETE /meetings/{meetingId}
Delete a meeting
| Detail | Value |
|---|---|
| Operation ID | comm.deleteMeeting |
| Method | DELETE |
| Path | /meetings/{meetingId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
meetingId | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.deleteMeeting. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.
GET /meetings/{meetingId}/recordings
Get meeting recordings
| Detail | Value |
|---|---|
| Operation ID | comm.getRecordings |
| Method | GET |
| Path | /meetings/{meetingId}/recordings |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
meetingId | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zoom connection from the Connection dropdown.
- In the Operation dropdown, select
comm.getRecordings. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zoom API reference.