Zoom Tools

The Zoom tools let a workflow create and inspect Zoom meetings and look up users on a Zoom account. Use them when a workflow needs to schedule a meeting, fetch a meeting's join details, or enumerate meetings and users for an account.

Overview

All requests authenticate against https://api.zoom.us/v2 using Authorization: Bearer <token>. The token is supplied via the apiKey parameter and must be a valid Zoom OAuth access token.

Operations

Configuration

zoom_list_meetings

GET https://api.zoom.us/v2/users/{userId}/meetings

zoom_create_meeting

POST https://api.zoom.us/v2/users/{userId}/meetings

zoom_get_meeting

GET https://api.zoom.us/v2/meetings/{meetingId}

zoom_list_users

GET https://api.zoom.us/v2/users

Outputs

zoom_list_meetings

• data (json) — Array of Zoom meeting objects.
• metadata (json) — List metadata:
  • count (number) — Number of items returned.
  • total_records (number) — Total number of records available.

zoom_create_meeting

• data (json) — The created Zoom meeting object.
• metadata (json) — Meeting identifiers:
  • id (string) — Meeting ID.
  • topic (string) — Meeting topic.

zoom_get_meeting

• data (json) — The Zoom meeting object.
• metadata (json) — Meeting identifiers:
  • id (string) — Meeting ID.
  • topic (string) — Meeting topic.

zoom_list_users

• data (json) — Array of Zoom user objects.
• metadata (json) — List metadata:
  • count (number) — Number of items returned.
  • total_records (number) — Total number of records available.

YAML Example

zoom_1:
  type: zoom
  name: "Zoom"
  inputs:
    operation: "zoom_create_meeting"
    userId: "me"
    topic: "Weekly Team Standup"
    type: 2
    start_time: "2025-06-03T10:00:00Z"
    duration: 60
    timezone: "America/Los_Angeles"
    apiKey: "{{ZOOM_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth setup: apiKey must be a Zoom OAuth access token, not an API key/secret pair. Create a Server-to-Server OAuth or OAuth app in the Zoom Marketplace, mint an access token, and pass it as apiKey. The token is sent as a Bearer credential, so it needs the relevant meeting:read/meeting:write and user:read scopes for the operations you call.
• Default user: userId defaults to me (the authenticated user) for zoom_list_meetings and zoom_create_meeting. Pass an email or Zoom user ID to act on behalf of another account user.
• Chaining: The created meeting's join details live in data — reference them downstream with {{zoom_1.data.join_url}} or grab the id from {{zoom_1.metadata.id}} to feed a later zoom_get_meeting step.
• Paging: page_size accepts 1-300; Zoom returns total_records in metadata so you can detect when more records exist than were returned.