Skip to main content
The Threads group powers the Threads automation (beta) Make.com app. It reads your Meta Threads posts, engagement insights, replies, and full conversation trees so you can store and search them in a Notion database. Callers authenticate with the MMK X-API-KEY header (or a Bearer token). The Threads account itself is connected once from the Magic Meal Kits app’s connection page — the credential is stored server-side on your deployment, so callers never pass the Threads token directly (see Authentication).
Closed beta — approved accounts only. The Threads automation is currently an invite-only beta. Only accounts that applied and were approved can use it. Apply on the Threads beta application page, and the team will send account-activation instructions after review. Requests from non-approved accounts will not be provisioned.
The data endpoints require a Pro license. A Basic key is rejected with 400 and you are not a magic meal kits PRO user. The health endpoint only requires a valid API key or Bearer token.

​
Endpoints

EndpointTierWhat it does
GET /threads/healthAPI keyLiveness check for the Threads routes
GET /threads/user/threadsProPaginated list of a user’s posts (optional per-post insights)
GET /threads/user/insightsProProfile insights — views, likes, follower demographics, …
GET /threads/media/repliesProDirect replies to a single post
GET /threads/media/conversationProFull conversation tree for a single post
POST /threads/media/conversationsProConversations for multiple posts in one call
GET /threads/media/conversation/emailsProEmail addresses surfaced in a post’s conversation
GET /threads/user/threads-with-conversationsProPosts from the last N months with all their conversations
GET /threads/analytics/top-engaged-usersProTop engaged users with reply / participation / engagement metrics
All paths are under the /api/v1 prefix (e.g. GET /api/v1/threads/user/threads).

​
Notes

  • Connect once from the app. Link your Threads account on the connection page in the Magic Meal Kits app; the credential is stored server-side, so you call the data endpoints with just your MMK API key. If the stored token expires, reconnect there and redeploy your MCP server with the latest version.
  • Page in batches. The Threads API caps a page at 100 items. When syncing to Notion, keep batches under 100 records (enable the date-range advanced option) to avoid performance issues.
  • Insights are optional and slower. include_insights=true on /user/threads fetches per-post metrics with bounded concurrency (max_concurrency) — expect longer response times for large accounts.
Server not responding, Google Cloud billing, or stopping/reinstalling the service? See Troubleshooting — those topics apply to every deployment, not just Threads.