Reply To Thread
twake.reply_to_thread
ActionChat & messagingconnection required
Calls the Twake API with the connection's credentials.
Add a message to an existing thread.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Twake
- Secret shape
- {"app_id": "…", "app_secret": "…"} — the application's API settings
- Config it needs
- base_url, company_id, workspace_id
- 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 |
|---|---|---|---|---|---|
thread_id The thread to act on; twake.send_message returns it as 'id'. | string | Yes | — | — | 7f1c9a20-0000-1111-2222-333344445555 |
text The message text, in Twake's markdown-like format. | string | No | — | — | Deploy finished — release 2026.09 is live. |
blocks Twake message blocks for a rich message (buttons, inputs, embedded views). | array | No | — | array of object | — |
company_id Twake company to act in; overrides the company set on the connection. | string | No | — | — | a1b2c3d4-1111-2222-3333-444455556666 |
- At least one of text, blocks must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"company_id": "a1b2c3d4-1111-2222-3333-444455556666",
"text": "Deploy finished — release 2026.09 is live.",
"thread_id": "7f1c9a20-0000-1111-2222-333344445555"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The message id. | string | — |
thread_id The thread the message belongs to. | string | — |
text The message text as Twake stored it. | string | — |
blocks The rich blocks on the message, empty when it is plain text. | array | — |
user_id The user who sent the message, empty for an application. | string | — |
application_id The application that sent the message, when it was one. | string | — |
created_at Creation time as a millisecond epoch timestamp. | number | — |
updated_at Last modification time as a millisecond epoch timestamp. | number | — |
files Files attached to the message. | array | — |
reactions Reactions on the message, each with a name and a count. | array | — |
{
"application_id": "",
"blocks": [],
"created_at": 0,
"files": [],
"id": "",
"reactions": [],
"text": "",
"thread_id": "",
"updated_at": 0,
"user_id": ""
}See Reply To Thread run in a workflow.
In a technical demo we add the Twake connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.