ActionThreadsUpdated May 2026

How do I publish a staged Threads container?

Short answer: Drop the "Threads → Publish Post" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Threads actions

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.

Google Sheets → Threads

2 Google Sheets triggers

HubSpot → Threads

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Publish Post support batch operations?

Yes. Run Publish Post inside a Loop node to process arrays. Tiny Command handles Threads's rate limits automatically so you don't have to throttle manually.

More actions