Update Registrant Status
zoom.update_registrant_status
ActionChat & messagingconnection required
Calls the Zoom API with the connection's credentials.
Approve, deny or cancel meeting registrants in bulk.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Zoom
- Secret shape
- {"account_id", "client_id", "client_secret"} — Server-to-Server OAuth
- Config it needs
- account_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
meeting_id The meeting number, as a string — an int64 read as a number loses digits. The spaced form Zoom's UI shows ('812 3456 7890') is accepted. | string | Yes | — | — | 81234567890 |
action approve lets them in, deny blocks them, cancel revokes an approval. | string | No | approve | one of "approve", "deny", "cancel" | — |
registrant_ids Registrant ids to act on — the 'registrant_id' Add Registrant returned. A JSON array or a comma-separated list. | array | No | — | ≥ 1 characters; array of string | ["cO_Uz9jTQwmVQ1sSlKPHUQ"] |
registrant_emails Registrant email addresses to act on, when you do not hold their ids. A JSON array or a comma-separated list. | array | No | — | ≥ 1 characters; array of string | — |
occurrence_id One occurrence of a recurring meeting. Leave blank to act on the series. | string | No | — | — | — |
- At least one of registrant_ids, registrant_emails must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"action": "approve",
"meeting_id": "81234567890",
"registrant_ids": [
"cO_Uz9jTQwmVQ1sSlKPHUQ"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Zoom accepted the change. | boolean | true |
action The action that was applied. | string | — |
count How many registrants were sent. | number | — |
{
"action": "",
"count": 0,
"ok": true
}Notes
- Zoom takes at most 30 registrants per call; a longer list is refused with a 400, so split a bigger approval queue upstream.
- Zoom answers 204 with no body — it does not report which registrants matched, so an id that does not exist fails silently. Read them back with List Registrants.
- Approving sends Zoom's confirmation email with the personal join link.
See Update Registrant Status run in a workflow.
In a technical demo we add the Zoom connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.