Get Message
webex.get_message
ActionChat & messagingconnection required
Calls the Cisco Webex API with the connection's credentials.
Fetch one Webex message by id, with its attachments.
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 |
|---|---|---|
id The message id — pass it to webex.get_message or delete_message. | string | — |
room_id Id of the space the message is in. | string | — |
room_type 'group' for a space, 'direct' for a 1:1 room. | string | — |
parent_id Id of the parent message when this is a threaded reply. | string | — |
person_id Id of the person or bot that posted it. | string | — |
person_email Email of the person or bot that posted it. | string | — |
text The message as plain text. | string | — |
markdown The message as Markdown, when it was sent that way. | string | — |
html The HTML Webex rendered from the Markdown. | string | — |
files URLs of the attachments; downloading one needs the same access token. | array | — |
created When the message was posted (ISO-8601). | string | — |
updated When it was last edited, if it has been. | string | — |
{
"created": "",
"files": [],
"html": "",
"id": "",
"markdown": "",
"parent_id": "",
"person_email": "",
"person_id": "",
"room_id": "",
"room_type": "",
"text": "",
"updated": ""
}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.
See Get 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.