List Rooms

webex.list_rooms

ActionChat & messagingconnection required

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

List the Webex spaces this connection belongs to.

Ask about Cisco Webex All Cisco Webex nodes Provider API docs ↗

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

4 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
team_id Only the spaces in this team.	string	No	—	—	—
type Only group spaces, or only 1:1 direct rooms.	string	No	—	one of "direct", "group"	—
sort_by Order the page by id, last activity or creation time.	string	No	—	one of "id", "lastactivity", "created"	—
max_results How many spaces to ask for (1-1000).	number	No	100	1–1000	—

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 space id — every other room and message node takes it.	string	—
items[].title The space's title.	string	—
items[].type 'group' for a space, 'direct' for a 1:1 room.	string	—
items[].team_id Id of the team the space belongs to, when it belongs to one.	string	—
items[].is_locked True when the space is moderated.	boolean	—
items[].is_public True when anyone in the organisation can find it.	boolean	—
items[].description The space's description.	string	—
items[].creator_id Id of the person who created it.	string	—
items[].owner_id Id of the organisation that owns it.	string	—
items[].last_activity When the space last had activity (ISO-8601).	string	—
items[].created When the space was created (ISO-8601).	string	—
count How many rows this page carries.	number	—

{
  "count": 0,
  "items": [
    {
      "created": "",
      "creator_id": "",
      "description": "",
      "id": "",
      "is_locked": false,
      "is_public": false,
      "last_activity": "",
      "owner_id": "",
      "team_id": "",
      "title": "",
      "type": ""
    }
  ]
}

Notes

The connection's token is the actor: a bot token only sees the spaces the bot has been added to, and a personal or integration token acts as that user.
The title of a 1:1 room is the other person's display name.
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.

Related Cisco Webex nodes

See List Rooms 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.

Book a technical demo Talk to sales