Skip to main content
Every network connects through its own official sign-in, except Telegram and Discord, which need none.
In short: Open Connections and connect each network through its official sign-in, the PostMesh bot for Telegram or a channel webhook for Discord. PostMesh never sees your passwords. When a login expires, the account shows Reconnect; sign in again and it carries on.

​
How connecting works

  • Connections opens the network’s own sign-in page. You approve PostMesh there, then come back.
  • Telegram has no sign-in: you add the PostMesh bot to your channel or group as an admin. Discord takes a webhook URL you make in the channel’s settings (how).
  • Each Facebook Page and each YouTube channel becomes its own account, so you can post to them one by one.
  • You can connect several accounts on the same network, for example a personal and a brand X account.
  • Your plan sets how many accounts you can connect: 10 on Creator, 50 on Growth, no limit on Pro.
  • A social account can belong to one PostMesh account at a time.

​
What each network needs

​
Reconnect an expired login

Networks end logins from time to time. The account then shows Signed out in Connections, and a strip at the top of every page says which scheduled posts are at risk. Select Reconnect and sign in again; the account keeps its place and its history. PostMesh checks every connected account about once a day, and again 24 hours and 60 minutes before each scheduled post that goes to it. When a network turns a login down, PostMesh emails you once, with the posts waiting on that account and when the next one is due, while there is still time to reconnect. Those posts are held, not failed, until you reconnect. A Telegram or Discord account comes back on its own once the bot can post again or the webhook works.
Check that you still have the right role, for example admin on a Facebook Page. A PostMesh plan can’t grant a role the network hasn’t given you.

​
Name or pause an account

Signed in, PATCH /api/post/accounts takes account_id and label, paused or both. label is your own name for the account, up to 80 characters; null or an empty string clears it, so the handle shows alone. paused: true holds the account’s due posts: nothing is sent to it and they don’t fail. paused: false resumes it and sends them back to the queue. It answers { account: { id, label, paused, paused_at } }, and GET /api/post/accounts lists the same label, paused and paused_at on every account. API keys can’t rename or pause accounts.