Get Meeting: Zoom action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Meeting ID meetingId	string	Required	Meeting ID. Example: 85746065

Sample request

{
  "meetingId": "e.g. 85746065"
}

Returns

{
  "id": 85746065,
  "type": 2,
  "topic": "Weekly Standup",
  "status": "waiting",
  "duration": 30,
  "join_url": "https://zoom.us/j/85746065",
  "timezone": "America/New_York",
  "start_time": "2026-04-11T14:00:00Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Meeting.

What does the Get Meeting action do in Zoom?

Returns details of a specific Zoom meeting: topic, start time, duration, agenda, join_url, and recording info. The standard read after a trigger fires with a meeting ID.

What inputs does Get Meeting require?

Required: Meeting ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Zoom returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Meeting support batch operations?

Yes. Run Get Meeting inside a Loop node to process arrays. Tiny Command handles Zoom's rate limits automatically so you don't have to throttle manually.

More actions