List Recordings: 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
From Date from	date	Optional	Start date (YYYY-MM-DD)
To Date to	date	Optional	End date (YYYY-MM-DD)

Sample request

{
  "from": "{{trigger.from}}",
  "to": "{{trigger.to}}"
}

Returns

{
  "meetings": [
    {
      "topic": "Weekly Standup",
      "duration": 30,
      "start_time": "2026-04-11T14:00:00Z",
      "recording_count": 2,
      "recording_files": [
        {
          "file_size": 52428800,
          "file_type": "MP4",
          "download_url": "https://zoom.us/rec/..."
        }
      ]
    }
  ]
}

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

FAQ

Questions about List Recordings.

What does the List Recordings action do in Zoom?

Lists cloud recordings for the authenticated user with download URLs. Use to mirror recordings into S3/Drive, transcribe, or generate AI summaries.

What inputs does List Recordings require?

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

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