Vivomeetings ACTION
Update Conference
Updates an existing conference or webinar on VivoMeetings. See the documentation
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Vivomeetings account once, then configure and run Update Conference 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: "vivomeetings-update-conference",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
vivomeetings: { authProvisionId: "apn_xxxxxxx" },
hostId: "Host Id",
conferenceId: "Conference ID",
},
})
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": "vivomeetings-update-conference",
"configured_props": {
"vivomeetings": { "authProvisionId": "apn_xxxxxxx" },
"hostId": "Host Id",
"conferenceId": "Conference ID"
}
}'// 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": "vivomeetings",
},
},
},
)
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: "vivomeetings-update-conference",
arguments: {
hostId: "Host Id",
conferenceId: "Conference ID",
},
})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 |
|---|---|---|
hostId Host Id | string | The Id of the host. Required Dynamic |
conferenceId Conference ID | string | ID of the conference. Required Dynamic |
subject Subject | string | The subject of the meeting. Optional |
agenda Agenda | string | The description of the meeting. Optional |
start Start | string | Start time, this works in conjunction with the time_zone to set the correct time. Optional |
timeZone Time Zone | string | Time zone associated with the start time. In the IANA Time Zone database (https://www.iana.org/time-zones) Optional |
duration Duration | integer | Duration in minutes. Optional |
autoRecord Auto Record | string | Indicates whether the conference should be recorded automatically and the format. If omitted will default to none. Both record and stream must be the same value if recording and streaming together. Optional |
autoTranscribe Auto Transcribe | boolean | Whether the recording should automatically be transcribed. Valid values are true or false. If omitted will default to false. Optional |
oneTimeAccessCode One Time Access Code | boolean | When set to true an access code will be returned in the response. Optional |
muteMode Mute Mode | string | Sets the initial participant mute settings. Optional |
participants Contact Ids | string[] | The unique identification of the contacts. Optional Dynamic |
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
- vivomeetings-update-conference
- Version
- 0.0.2
- App
- Vivomeetings
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗