List Teams
webex.list_teams
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
List the Webex teams this connection belongs to.
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
1 field, 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 |
|---|---|---|---|---|---|
max_results How many teams 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 team id — pass it as team_id to webex.create_room. | string | — |
items[].name The team's name. | string | — |
items[].description The team's description. | string | — |
items[].created When the team was created (ISO-8601). | string | — |
count How many rows this page carries. | number | — |
{
"count": 0,
"items": [
{
"created": "",
"description": "",
"id": "",
"name": ""
}
]
}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.
- 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 Teams 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.