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.Documentation Index
Fetch the complete documentation index at: https://help.hivra.app/llms.txt
Use this file to discover all available pages before exploring further.
How connections work
Every platform follows the same four-step flow regardless of which tile you choose.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.
Confirm the redirect
A confirmation overlay appears summarizing the workspace you are wiring and the callback URL that fires when the platform returns control to Hivra. Review it, then click Continue.
Grant scopes in the platform's UI
You are redirected to the platform’s own 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.
Supported platforms
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 and long-form videos to your YouTube channel with playlist and privacy settings.
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.| State | Meaning |
|---|---|
| Healthy | The stored token is valid and Hivra can publish to this account. |
| Attention | The token has expired or been revoked. Scheduled posts to this account will fail until you reconnect. |
When to reconnect vs disconnect
- Reconnect when the health chip reads Attention 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.
Meta token family: Instagram, Facebook, and Threads
Instagram, Facebook Pages, and Threads are all Meta products that share the same OAuth token family. When you reconnect one of these accounts, the refresh may also update the tokens for the other two. This is expected behavior — if you manage all three surfaces in Hivra, reconnect them together so the tokens stay in sync.If one Meta account shows Attention, check whether the other two are also affected before reconnecting just one.
Troubleshooting connection issues
OAuth redirect loop or blank screen after authorization
OAuth redirect loop or blank screen after authorization
Connection card shows Attention immediately after authorizing
Connection card shows Attention immediately after authorizing
Wrong workspace is connected
Wrong workspace is connected
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.
Still failing after multiple attempts
Still failing after multiple attempts
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.