Repository navigation
Threads toolkit: a managed Meta Threads integration with the full API surface #4807
King of Automation (andrea-kingautomation)
started this conversation in
Tool/Toolkit Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Composio has no Threads toolkit today. The Facebook and Instagram toolkits do not reach Threads: it lives on its own host,
graph.threads.net, so the Facebook connection's proxy rejects it (ExternalProxy_OriginMismatch, as also reported in #3624, which was auto-closed and redirected here).Why a managed toolkit matters, beyond convenience
The only way to use Threads programmatically today is to register your own Meta developer app. Until Meta approves that app through App Review, it only works for the app's own developer and tester accounts. So every team that wants agents to post on Threads either goes through Meta App Review for the Threads permissions themselves, or stays limited to accounts listed as testers. A Composio-managed toolkit with a reviewed app would remove that barrier for everyone, the same way the managed Instagram and Facebook toolkits do.
Scopes needed (official Threads API permissions)
threads_basic,threads_content_publish,threads_manage_replies,threads_read_replies,threads_manage_insights,threads_keyword_search,threads_delete,threads_manage_mentions,threads_profile_discoveryTools wanted (the full surface)
We run our own Threads connector and these are the 24 tools our agents use daily, which is a good map of what a complete toolkit needs:
Publishing uses Meta's two-step flow (create a media container with
POST /{user-id}/threads, thenPOST /{user-id}/threads_publish), with status polling for video and carousel containers. Returning the published media id and permalink makes downstream logging straightforward.Docs
Happy to share our tool definitions as a reference for the implementation.
All reactions