Connect a channel
post.buzz connects to your social accounts using each platform's official OAuth flow. You authorize access on the provider's own site, and we exchange the authorization for access tokens we can refresh on your behalf. We never see your password.
Connect an account
- Go to Settings → Accounts and choose Connect.
- Select the platform.
- You'll be redirected to that platform to sign in (if you aren't already) and shown the exact scopes we're requesting.
- Approve. You'll be sent back to post.buzz with the account connected.
Each platform requests the minimum scopes needed to publish, read insights, and manage engagement on your behalf. You can disconnect any account at any time from the same screen — see disconnecting below.
Per-platform notes
Most platforms use a standard OAuth 2.0 code exchange. A few are worth calling out:
- Facebook connects a Page (via a Business app), distinct from consumer Facebook Login used for sign-in.
- Instagram connects a professional (Business or Creator) account.
- Threads is a separate app/connection from Instagram.
- X (Twitter) detects your account tier (free vs. premium) at connect time, which drives your text and video limits.
- Bluesky uses an app password (
createSession), not OAuth. Create one in your Bluesky settings before connecting. - Mastodon is instance-based — you'll need your instance URL.
- YouTube connects a channel via Google.
- LinkedIn connects a profile (or organization page).
- Pinterest, Discord, Slack, Telegram, Reddit, Dribbble, Google Business — follow the on-screen OAuth steps; each has a slightly different permission surface.
For the full capability breakdown per platform (what you can publish, whether insights/comments/DMs are supported), see Platforms.
Disconnecting an account
When you disconnect an account, we revoke its tokens and soft-delete it. Historical posts and analytics are preserved with the account's name and avatar (visible as a "Disconnected" badge), but the account can no longer be used to publish or appear in the compose flow. Reconnecting the same channel later creates a fresh account row — there's no data leakage between connections.
Permissions and token refresh
Access tokens expire. post.buzz stores a refresh token for each connected account and uses it to silently obtain a new access token before the old one expires. If a refresh fails (for example, you revoked access at the provider), the account is marked disconnected and you'll be asked to reconnect.