ActionThreadsUpdated September 2026
How do I publish a staged Threads container?
Short answer: You can publish post in Threads by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Threads Publish Post action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Creation ID creation_id | string | Required | – |
Sample request
{"creation_id": "{{trigger.creation_id}}"}
Returns
{"id": "thread_abc"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Publish Post.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Publish Post.
What does the Publish Post action do in Threads?
Step 2 of Threads publishing: publishes a previously staged container (creation_id) and returns the live media ID. Recommended to wait a few seconds between staging and publish for media processing.
What inputs does Publish Post require?
Required: Creation ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Threads returns an error?
The run history shows the failed step with its input and the error message Threads returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Publish Post support batch operations?
Run Publish Post inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Threads's rate limits.
More actions
Other Threads actions.
Action
Create Post Container
Step 1 of Threads publishing: stages the post (text, media URL, alt text) and returns a creation_id. Pair with Publish Post to actually push it live.
ActionGet Post
Retrieves a Threads post by its media ID with engagement counts and metadata. Useful to read back details after publishing or for reporting.