Zoom ACTION
Add Meeting Registrant
Registers a participant or multiple participants for a meeting. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoom account once, then configure and run Add Meeting Registrant from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "zoom-add-meeting-registrant",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoom: { authProvisionId: "apn_xxxxxxx" },
meetingId: "Meeting ID",
occurrenceIds: "Occurrence IDs",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "zoom-add-meeting-registrant",
"configured_props": {
"zoom": { "authProvisionId": "apn_xxxxxxx" },
"meetingId": "Meeting ID",
"occurrenceIds": "Occurrence IDs"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "zoom",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "zoom-add-meeting-registrant",
arguments: {
meetingId: "Meeting ID",
occurrenceIds: "Occurrence IDs",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
meetingId Meeting ID | string | The meeting ID to get details for. Required Dynamic |
occurrenceIds Occurrence IDs | string | Occurrence IDs. You can find these with the meeting get API. Multiple values separated by comma. Optional |
email Email | string | A valid email address of the registrant. Required |
firstName First Name | string | Registrant's first name. Required |
lastName Last Name | string | Registrant's last name. Required |
address Address | string | Registrant's address. Optional |
city City | string | Registrant's city. Optional |
country Country | string | Registrant's country. Optional |
zip Zip/Postal Code | string | Registrant's Zip/Postal code. Optional |
state State/Province | string | Registrant's State/Province. Optional |
phone Phone | string | Registrant's Phone number. Optional |
industry Industry | string | Registrant's industry. Optional |
org Organization | string | Registrant's Organization. Optional |
jobTitle Job Title | string | Registrant's job title. Optional |
purchasingTimeFrame Purchasing Time Frame | string | This field can be included to gauge interest of webinar attendees towards buying your product or service. Optional |
roleInPurchaseProcess Role in Purchase Process | string | Role in Purchase Process. Optional |
noOfEmployees Number of Employees | string | Number of Employees. Optional |
comments Comments | string | A field that allows registrants to provide any questions or comments that they might have. Optional |
customQuestions Custom Questions | string | Custom questions. Optional |
registrants Registrants | object | Use this field to enter multiple registrants at once. Will override the single registrant fields if provided. Each registrant should be an object with at least the following properties: email, first_name, last_name. Example:
[ { "email": "test@example.com", "first_name": "John", "last_name": "Doe" } ] Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- zoom-add-meeting-registrant
- Version
- 0.3.12
- App
- Zoom
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗