Skip to main content
BlendDuck

Connect the channels your brand actually operates

One provider layer normalizes account connections, publishing capabilities, validation, tokens, and errors while preserving platform-specific controls.

A broad channel foundation, with honest capability boundaries

Availability depends on each platform's credentials, app review, account type, and granted permissions. BlendDuck rejects unsupported actions explicitly.

Twitter / X

OAuth 2.0 connection, text publishing, media upload, and thread-aware provider foundations.

Instagram

Connect professional accounts and publish supported image, video, Reel, Story, and carousel shapes.

Facebook

Connect selected Pages and publish Page text or supported image posts with explicit Page access.

TikTok

Creator-aware privacy choices, consent controls, video Direct Post, and photo carousel foundations.

LinkedIn

OIDC identity connection and versioned text publishing for authorized member profiles.

YouTube

OAuth connection and provider foundations for uploading channel video content.

Snapchat

Public Profile foundations for publishing supported Spotlight videos and Public Story media.

Operate beyond the largest social platforms

The provider contract also supports community and decentralized networks without pretending they all share identical rules.

Threads

Long-lived token handling, text publishing, and supported media containers.

Reddit

Permanent OAuth grants with subreddit-aware text and link submission settings.

Pinterest

OAuth connection, continuous refresh, and board-aware Pin publishing foundations.

Bluesky

App Password exchange, encrypted sessions, image upload, and ordered reply threads.

Mastodon

Instance-specific OAuth configuration for federated publishing workflows.

WhatsApp

Meta WhatsApp Business connection, template sync, inbound events, media, and service-window messaging controls.

Telegram

Bot-authored channel or group posts with text, media groups, forum topics, and notification controls.

Discord

Bot publishing to selected server channels or forums with safe mention and attachment controls.

Credentials stay in the product you control

BlendDuck does not promise hosted developer apps. Operators configure the platform credentials and approvals required by the channels they enable.

Encrypted channel secrets

OAuth tokens and provider credentials are encrypted before persistence with the configured encryption key.

Capability-driven UI

Editors and settings surfaces reflect each provider's supported text, media, and publishing controls.

Explicit provider errors

Missing credentials, permissions, unsupported media, and terminal provider errors remain visible and actionable.

Start with one channel and keep the provider boundary clear

Add the credentials for a supported platform, connect an account, and publish through the same workspace your team reviews.