Send Conversation Message
twist.add_message
ActionChat & messagingconnection required
Calls the Twist API with the connection's credentials.
Post a message into a direct conversation rather than a channel thread.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Twist
- Secret shape
- {"access_token": "…"} — the token Twist's OAuth2 flow returns
- Config it needs
- workspace_id, channel_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 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 |
|---|---|---|---|---|---|
conversation_id The conversation to post into, as a Twist conversation id. | string | Yes | — | — | 13030 |
content The message body, in Twist's markdown format. | string | Yes | — | — | Standup moved to 10:00 — see you there. |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"content": "Standup moved to 10:00 — see you there.",
"conversation_id": "13030"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Send Conversation Message run in a workflow.
In a technical demo we add the Twist connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.