List Meetings
webex.list_meetings
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
List Webex meetings in a time window or by state.
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
11 fields, none 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 |
|---|---|---|---|---|---|
from_time Only meetings starting at or after this ISO-8601 date and time. | string | No | — | iso8601 format | — |
to_time Only meetings starting at or before this ISO-8601 date and time. | string | No | — | iso8601 format | — |
state Only meetings in this state. | string | No | — | one of "active", "scheduled", "ready", "lobby", "inProgress", "ended", "missed", "expired" | — |
meeting_type Whether to return recurring series, their scheduled occurrences, or single meetings. | string | No | — | one of "meetingSeries", "scheduledMeeting", "meeting" | — |
scheduled_type Narrow meetingSeries results to meetings, webinars or personal rooms. | string | No | — | one of "meeting", "webinar", "personalRoomMeeting" | — |
meeting_number Only the meeting with this number. Webex then ignores the window, state and meeting_type filters. | string | No | — | — | — |
web_link Only the meeting with this join link. | string | No | — | url format | — |
room_id Only the meetings associated with this Webex space. | string | No | — | — | — |
site_url The Webex site to list from, e.g. acme.webex.com. Defaults to all of the host's sites. | string | No | — | — | — |
host_email Act on the meeting of this host instead of the token's own. Needs an admin or delegate token. | string | No | — | email format | — |
max_results How many meetings to ask for. | number | No | 100 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_results": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items[].id The meeting id — the other meeting nodes take it. | string | — |
items[].meeting_number The numeric meeting number attendees dial. | string | — |
items[].title The meeting's title. | string | — |
items[].agenda The meeting's agenda. | string | — |
items[].password The meeting password. | string | — |
items[].meeting_type 'meetingSeries', 'scheduledMeeting' or 'meeting'. | string | — |
items[].state scheduled, ready, lobby, inProgress, ended, missed or expired. | string | — |
items[].timezone The timezone start and end are expressed in. | string | — |
items[].start When it starts (ISO-8601). | string | — |
items[].end When it ends (ISO-8601). | string | — |
items[].recurrence The recurrence rule, for a recurring series. | string | — |
items[].host_email Email of the meeting host. | string | — |
items[].host_display_name Display name of the meeting host. | string | — |
items[].site_url The Webex site the meeting lives on. | string | — |
items[].web_link Link participants use to join. | string | — |
items[].sip_address SIP address for joining from a video system. | string | — |
items[].room_id Id of the space the meeting is associated with, if any. | string | — |
count How many rows this page carries. | number | — |
{
"count": 0,
"items": [
{
"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
- Passing meeting_number makes Webex ignore from_time, to_time, state and meeting_type.
- One page only: Webex paginates with an RFC 5988 Link header, which this node does not follow — narrow the filters or raise max_results instead.
See List Meetings 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.