Update Thread
twist.update_thread
ActionChat & messagingconnection required
Calls the Twist API with the connection's credentials.
Change a thread's title, body or notified recipients.
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
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, as returned by twist.add_thread or twist.get_threads. | string | Yes | — | — | 32038 |
title A replacement subject line for the thread. | string | No | — | — | API change: pagination on /threads (resolved) |
content The body text, in Twist's markdown format. | string | No | — | — | Shipping the API change tomorrow — shout if that is a problem. |
recipients User ids to notify, or the single value EVERYONE to notify the whole channel. | array | No | — | array of string | — |
- At least one of title, content, recipients must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"content": "Shipping the API change tomorrow — shout if that is a problem.",
"thread_id": "32038",
"title": "API change: pagination on /threads (resolved)"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The thread id. | number | — |
title The thread's title. | string | — |
content The body of the thread's opening post. | string | — |
channel_id The channel the thread lives in. | number | — |
workspace_id The workspace the channel belongs to. | number | — |
creator User id of whoever opened the thread. | number | — |
comment_count How many comments the thread carries. | number | — |
participants User ids taking part in the thread. | array | — |
recipients User ids notified about the thread. | array | — |
posted_ts When the thread was posted, as a Unix timestamp. | number | — |
last_updated_ts When the thread last changed, as a Unix timestamp. | number | — |
snippet Preview text of the most recent comment. | string | — |
pinned True when the thread is pinned in its channel. | boolean | — |
starred True when the current user starred the thread. | boolean | — |
is_archived True when the thread has been archived. | boolean | — |
attachments Files attached to the thread's opening post. | array | — |
reactions Reactions on the opening post, keyed by emoji. | object | — |
{
"attachments": [],
"channel_id": 0,
"comment_count": 0,
"content": "",
"creator": 0,
"id": 0,
"is_archived": false,
"last_updated_ts": 0,
"participants": [],
"pinned": false,
"posted_ts": 0,
"reactions": {},
"recipients": [],
"snippet": "",
"starred": false,
"title": "",
"workspace_id": 0
}See Update Thread 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.