Add Member
webex.create_membership
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
Add someone to a Webex space, optionally as a moderator.
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, 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 |
|---|---|---|---|---|---|
room_id Id of the Webex space (a room id, not its title). Supports {{ }}. | string | Yes | — | — | Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0 |
person_email The person's Webex email address. | string | No | — | email format | john.andersen@example.com |
person_id The person's Webex id, as emitted by webex.list_people or webex.get_me. | string | No | — | — | — |
is_moderator Add them as a moderator of the space. | boolean | No | — | — | — |
- At least one of person_email, person_id must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"person_email": "john.andersen@example.com",
"room_id": "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The membership id — pass it to webex.delete_membership. | string | — |
room_id Id of the space this membership is in. | string | — |
person_id Id of the member. | string | — |
person_email Email of the member. | string | — |
person_display_name The member's display name. | string | — |
person_org_id Id of the member's organisation. | string | — |
is_moderator True when the member moderates the space. | boolean | — |
room_type 'group' for a space, 'direct' for a 1:1 room. | string | — |
created When the membership was created (ISO-8601). | string | — |
{
"created": "",
"id": "",
"is_moderator": false,
"person_display_name": "",
"person_email": "",
"person_id": "",
"person_org_id": "",
"room_id": "",
"room_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.
- Adding someone to a moderated space needs the token to be a moderator of it.
- Adding a person who is already a member fails with a 409.
See Add Member 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.