Threads posts, replies, insights & webhooks
3 fields
Get the authenticated Threads user's profile.
1 field
Look up a public Threads profile by username (>=100 followers).
2 fields
List a public Threads profile's posts by username (>=100 followers).
5 fields
Create a Threads media container (step 1 of publishing).
16 fields
Publish a previously-created Threads media container (step 2).
Check the processing status of a media container before publishing.
Delete one of the authenticated user's own Threads posts.
Get the user's remaining publishing / reply / delete quota (per 24h).
Get a single Threads post (media object) by ID.
List the authenticated user's Threads posts.
7 fields
List the authenticated user's ghost (ephemeral) posts.
Get the top-level replies to a Threads post.
Get the full (flattened, nested) conversation for a Threads post.
List replies authored by the authenticated user.
Hide or unhide a reply on one of the user's posts.
List pending (approval-gated) replies on the user's posts.
4 fields
Approve or ignore a pending reply.
Get insights for a single Threads post.
Get account/user-level Threads insights.
Search public Threads posts by keyword or tag.
9 fields
List public Threads posts that mention the authenticated user.
Search for a location to tag on a post.
Get a Threads location object by ID.
Make an arbitrary Threads Graph API request (escape hatch).
Every Threads mention arrives in Slack with the conversation it came from and a reply already drafted in your account's voice, ready for a person to send or ignore. Threads is a reply first platform, and an account that only broadcasts gets treated like an ad. This agent takes each mention, reads the conversation it came out of, checks who wrote it, and drafts the response in the voice you described, so your community manager is approving a reply rather than staring at an empty box. Nothing is ever published by the agent: every reply leaves from a human hand. ## What people use it for - **Replies that sound like you** - The draft copies the register from your own examples, so whoever is on the account edits a sentence instead of composing from scratch and sounding like a help desk. - **Context before the reply** - A mention is usually the fortieth reply in somebody else's thread. The Slack message shows what was being discussed, so nobody answers a question that was never put to them. - **Ten seconds, not ten minutes** - Opening the thread, checking the account and finding the right tone is most of the work in replying. Having it done in advance is what makes answering every mention realistic for one person. - **Nothing goes out unread** - The agent cannot publish. Everything that appears on Threads was read and sent by somebody who works here, which is the only way an account keeps a voice worth having. ## Before you fork **What do we need connected?** A Threads account connected through its Meta app, with permission to read your mentions and replies, plus the Slack channel the drafts land in. After that the only thing left to write is the voice notes. Test Run stages a mention against your real instructions, so you can read three drafts before a live one appears anywhere. **How does it know how we sound?** From the voice notes and nowhere else. Paste two or three replies you actually liked, name the subjects you keep out of, and it copies that register rather than inventing a personality of its own. When a draft feels wrong, change the examples rather than the wording, because the examples are what it reads before writing anything. **A post about us went viral. What happens then?** Each mention triggers its own run, so a viral thread costs a run per mention and fills Slack at the moment you are least able to read it. The voice notes are where you bound that: tell it to skip mentions that ask nothing and to stay out of arguments it is only named in, and the volume drops to the handful genuinely addressed to you.
Wire Threads into a coding agent and let it use these operations as tools.
Start building workflows in minutes with our visual builder. No code required.