Connect Threads

A Threads connection lets Marketing post to a brand's Threads account and read its numbers. It is a connection of its own, beside Meta: Threads signs people in at threads.net with the Meta app's separate Threads app ID and secret, so one sign-in cannot hold both. It can live in the same Meta app. A Threads connection is your org's or a brand's. See Connections for how connecting works in general.

Ways to connect

  • Connect, through GreenMind's app, where it is open to your org.

  • Use your own app: a Meta app with the Threads use case. Start at Meta's app creation page; Meta's Threads guide explains the rest.

  • Post by hand instead, at the foot of the Use your own app dialog: you give the account's name, GreenMind prepares each post and opens Threads for you to finish it, and nothing is held for the account.

There is no key option.

Making your own app

Meta's names for screens and use cases change from time to time. Follow the dialog and Meta's documentation where this page and Meta's screens differ.

  1. Open the Use your own app dialog for Threads on the Connections page, and keep it open.
  2. In Meta for Developers, create an app (or open the one you use for Meta), and add the use case for accessing the Threads API. Meta's documentation says Threads can share an app with the Page use case; if Meta greys it out, make a second app.
  3. Open the Threads use case's Settings. Add the redirect URL from the dialog as a redirect callback URL, copied exactly. Meta's settings also ask for a deauthorize callback URL and a data deletion requests URL; give addresses of your own that explain how you remove what you hold.
  4. Add the permissions to the use case (see below).
  5. Copy the Threads app ID and Threads app secret from that same Threads settings page. They are not the Meta app's App ID and secret. Paste them into the dialog and press Connect.
  6. Add testers. While the app is not approved for people without a role, only accounts with a role on it can connect. In App roles > Roles, add each Threads account that will connect as a Threads Tester, and have each one accept the invitation in Threads, in its settings.
  7. Mark the use case Ready to test and publish the app (Live mode).

Permissions

threads_basic threads_content_publish threads_delete threads_manage_insights

By use:

Use Permissions
Post threads_basic, threads_content_publish, threads_delete
Read post insights threads_basic, threads_manage_insights

Add all four to the app's Threads use case. The Use your own app dialog lists the posting permissions, and the numbers permission too if you tick Also read the numbers of what is posted; Reconnect asks for all four.

App Review

Meta lets people with a role on your app use its permissions without a review. Anybody else needs App Review for each Threads permission, and Business Verification. See Connect Meta.

If it goes wrong

  • The sign-in fails or Meta says the app is not available. The account has no role on the app. Add it as a Threads Tester and accept the invitation.
  • The wrong id and secret. The Meta app's own App ID and secret do not work here; use the Threads app ID and secret.
  • Reconnecting. GreenMind refreshes a Threads token as it nears its end. If the connection still shows Needs reconnecting, sign in again with Reconnect.