Threads
Threads (Meta) post publishing
Threads is Meta's text-first social network — built as a Twitter alternative, tightly integrated with Instagram for follow graph and auth. Tiny Command exposes three actions, no triggers (Threads doesn't currently expose webhook-style event delivery for posts or replies): Create Post Container (step 1) (Threads requires a two-step publish — first create the post container with text and optional media), Publish Post (step 2) (publish the previously created container, returns the live post ID), Get Post (read a post's content and engagement). The connection uses Meta Graph OAuth with threads_basic and threads_content_publish scopes, scoped to the connected Instagram-linked Threads account. The two-step publish is a Threads API convention — Create the container, then Publish moves it live. For workflows that need to publish cross-network (e.g., cross-post from Bluesky or X to Threads), this is the path.
Do anything Threads can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| Get Post | Retrieves a Threads post by its media ID with engagement counts and metadata. Useful to read back details after publishing or for reporting. |
| Publish Post | 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. |
Pre-built Threads workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Threads once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Threads field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Threads integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Threads to Tiny Command?
What Threads triggers does Tiny Command support?
What Threads actions can I run from a workflow?
Is the Threads integration real-time?
Do I need to write code to use Threads with Tiny Command?
How much does the Threads integration cost?
More other apps people connect.
Same category as Threads, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Threads.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
