Connect social accounts
How to connect nine social networks and understand the requirements and current availability of each one.
Every network controls its own programmatic-publishing rules. Naasher shows those requirements in Accounts → Connect a channel before authorization, so an unavailable provider path is not disguised as a working connection.
Three connection states
| State | Meaning |
|---|---|
| Available | The current product contract allows you to start authorization. |
| Coming soon — provider approval pending | The integration exists, but ordinary production access is not enabled. |
| Paid plan required | The provider uses a paid API or the feature belongs to a paid Naasher plan. |
Availability can differ by provider approval, account type, role, region, and granted scope. The in-product state for the exact workspace is authoritative when it differs from this dated guide.
Requirements by network
Instagram and Facebook
Facebook publishing targets Pages, not personal profiles. Instagram programmatic publishing requires an eligible professional account and the associated Meta assets and permissions. Authorize on Meta's screen and confirm the exact Page or Instagram identity returned before scheduling.
Threads
Threads authorization uses the provider's supported account relationship and scopes. Some formats and reply operations remain subject to provider rules, so validate the format and remote result on the intended account.
X
X uses a paid provider API. Naasher therefore exposes X only under the plan and credit rules shown in the current billing surface. Do not infer customer billing from the provider's developer pricing; read Plans and billing for the public product contract.
A personal profile and an organization Page are separate destinations. Publishing to an organization requires a role that LinkedIn accepts for that organization. Confirm the returned identity instead of relying on a display name alone.
TikTok
TikTok distinguishes Upload, in which the creator finishes an inbox draft, from reviewed Direct Post. Naasher's supported ordinary path is the explicitly labeled upload handoff unless the workspace shows approved Direct Post. An uploaded draft is not a live post.
Snapchat
Snapchat Login Kit support does not establish Public Profile publishing access. Ordinary production publishing remains disabled while provider allowlisting is pending. Naasher rejects a Snapchat publishing target rather than accepting a schedule it cannot execute.
Mastodon and Bluesky
Mastodon connects through the selected instance's authorization flow. Bluesky uses an app password created in account settings, not the user's main password. Instance policy, service availability, and format support still need an account-level acceptance check.
Tokens, refresh, and offboarding
Provider grants can expire or be revoked when a password, role, business asset, or provider policy changes. Naasher attempts supported refresh flows and surfaces reconnection when it cannot refresh. A stored green connection does not prove that the person's remote role still permits a future publish.
Keep a register with the workspace, provider identity, business owner, authorization owner, last acceptance test, and offboarding contact. When a person leaves, remove access on both the provider and Naasher sides. Never paste tokens into tickets, chat prompts, CSV files, or screenshots.
Account limits and billing
Each plan includes a documented number of connected accounts. Paid plans can have published overage rules; the free plan uses a hard limit. Naasher shows the current effect before adding an account. If a paid subscription ends, accounts beyond the free-plan limit can be disabled until the plan or connection set changes.
Continue with Publishing and scheduling, then test one low-risk post and verify the visible provider result before moving a critical calendar.