Connect and manage social channels

BlendDuck includes connections for X, Instagram, Facebook, TikTok, YouTube, LinkedIn, Threads, Reddit, Bluesky, Mastodon, Pinterest, Telegram, Snapchat Public Profiles, and Google Business Profile locations.

Use the channel capability matrix to compare all providers, then open the linked platform guide for exact formats, limits, completion checks, and recovery steps.

Before you connect

• Sign in to the correct social account in a separate browser tab.
• Confirm that the account type supports third-party publishing. Some personal profiles cannot be connected where a Business, Creator, Page, or Public Profile is required.
• Make sure your social account role can authorize apps and publish content.
• Turn off browser pop-up blocking for the authorization window when needed.

Connect a channel

1. Open Dashboard → Channels.
2. Select a provider and choose Connect.
3. Review the permissions on the provider's own authorization screen.
4. Choose the intended account when discovery returns multiple Pages, profiles, channels, or locations.
5. Return to BlendDuck and confirm the connected account name and avatar.

Telegram uses a BotFather token instead of OAuth. Add the bot to the target channel or group first, then provide its public @channel name or numeric chat ID. The token is encrypted and is never returned by channel APIs.

Capabilities are account-specific

A connected channel does not imply that every content type is available. BlendDuck evaluates connection, publishing, media, Analytics, Inbox, replies, messages, reactions, and moderation separately. Availability can depend on:

• the provider's app-review and product-access tier;
• the account type, region, age, and owner permissions;
• OAuth scopes granted during the latest connection;
• media format, aspect ratio, duration, size, and post type;
• native platform policy or moderation state.

The composer and channel details show the effective capabilities reported for that connection. Unsupported actions fail with a specific provider or capability error; BlendDuck does not report a false success.

Automatic connection recovery

BlendDuck refreshes expiring access tokens and manages recovery state in the background. Token expiry and refresh timing are not user-facing channel tasks. When a provider revoked the app, changed the native account role, or requires new permissions, use the normal Connect Channel flow again.

Before disconnecting, review scheduled posts and automations that use the channel. Disconnecting stops future provider actions but does not remove content already published on the native network.

See automatic channel recovery for the identity and failed-target safeguards.

Protect access

Treat social authorization as privileged access. Grant the smallest workspace role required, review connected channels regularly, and disconnect accounts a workspace no longer manages. Never paste provider tokens into a post, comment, support ticket, or public URL.