Create Room

webex.create_room
ActionChat & messagingconnection required

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

Create a Webex space, optionally inside a team.

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

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

FieldTypeRequiredDefaultConstraintsExample
title
The space's title, as members see it. Supports {{ }}.
stringYes——Incident 4821
team_id
Id of the team to create the space in, from webex.create_team or list_teams.
stringNo———
description
A description shown under the title.
stringNo———
is_public
Make the space discoverable by anyone in the organisation.
booleanNo———
is_locked
Moderate the space, so only moderators can add people or change it.
booleanNo———
is_announcement_only
Announcement mode: only moderators may post.
booleanNo———
classification_id
Id of the space classification to apply, for organisations that use them.
stringNo———

Example configuration

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

{
  "title": "Incident 4821"
}

Output

One shape.

result

FieldTypeExample
id
The space id — every other room and message node takes it.
string—
title
The space's title.
string—
type
'group' for a space, 'direct' for a 1:1 room.
string—
team_id
Id of the team the space belongs to, when it belongs to one.
string—
is_locked
True when the space is moderated.
boolean—
is_public
True when anyone in the organisation can find it.
boolean—
description
The space's description.
string—
creator_id
Id of the person who created it.
string—
owner_id
Id of the organisation that owns it.
string—
last_activity
When the space last had activity (ISO-8601).
string—
created
When the space was created (ISO-8601).
string—
{
  "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 token's own identity joins the new space; add everyone else with webex.create_membership.

See Create Room 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.