Short answer: Drop the "Twist → Create Thread" 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 |
|---|---|---|---|
Channel ID channel_id | string | Required | The Channel ID assigned by Twist. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Title title | string | Required | — |
First Message (Markdown) content | string | Required | — |
{"channel_id": "{{trigger.channel_id}}","title": "{{trigger.title}}","content": "{{trigger.content}}"}
{"id": 7777,"title": "RFC","channel_id": 1}
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.