Skip to main content
Hivra connects to your social accounts through each platform’s official OAuth flow. You authorize Hivra once per account, and Hivra stores an access token that lets it publish on your behalf — you never share your password. This page explains how every connection works, what the health states mean, and when to reconnect or disconnect an account.

​
How connections work

Every platform follows the same three-step flow regardless of which tile you choose.
1

Choose a platform tile

Open Dashboard → Integrations and click the tile for the platform you want to connect. The tile list shows all supported platforms and indicates which are already linked.
2

Grant scopes in the platform's UI

When you click Connect, you’re redirected to the platform’s official authorization page. Accept all the permissions listed — these are the minimum scopes Hivra needs to publish. If you decline any scope, the callback lands in a soft-failure state and the connection will not complete.
3

Validate the connection card

After the redirect returns you to Hivra, the integration card displays your profile picture, handle, and account ID. Within a few minutes, the monitoring job runs, and the status in the Integration Health section of the dashboard overview should read as Healthy.

​
Supported platforms

Instagram

Share Reels and Stories to your Instagram professional or creator account.

TikTok

Publish videos directly to your TikTok profile with privacy and disclosure controls.

YouTube

Upload Shorts to your YouTube channel with playlist and privacy settings.

Facebook

Post Reels and videos to your Facebook Page.

X

Share video clips and tweet text to your X timeline.

Threads

Publish content to your Threads profile with reply audience controls.

​
Connection health states

Each integration card displays a health chip that updates after every monitoring cycle.
StateMeaning
HealthyThe stored token is valid and Hivra can publish to this account.
AttentionThe token has expired or been revoked. Scheduled posts to this account will fail until you reconnect.
IssueThe token has expired or been revoked. Publishing or scheduling will fail until you reconnect.

​
When to reconnect vs disconnect

  • Reconnect when the health chip reads Attention or Issue, or you receive an email alert about a failed scheduled post. Reconnecting re-runs the OAuth flow and issues a fresh token without removing any of your existing drafts or publish history.
  • Disconnect when an account should stop receiving posts entirely. Content already published to the platform stays live, but Hivra will no longer target that account for new publishes.
Disconnecting an account removes it from all queued and scheduled posts. Review your upcoming schedule before disconnecting.

​
Troubleshooting connection issues

Browser extensions — particularly ad blockers and privacy shields — can intercept the OAuth redirect. Try connecting in a fresh browser window with extensions disabled, or use a private/incognito window.
Confirm you accepted every permission on the platform’s authorization page. If you dismissed any scope, disconnect the partial connection and restart the flow, accepting all scopes this time. Also, the integration health check runs once every 24 hours; you may need to wait for the next check to run before status is updated.
Use the sidebar switcher to verify you are inside the correct workspace before starting the OAuth flow. Tokens are scoped to the workspace that was active when you authorized.
Copy the URL from your browser’s address bar immediately after the redirect completes, note the timestamp, and email both to support@hivra.app. The support team can correlate the URL parameters with server-side ingestion logs to diagnose the failure.

​
Suggest a new platform

If you publish to a platform Hivra does not yet support, use the Suggest integration field at the bottom of the Integrations page to submit it. Suggestions are reviewed when planning the platform roadmap.