Update Meeting

webex.update_meeting
ActionChat & messagingconnection required

Calls the Cisco Webex API with the connection's credentials.

Change the title, time or agenda of a scheduled Webex meeting.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Cisco Webex
Secret shape
the Webex access token, or {"access_token": "…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

10 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
meeting_id
Id of the meeting, as emitted by webex.create_meeting or webex.list_meetings.
stringYes———
title
The meeting's new title. Supports {{ }}.
stringNo——Sprint review
start
New ISO-8601 start time.
stringNo—iso8601 format—
end
New ISO-8601 end time.
stringNo—iso8601 format—
agenda
The meeting's new agenda.
stringNo———
password
A new meeting password.
stringNo—credential materialcredential
timezone
Timezone the start and end times are in, e.g. Asia/Kolkata.
stringNo———
recurrence
A new recurrence rule, e.g. FREQ=DAILY;INTERVAL=1;COUNT=10.
stringNo———
send_email
Have Webex email the invitees about the change.
booleanNo———
host_email
Act on the meeting of this host instead of the token's own. Needs an admin or delegate token.
stringNo—email format—
  • At least one of title, start, end, agenda, password, timezone, recurrence must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "title": "Sprint review"
}

Output

One shape.

result

FieldTypeExample
id
The meeting id — the other meeting nodes take it.
string—
meeting_number
The numeric meeting number attendees dial.
string—
title
The meeting's title.
string—
agenda
The meeting's agenda.
string—
password
The meeting password.
string—
meeting_type
'meetingSeries', 'scheduledMeeting' or 'meeting'.
string—
state
scheduled, ready, lobby, inProgress, ended, missed or expired.
string—
timezone
The timezone start and end are expressed in.
string—
start
When it starts (ISO-8601).
string—
end
When it ends (ISO-8601).
string—
recurrence
The recurrence rule, for a recurring series.
string—
host_email
Email of the meeting host.
string—
host_display_name
Display name of the meeting host.
string—
site_url
The Webex site the meeting lives on.
string—
web_link
Link participants use to join.
string—
sip_address
SIP address for joining from a video system.
string—
room_id
Id of the space the meeting is associated with, if any.
string—
{
  "agenda": "",
  "end": "",
  "host_display_name": "",
  "host_email": "",
  "id": "",
  "meeting_number": "",
  "meeting_type": "",
  "password": "",
  "recurrence": "",
  "room_id": "",
  "sip_address": "",
  "site_url": "",
  "start": "",
  "state": "",
  "timezone": "",
  "title": "",
  "web_link": ""
}

Notes

  • Sends a PATCH, so only the fields set here change and the rest of the meeting is left alone.
  • Applies to a meeting series or a scheduled meeting; an ended or in-progress occurrence cannot be updated.

See Update Meeting run in a workflow.

In a technical demo we add the Cisco Webex connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.