Zoom · New recording starts a run for each meeting's cloud recording once Zoom has processed it. It checks on a schedule — every 5 minutes on paid plans, every 15 on Free — through your Zoom connection, which is a Server-to-Server app of your own.

Instant triggers — Meeting started, Meeting ended, Recording completed, New registrant and Participant joined, where Zoom tells Bizomate the moment it happens — come later, with Sign in with Zoom, once Bizomate's own Zoom app is published. Until then New recording is Zoom's only trigger.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

Before you start

A Zoom connection. See Connect Zoom. Cloud recording needs a paid Zoom plan.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under Zoom, select New recording.
  3. In Connection, choose your Zoom connection.
  4. Optional: in Host, give one user's email or Zoom user id to watch only their recordings. Left empty, it watches every user in the Zoom account who can record to the cloud.
  5. Under Checks, choose Every 5 minutes or Every 15 minutes, then open Output and select Fetch a sample.
  6. Add the steps — Get a recording with {{ $json.uuid }} fetches the files — then Publish.

What the trigger gives

Field
meetingId, uuid, topic, start, duration The meeting, and this recording's own id — Get a recording takes it.
count, files How many files the recording has, and each one's name, type (video, audio, transcript, captions, chat …) and size. The files themselves are not fetched; add Get a recording.
shareUrl The recording's page in Zoom.

What happens next

  • The first check after publishing only notes the recordings already there, so they never start a run.
  • A recording starts its run once every file is processed — one run per recording, never twice.
  • Up to 100 new recordings start runs in one check; the rest wait for the next check, in order. A check that finds nothing starts no run and costs nothing.
  • The trigger's Settings show what it is doing: Checking every 5 minutes — Last checked 10:45 · next 10:50, and Recent checks — Nothing new, or 2 found · 2 runs.
  • Every 5 minutes is for paid plans. On Free it checks every 15 minutes whatever is chosen.

Good to know

  • Each check asks Zoom once for each user it watches. In a large Zoom account, give a Host to watch only the user whose recordings matter.
  • When Zoom says the account's daily allowance of requests is used, the checks pause until it resets — usually midnight UTC — and then carry on from where they stopped, so nothing is missed. The paused checks show in Recent checks as finding nothing.
  • Runs count in the month's allowance.

If something goes wrong

What you see Why What to do
Not checking since 10:45 with Zoom refused: … The Zoom app was deactivated, or lacks the users or recordings scope. Fix the app, then Check now. See When an app trigger stops checking.
Fetch a sample says Nothing matches yet No cloud recording in the last 30 days — Fetch a sample looks through up to 50 users. Record a short test meeting to the cloud, wait for Zoom to process it, and fetch again.