How channels connect
Every platform is connected from the Channels page, but there are three different authorisation models. This page covers channel slots, token status and per-platform limits.
Three authorisation models
The Channels page holds every channel in one place, but how a channel is authorised differs. Knowing which model you are on saves time when something breaks.
| Model | Platforms | What it means for you |
|---|---|---|
| Authorisation login | TikTok, Facebook, Threads, LinkedIn | Click Add account, a popup opens, you sign in and approve. Renewal is automatic; you only reconnect if the platform revokes access. |
| Your own credentials | YouTube | You create an OAuth client in Google Cloud Console and register it here. The publishing quota belongs to your own Google project and is not shared. |
| Bot / OA | Telegram, Zalo OA | Telegram needs a bot you create and promote to admin in the channel. Zalo needs a verified Official Account on a plan that includes the Open API. |
The common steps
- 1
Open the Channels page
Left menu → Channels. The summary cards at the top show how many channels are connected, how many slots your plan has left, total followers, and how many channels are close to expiry.
- 2
Click Add account
Pick a platform from the list. Platforms that are not open yet are locked with the reason shown — Instagram, for instance, states that it is awaiting Meta approval.
- 3
Complete the authorisation in the popup
Sign in with the exact account you want to connect and approve every permission requested. Do not deselect any: drop the comment permission and the channel still publishes, but it will carry a Comment permission missing badge and auto-commenting silently will not run.
If no window appears, your browser is blocking popups. Allow popups for this site and try again.
- 4
Check the list
The new channel appears under the Accounts tab with the status Connected. From there you set the approval mode (publish automatically or wait for manual approval), attach a branding template to the channel, or add it to a group.
How channel slots work
A removed channel's slot frees up after 7 days
Every connected channel occupies one slot. When you disconnect a channel, its slot is held for another 7 days and then frees up on its own, with no need to contact support. Until then you cannot reuse that place for a different channel, so connecting one just to look around and then removing it still occupies the slot until the hold ends.
- Once every slot is used, Add account is disabled. Channels already connected keep publishing normally.
- Removing channels to get back under your plan's limit restores normal creating and publishing, but still will not let you connect a new channel — for that you need to upgrade.
- Reconnecting the exact channel you just removed within the 7-day hold takes its old place and costs no new slot. After 7 days it counts as a brand-new channel.
Reading channel status
| Status | What it means | What to do |
|---|---|---|
| Connected | The authorisation is valid and the channel can publish. | Nothing. |
| Expiring | The authorisation is close to its deadline. Renewal happens before publishing, but some platforms require a fresh sign-in. | Click Refresh token. If it still reads as expiring, use Reconnect. |
| Revoked | The platform cancelled access — usually after a password change, an app removal, or a long period of inactivity. | You must Reconnect. Refreshing the token cannot recover this. |
| Comment permission missing | The channel can publish, but the comment scope was skipped during authorisation. | Reconnect the channel and approve every permission requested. |
Two error messages that look alike
"The platform revoked access" is a real failure and needs a reconnect. "Could not reach the platform" is a temporary network problem — the channel is untouched, so wait a moment and retry. Do not remove the channel over the second message; removing it keeps its slot held for 7 days.
Per-platform limits
Each platform sets its own rules, and they differ by more than tenfold. The table below is read from the running configuration, so it always matches what the system actually enforces.
| Platform | Cap per 24 hours | Caption length | Max video |
|---|---|---|---|
| TikTok | 15 posts | 2,200 characters | 10 minutes · 9:16 |
| YouTube | 6 posts | 5,000 characters | 12 hours · 16:9 or 9:16 (Shorts) |
| Facebook Page | 50 posts | 63,206 characters | 45 minutes · 9:16 (Reels) |
| Chờ Meta duyệt | 2,200 characters | 2 minutes · 9:16 | |
| Threads | 250 posts | 500 characters | 5 minutes · 9:16 / 1:1 |
| 10 posts | 3,000 characters | 30 minutes · 16:9 / 1:1 / 9:16 | |
| Telegram | 50 posts | 1,024 characters | 1 hours · 16:9 / 9:16 / 1:1 |
| Zalo OA | 30 posts | 300 characters | 30 minutes · 16:9 / 9:16 |
On top of this hard cap there is a soft recommendation of 5 posts per channel per day. Passing the soft mark only produces a warning; passing the hard cap blocks the post at send time.
What permissions we request
We request only what is needed to publish and to read the figures for the channels you connect: publishing video, reading public profile details (name, avatar, follower count), reading reach and engagement for posts we published, and writing comments under those same posts.
- We do not read private messages, do not publish anything beyond what you create here, and do not touch channels you have not connected.
- You can revoke access at any time, either in the platform's own app settings or with the Disconnect button here.
- Access tokens are stored encrypted and used only for the actions you request.