Add Meeting Registrant
zoom.add_registrant
ActionChat & messagingconnection required
Calls the Zoom API with the connection's credentials.
Register somebody for a meeting and get their personal join link.
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
11 fields, 3 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 |
email The registrant's email address. Supports {{ }}. | string | Yes | — | ≤ 128 characters; email format | — |
first_name The registrant's first name — Zoom requires it. | string | Yes | — | ≤ 64 characters | — |
last_name The registrant's last name. | string | No | — | ≤ 64 characters | — |
phone The registrant's phone number. | string | No | — | — | — |
org The registrant's organisation. | string | No | — | — | — |
job_title The registrant's job title. | string | No | — | — | — |
country Two-letter country code, e.g. US. | string | No | — | — | — |
comments The registrant's questions or comments. | string | No | — | — | — |
custom_questions Answers to the meeting's custom questions, as JSON: [{"title": "...", "value": "..."}]. | array | No | — | array of object | — |
occurrence_ids Occurrences to register them for, for a recurring meeting. A JSON array or a comma-separated list; blank means every occurrence. | array | No | — | array of string | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"meeting_id": "81234567890"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Zoom created the registration. | boolean | true |
id The meeting number registered for. | string | — |
registrant_id The registrant id — pass it to Update Status. | string | — |
join_url This registrant's personal join link. | string | — |
topic The meeting's topic. | string | — |
start_time The meeting's start time. | string | — |
participant_pin_code Dial-in PIN, when the meeting has one. | string | — |
{
"id": "",
"join_url": "",
"ok": true,
"participant_pin_code": "",
"registrant_id": "",
"start_time": "",
"topic": ""
}Notes
- Registration must be switched on for the meeting (settings.approval_type 0 or 1); otherwise Zoom answers 3027 and nothing is created.
- With approval_type 1 (manual) the registrant is created as 'pending' and the join_url only works once Update Registrant Status approves them.
See Add Meeting Registrant 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.