ActionThreadsUpdated May 2026

How do I fetch a Threads post by ID?

Short answer: Drop the "Threads → Get 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
Post ID post_id	string	Required	—

Sample request

{
  "post_id": "{{trigger.post_id}}"
}

Returns

{
  "id": "abc",
  "text": "Hello",
  "permalink": "https://threads.net/...",
  "timestamp": "2026-05-11T00:00:00Z",
  "media_type": "TEXT"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get 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 Get Post.

What does the Get Post action do in Threads?

Retrieves a Threads post by its media ID with engagement counts and metadata. Useful to read back details after publishing or for reporting.

What inputs does Get Post require?

Required: Post 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 Get Post support batch operations?

Yes. Run Get 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