Delete Message
webex.delete_message
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
Delete one Webex message.
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, 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 |
|---|---|---|---|---|---|
message_id Id of the message, as emitted by webex.create_message or webex.list_messages. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok Always true; a failure raises instead. | boolean | true |
message_id Id of the message that was deleted. | string | — |
{
"message_id": "",
"ok": true
}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.
- Anyone can delete their own message; deleting someone else's needs a space moderator or a compliance officer token.
See Delete Message 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.