Supported social platforms
ReachFlow connects one organization workflow to several social destinations. Each provider has its own authorization model, content formats, publishing rules, review requirements, and API limitations.
Use this page as an orientation. The provider-specific guides added later will document detailed connection and publishing steps for each network.
On this page
Platform overview
ReachFlow prepares content inside one organization-aware workflow while preserving the differences between destinations. A single campaign idea can produce platform-specific drafts, but each final payload must satisfy the selected provider.
| Destination | Typical ReachFlow workflow |
|---|---|
| Prepare and publish supported Page content, media, and related operational follow-up. | |
| Prepare media-led posts or supported professional-account publishing workflows. | |
| Threads | Create concise platform-ready posts and supported reply-oriented content. |
| X | Prepare text and supported media posts within provider and account limits. |
| Create professional content for supported member or organization destinations. | |
| TikTok | Prepare video-focused publishing workflows subject to TikTok permissions and media requirements. |
| YouTube | Prepare supported video publishing and comment-related operations. |
| Create visual Pin content for supported boards and publishing identities. | |
| Prepare community-aware posts for authorized destinations and supported workflows. | |
| Custom API | Send a signed payload to an approved external destination when a custom workflow is required. |
Connections and permissions
A connection is usable only while its provider authorization remains valid and includes the permissions required for the intended action. Some platforms require professional or organization account types, app review, administrator access, or renewed authorization.
ReachFlow can show saved connection state and perform readiness checks, but the provider can change or revoke access independently.
Content is adapted per destination
Cross-platform planning does not mean publishing identical payloads everywhere. Text length, link behavior, hashtags, aspect ratio, media count, video rules, titles, descriptions, boards, communities, and publishing identity can differ.
- Preserve the campaign idea while adapting the final message to the destination.
- Use the correct media type, dimensions, duration, and file limits.
- Confirm whether the destination accepts links, hashtags, mentions, or multiple media items in the intended form.
- Review the account and audience context before reusing a draft across platforms.
- Run final provider readiness checks after every platform-specific change.
Custom API delivery
A signed custom API destination supports workflows where social networks are only one part of a larger content operation. The receiving system must verify the signature, validate the payload, protect credentials, handle retries safely, and report failures clearly.
Custom delivery should be configured only by teams that control or trust the destination and understand the security and data-handling responsibilities involved.