Short answer: Drop the "Twist → Post Comment" 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 |
|---|---|---|---|
Thread ID thread_id | string | Required | — |
Content (Markdown) content | string | Required | — |
{"thread_id": "{{trigger.thread_id}}","content": "{{trigger.content}}"}
{"id": 9999,"posted": "2026-05-11T00:00:00Z","content": "Hi"}
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.