Agent Forge

Zoom

Manage Zoom meetings, registrants, recordings, and past meeting data

Zoom helps teams schedule meetings, register attendees, record sessions, and track what happened after a call. In Agent Forge, the Zoom block is focused on workflow-friendly meeting automation rather than broad account administration.

With Zoom in Agent Forge, you can:

  • create, read, update, and delete meetings
  • inspect your connected Zoom profile and list your meetings
  • add and inspect meeting registrants
  • list recordings and fetch recording details
  • read past meeting details and participants
  • trigger workflows from Zoom webhook events such as meeting.started, meeting.ended, and recording.completed

Usage Instructions

Use the Zoom block when you want a workflow step or agent tool to call the Zoom REST API with a connected user OAuth credential.

Authentication

  • Connect a Zoom account through the credential field.
  • The Zoom integration uses user OAuth only in v1.
  • Agent Forge requests granular Zoom scopes for user-owned meeting workflows, registrants, past-meeting reads, and cloud recordings.

Request Model

  • Read operations use direct fields such as userId, meetingId, pageSize, nextPageToken, from, and to.
  • create_meeting uses form fields such as topic, start time, duration, recording preference, and waiting room settings.
  • add_meeting_registrant uses normal attendee fields like email and name.
  • update_meeting still uses the payload field as an advanced escape hatch for raw Zoom JSON.
  • For most user-scoped operations, leaving userId blank defaults to me.

Good Fit

Use Zoom when you want to:

  • spin up meetings from CRM or scheduling workflows
  • register attendees from forms, tickets, or onboarding flows
  • inspect recordings after a call finishes
  • build follow-up automations when meetings start, end, or recordings complete

Supported Operations

Users

  • zoom_get_current_user

Meetings

  • zoom_create_meeting
  • zoom_get_meeting
  • zoom_list_user_meetings
  • zoom_update_meeting
  • zoom_delete_meeting

Registrants

  • zoom_add_meeting_registrant
  • zoom_list_meeting_registrants

Recordings

  • zoom_list_recordings
  • zoom_get_recording

Past Meetings

  • zoom_get_past_meeting_details
  • zoom_list_past_meeting_participants

Common Inputs

  • credential: connected Zoom OAuth account
  • userId: Zoom user ID or email address, defaults to me for user-scoped actions
  • meetingId: Zoom meeting ID or UUID
  • topic: meeting title for create_meeting
  • startTime: meeting start time, chosen in the UI and converted to ISO automatically
  • duration: meeting duration in minutes
  • registrantEmail, registrantFirstName, registrantLastName: attendee fields for add_meeting_registrant
  • pageSize: page size for Zoom list endpoints
  • nextPageToken: pagination token from a prior response
  • from / to: optional recording date range in YYYY-MM-DD
  • payload: advanced raw JSON request body for update_meeting

Example Inputs

Create a meeting

  • Topic: Customer onboarding call
  • Start Time: 2026-05-20T14:00:00Z
  • Duration: 45
  • Timezone: UTC
  • Agenda: Kickoff and implementation review
  • Host Video On: true
  • Participant Video On: true
  • Waiting Room: true
  • Registration Approval: Approve Automatically

Add a registrant

  • Registrant Email: attendee@example.com
  • First Name: Jordan
  • Last Name: Lee

Trigger Support

Zoom webhooks are available through the webhook trigger surface and are designed for the most automation-relevant events:

  • meeting.started
  • meeting.ended
  • recording.completed

Setup Notes

  • Enable Event Subscriptions in your Zoom app.
  • Paste the generated Forge webhook URL into Zoom.
  • Paste your Zoom Secret Token into the webhook configuration token field so Forge can verify x-zm-signature headers.
  • Forge automatically handles Zoom's endpoint.url_validation challenge when the secret token is configured.

Notes

  • Category: tools
  • Type: zoom
  • The Zoom block is intentionally scoped to user-owned meeting workflows in v1.
  • Account-wide admin operations such as listing all users are intentionally excluded from this granular-scope release.