logo
Schedulin

Connecting a channel

A channel in Schedulin is a single social account — one Instagram profile, one LinkedIn page, one YouTube channel. You can connect as many channels as your plan allows.

How to connect

  1. Open the Channels page from the sidebar.
  2. Click Connect a channel and pick the network.
  3. You're redirected to the network's login screen. Sign in to the account you want to connect.
  4. Approve the permissions Schedulin requests. These are the minimum needed to publish and read analytics — we never request more than that.
  5. You're returned to Schedulin with the channel listed and ready to use.

Most networks (Twitter/X, LinkedIn, Bluesky, Threads, Pinterest, TikTok, YouTube, Reddit, Google Business Profile) connect with a single OAuth flow.

Meta networks (Facebook and Instagram) have extra requirements — see the per-platform guides.

Account type requirements

Some networks only allow API publishing from specific account types:

  • Instagram — Business or Creator account, linked to a Facebook Page.
  • Facebook — A Page (not a personal profile).
  • TikTok — Any account, but some advanced features require a Business account.
  • YouTube — Any account with the Data API enabled (handled automatically on connect).

See the social network guides for the full per-platform list.

Selecting a Page or sub-account

Some networks let you pick which page or sub-account to manage during the OAuth flow. For example:

  • Facebook asks which Pages you want Schedulin to publish to.
  • LinkedIn asks whether you want to publish as the personal profile or a company page.
  • Google Business Profile lists every location you manage.

Pick only the accounts you actually want to schedule for — you can always add more later.

What if the connection fails

  • "Already connected to another workspace" — the account is connected elsewhere. See Already connected to another workspace.
  • "Missing permissions" — you skipped a checkbox during OAuth. Restart the connect flow and approve all requested scopes.
  • OAuth redirect didn't return — disable browser extensions (especially privacy/ad blockers) that strip query parameters, then retry.
  • Network's API was down — try again in a few minutes. We surface the upstream error if the network returned one.

Next steps