Short answer: Drop the "Threads → Create Post Container" 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 |
|---|---|---|---|
Media Type media_type | options | Required | — |
Text text | string | Optional | — |
Image URL image_url | string | Optional | A fully qualified URL (https://...) for the image url. |
Video URL video_url | string | Optional | A fully qualified URL (https://...) for the video url. |
Reply to Post ID reply_to_id | string | Optional | — |
{"media_type": "{{trigger.media_type}}","text": "{{trigger.text}}","image_url": "e.g. https://example.com/path","video_url": "e.g. https://example.com/path","reply_to_id": "{{trigger.reply_to_id}}"}
{"id": "container_abc"}
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.