Short answer: Drop the "Webex → Send Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Room/Space ID roomId | string | Optional | Either roomId or toPersonEmail is required |
To Person Email toPersonEmail | Optional | Send direct message by email | |
Message (Plain Text) text | string | Optional | Message (Plain Text) |
Message (Markdown) markdown | string | Optional | Supports Webex Markdown formatting |
{"roomId": "{{trigger.roomId}}","toPersonEmail": "{{trigger.from}}","text": "{{trigger.text}}","markdown": "{{trigger.markdown}}"}
{"id": "msg123","text": "Hello!","roomId": "room456","created": "2026-04-11T10:00:00Z","personEmail": "bot@webex.bot"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.