Create Team
webex.create_team
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
Create a Webex team to group spaces and people under.
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
2 fields, 1 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 |
|---|---|---|---|---|---|
name The team's name. Supports {{ }}. | string | Yes | — | — | Build Squad |
description What the team is for. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"name": "Build Squad"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The team id — pass it as team_id to webex.create_room. | string | — |
name The team's name. | string | — |
description The team's description. | string | — |
created When the team was created (ISO-8601). | string | — |
{
"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.
- Creating a team creates its General space too; pass the team id to webex.create_room to add more.
See Create Team 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.