Connecting Accounts
Connect a network, keep it healthy, and reconnect when a token expires.
How it works
- Go to Accounts
- Click Connect next to a network
- Approve on that network's own authorisation screen
- You come back, and the account shows as connected
FoPost never asks for your password. The network hands over a token that grants only what publishing needs, and you can revoke it from that network at any time.
The full list of networks is on Supported Platforms.
Networks with extra requirements
Most are one click. These need something in place first:
| Network | What you need |
|---|---|
| A Business or Creator account, linked to a Facebook Page | |
| A Page you administer. Personal profiles cannot be published to | |
| A profile, or admin on the company page | |
| Telegram | A one-time code sent to our bot in the chat you connect; for a channel, the bot made admin first (details) |
| Discord | Permission to add a webhook or a bot in the server |
| Slack | Permission to install an app in the workspace |
| A Business account | |
| Hashnode | A Pro publication, which is Hashnode's own requirement for API access |
| WordPress | The FoPost plugin installed on the site |
| Substack | The browser extension, since Substack has no write API |
Several accounts on one network
Each workspace connects one account per network, so a workspace always maps to one brand and the composer never guesses which of your X accounts you meant. A second account on the same network gets its own workspace, with its own calendar, media library, and analytics; switching workspaces takes one click.
Account health
Tokens expire and people revoke apps. Rather than finding out when a scheduled post fails, Accounts shows a health state per account:
- Healthy. Nothing to do
- Degraded. Still publishing, but something needs attention soon
- Expired or revoked. Publishing will fail until you reconnect
Click Reconnect and go through authorisation again. Nothing else is lost: your posts, history, and analytics stay attached to the account.
Turn on the account.health_changed webhook if you want to hear about it before a human notices.
Renaming and moving
Open the ⋯ menu on an account card.
- Rename gives the account a name of your own. It shows everywhere the account is listed and survives profile refreshes. Clear the name to go back to the network's.
- Move to Workspace moves the account, with its connection, inbox and analytics, to another workspace you own. If the account still has posts or other records in its current workspace, the move is refused and the reason names them.
When the workspace has account groups, they appear as filters above the cards.
Disconnecting
Disconnect removes the stored token. Posts already published stay published, since they live on the network now. Scheduled posts targeting that account will fail until you reconnect or retarget them.
Troubleshooting
Authorisation failed. Usually the wrong account was logged in on the network, or you lack admin on the Page, channel, or workspace. Check both, then retry.
Connected but posts fail. The token is valid and the permission is missing. Disconnect and reconnect to be re-prompted for the full permission set.
The account keeps disconnecting. Some networks expire tokens on a fixed schedule, and some revoke them when the account's password changes. If it recurs on one network, check whether anyone else revoked the app from that account's settings.
Next
Related documentation
- Guide
How to use FoPost as a creator, a team, or an agency.
- Getting Started
From signing up to your first published post.
- Dashboard Overview
A tour of the sidebar and what lives where.
- Creating Posts
The composer, per-network overrides, and previews.
- Scheduling
Schedule a post, repeat it, and see what happened.
- The Calendar
Everything scheduled and published, in one view you can drag.
- Bulk Scheduling
Import a spreadsheet of posts, validate it, and roll it back if it is wrong.
- Recycling
Send your evergreen winners out again, with a fresh variant each time.