Hivra connects to Threads using the Threads API. Once your account is linked, you can publish content from the Hivra Composer to your Threads profile. Threads offers granular control over who can reply to each post, which Hivra exposes as per-post settings in the Composer.
Connect your Threads account
Open Integrations
In Hivra, go to Dashboard → Integrations and find the Threads tile.
Start the redirect
Click Connect to start the authorization flow.
Authorize in Threads
You are redirected to Meta’s authorization page for Threads. Accept all requested permissions — these cover creating posts on your Threads profile. Declining any scope prevents the connection from completing.
Verify the connection card
After the redirect returns you to Hivra, your Threads handle and profile picture appear on the integration card. The health chip reads Healthy once the monitoring job confirms the token is valid.
Threads publish settings
When you add Threads as a destination in the Composer, a settings panel appears with the following options.
Reply audience
Use the Who can reply selector to control which accounts can respond to your post. Threads exposes the following options:
| Option | Who can reply |
|---|
| Everyone | Any Threads user |
| Accounts you follow | Only accounts you follow on Threads |
| Mentioned only | Only accounts you explicitly @mention in the post |
| Followers only | Accounts that follow you on Threads |
| Parent post author only | Only the author of the post you are replying to (relevant for threaded conversations) |
Choose Mentioned only or Followers only when you want to limit unsolicited replies on posts that are likely to attract broad attention.
By default, the Composer’s shared caption is used for all destinations. To write a different caption specifically for Threads, click the Threads tile in the Customize Caption Per Platform section and enter your Threads-specific text. Hashtags and @mentions you include here apply only to the Threads post.
Reconnect your Threads account
If the Threads integration card in the dashboard overview shows Attention/Issue, your Meta token has expired or been revoked.
Open Integrations
Go to Dashboard → Integrations and locate the Threads card.
Click Reconnect
Click Reconnect on the card to restart the OAuth flow.
Re-authorize in Threads
Accept all permissions on Meta’s authorization page to issue a fresh token.
Confirm the health chip
Wait for the monitoring job to run. The chip should return to Healthy after the check runs.
If your Instagram or Facebook Pages accounts are also connected in the same workspace, check whether those cards also show Attention after reconnecting.