List Meetings: 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 Type type	options	Optional	Meeting Type. Options: Upcoming, Previous (last 30 days), Scheduled
Page Size page_size	string	Optional	Page Size. e.g. "30"

Sample request

{
  "type": "{{trigger.type}}",
  "page_size": "30"
}

Returns

{
  "meetings": [
    {
      "id": 123,
      "topic": "Team Sync",
      "duration": 30,
      "join_url": "https://zoom.us/j/123",
      "start_time": "2025-01-20T10:00:00Z"
    }
  ],
  "total_records": 5
}

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

FAQ

Questions about List Meetings.

What does the List Meetings action do in Zoom?

Lists upcoming, live, and past Zoom meetings for the authenticated user. Used for daily agenda emails or for prep-doc generation.

What inputs does List Meetings require?

List Meetings has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Meetings support batch operations?

Yes. Run List Meetings 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