Help Center / Publishing & AccountsPublishing & Accounts

Connect the right account. Publish with confidence.

Cliprr keeps the normal path simple: connect through the provider, verify the account, test it, and only open Advanced when the platform requires extra configuration.

Connect your accounts

Start with the normal connection flow.

For everyday use, connect, authorize through the provider, return to Cliprr, and test the connection. Manual tokens and developer fields belong under Advanced.

YouTube

Connect the Google account that owns the YouTube channel you intend to publish to. Multiple eligible accounts can be configured.

YouTube setup →

Instagram Reels

Use an appropriate Instagram account, authorize through the provider screen, then verify the connected username and run Test Connection.

Instagram setup →

X / Twitter

Connect through OAuth. If your provider app requires a callback URL, use the value displayed by your current Cliprr version.

X setup →

TikTok

Connect and then check which capability is available. Draft Upload and Direct Post are separate provider capabilities.

TikTok setup →

Add and verify YouTube accounts

  1. Connect the Google account from Cliprr Settings.
  2. Open Check YouTube Channels.
  3. Compare the authenticated channel name and channel ID with the destination you expected.
  4. Confirm the account is healthy and eligible for publishing.
If uploads go to the wrong channel

Do not change routing first. A custom Cliprr label can point to a Google authorization that belongs to a different YouTube channel. Reconnect that account and choose the Google/YouTube identity that owns the correct channel.

How routing behaves

When multiple YouTube accounts are configured and eligible, Cliprr can distribute publishing work between them. If an upload is skipped, newer builds record a more specific reason such as disabled account, missing credentials, unhealthy account, quota/rate limitation, or upload failure.

Standard connection

  1. Use an Instagram Professional account where your Meta configuration requires it.
  2. Select Connect Instagram in Cliprr.
  3. Sign in on the official provider authorization screen and approve the requested publishing permissions.
  4. Return to Cliprr and confirm it shows Connected as @username.
  5. Run Test Connection.
Provider requirements matter

Instagram publishing depends on the Meta/Instagram account and app having the appropriate permissions. An external provider permission or approval problem is not necessarily a Cliprr bug.

Connect X

Use Connect X, complete provider authorization, return to Cliprr, then use Test. Reconnect and Disconnect are available when you need to refresh or remove the authorization.

Do not copy an old hard-coded port from a guide.

If your X developer/app configuration asks for a callback or redirect URL, use the callback URL displayed by your current Cliprr Settings page. Cliprr now derives provider callbacks from its configured backend instead of treating an old port as permanent.

Draft Upload

Cliprr can hand the video into the provider's draft flow when that capability is available.

Direct Post

Direct posting requires the appropriate TikTok API capability and approval. Cliprr shows when it is enabled.

Why Direct Post can be unavailable

The account can be successfully connected while the provider app only has Draft Upload access. Check the capability shown in Cliprr before treating the missing Direct Post option as an application failure.

Advanced / provider configurationOnly open this if the standard connection flow requires it.

Some Meta/Instagram, X, or TikTok setups may still require developer/app configuration such as a client ID/key, client secret, callback URL, publishing permissions, or provider app approval.

Keep the distinction clear: Cliprr configuration controls how Cliprr connects and publishes; provider configuration controls what the external platform allows that app/account to do.

When a callback URL is required, use the value displayed by the current Cliprr version rather than copying a stale hard-coded URL.