Zoom ACTION
Update Meeting
Updates an existing Zoom meeting
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zoom account once, then configure and run Update Meeting 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-update-meeting",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zoom: { authProvisionId: "apn_xxxxxxx" },
meetingId: "Meeting ID",
topic: "Topic",
},
})
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-update-meeting",
"configured_props": {
"zoom": { "authProvisionId": "apn_xxxxxxx" },
"meetingId": "Meeting ID",
"topic": "Topic"
}
}'// 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-update-meeting",
arguments: {
meetingId: "Meeting ID",
topic: "Topic",
},
})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 Zoom Meeting ID of the meeting you'd like to update. Required |
topic Topic | string | Meeting topic Optional |
type Type | integer | Meeting type:
1 - Instant meeting.
2 - Scheduled meeting.
3 - Recurring meeting with no fixed time.
8 - Recurring meeting with fixed time. Optional |
start_time Start time | string | Meeting start time. We support two formats for start_time - local time and GMT.
To set time as GMT the format should be yyyy-MM-ddTHH:mm:ssZ.
To set time using a specific timezone, use yyyy-MM-ddTHH:mm:ss format and specify the timezone ID in the timezone field OR leave it blank and the timezone set on your Zoom account will be used. You can also set the time as UTC as the timezone field.
The start_time should only be used for scheduled and / or recurring webinars with fixed time. Optional |
duration Duration | integer | Meeting duration (minutes). Used for scheduled meetings only. Optional |
timezone Timezone | string | Time zone to format start_time. For example, America/Los_Angeles. For scheduled meetings only. Please reference our time zone list for supported time zones and their formats. Optional |
password Password | string | Password to join the meeting. Password may only contain the following characters: [a-z A-Z 0-9 @ - _ *]. Max of 10 characters. Optional |
agenda Agenda | string | Meeting description. Optional |
tracking_fields Tracking fields | any | Tracking fields. Optional |
recurrence Recurrence | object | Recurrence object Optional |
settings Settings | string | Meeting settings. 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-update-meeting
- Version
- 0.1.8
- App
- Zoom
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗