Short answer: Drop the "Discord → 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 channelId | string | Required | Channel ID |
Thread Name name | string | Required | Thread Name |
First Message message | string | Required | First Message |
{"channelId": "{{trigger.channelId}}","name": "{{trigger.name}}","message": "{{trigger.message}}"}
{"id": "thread123","name": "Discussion","type": 11}
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.