# ReachFlow Documentation > Official AI-readable documentation for ReachFlow by Mohuls Soft Limited. Canonical documentation: https://www.mohuls.com/reachflow/docs Product: https://www.mohuls.com/reachflow Application: https://reachflow.mohuls.com/ # ReachFlow documentation URL: https://www.mohuls.com/reachflow/docs ReachFlow brings brand context, AI content creation, media, schedules, connected social accounts, publishing checks, and day-to-day operations into one organized workspace. Start here if you are evaluating ReachFlow, preparing your first organization, onboarding a team, or learning how each part of the platform connects to the next. ## Start with the right guide The introductory path explains what ReachFlow is, how information moves through the product, the vocabulary used across the workspace, and the safest way to complete a first publishing workflow. You do not need to understand every feature before starting. Learn the core model first, complete a small real workflow, and then move into the feature-specific guides as they are added. ### What is ReachFlow? Understand the problem ReachFlow solves, its primary capabilities, and who it is designed for. /reachflow/docs/getting-started/what-is-reachflow ### How ReachFlow works Follow the complete path from organization context to a validated and published social post. /reachflow/docs/getting-started/how-reachflow-works ### Core concepts Learn organizations, AI Brains, connections, schedules, media, publishing states, credits, and MCP access. /reachflow/docs/getting-started/core-concepts ### Quick start Prepare an organization, connect a channel, create a schedule, review the result, and publish safely. /reachflow/docs/getting-started/quick-start ## The ReachFlow workflow ReachFlow treats social publishing as a connected operational system. Brand knowledge informs creation; creation produces drafts and media; schedules place that work in context; validation checks provider requirements; and publishing records the final result. 1. Create an organization and define the brand context. 2. Prepare the organization's AI Brain with approved knowledge and visual direction. 3. Connect the social accounts or custom destinations the organization is allowed to use. 4. Create weekday, calendar, or daily scheduling rules for the required channels. 5. Generate or write content and attach the correct media. 6. Review the content, permissions, media requirements, and publishing readiness. 7. Schedule or publish, then follow the activity and result inside ReachFlow. ## What you can manage The workspace is divided into focused operational areas. Each area keeps its own responsibility while sharing the same organization context and permission model. ### AI Brain Brand voice, audience, approved knowledge, goals, memories, and visual direction. ### Content and media Platform-ready copy, hashtags, visual prompts, generated images, and uploaded assets. ### Schedules and calendar Reusable weekday rules, daily work, calendar placement, and publishing timing. ### Publishing Connected providers, requirement checks, explicit approval, delivery, and status tracking. ### ChatGPT MCP Authorized content, media, scheduling, validation, and publishing actions through conversation. ### Teams and reporting Organization isolation, role-aware access, activity visibility, usage, and operational follow-up. ## Supported publishing destinations ReachFlow includes workflows for the major social networks used by modern teams. The exact publishing actions available to an organization depend on each provider's API, approved permissions, account type, media rules, and current platform policies. - Facebook Pages - Instagram professional accounts - Threads - X - LinkedIn profiles and organizations - TikTok - YouTube - Pinterest - Reddit - Signed custom API destinations > **Provider capabilities can differ:** A network may require a specific account type, review status, permission scope, media format, or user confirmation. ReachFlow exposes readiness information, but it cannot bypass a provider's rules. ## How to use this documentation Each page begins with the outcome it helps you achieve, then explains the concepts, prerequisites, safe workflow, and validation points. Use the left navigation to move between guides and the page outline to jump to a specific section. The documentation is being expanded feature by feature. The initial introduction establishes a reliable shared vocabulary so future guides can stay precise without repeating the same foundation. > **Begin with one real organization:** A small real workflow is more useful than configuring every feature at once. Prepare one organization, connect one permitted channel, create one reviewed post, and confirm the result before scaling the setup. ## Documentation roadmap Upcoming guides will cover AI Brain configuration, content generation, media management, schedule types, provider connections, publishing rules, ChatGPT MCP setup, teams, security, usage, billing, reporting, and troubleshooting in detail. New feature guides will be added to this same navigation and will receive their own server-rendered page, canonical metadata, structured data, sitemap entry, and previous or next relationship. --- # What is ReachFlow? URL: https://www.mohuls.com/reachflow/docs/getting-started/what-is-reachflow ReachFlow is an AI social media management and publishing platform built around an organization's real context—not an isolated prompt or a disconnected post generator. It helps teams move from brand knowledge to platform-ready content, media, schedules, validation, publishing, and operational visibility without rebuilding the same context for every channel. ## ReachFlow in one sentence ReachFlow is the operational workspace where an organization can preserve its brand context, create social content and media, plan when that work should appear, connect approved destinations, and publish with visible checks and control. ## The problem ReachFlow solves Social content often becomes fragmented across brand documents, prompt histories, image tools, spreadsheets, approval messages, platform dashboards, and manual reminders. The result is repeated context, inconsistent voice, unclear ownership, and publishing mistakes. ReachFlow connects those stages around one organization. The same approved context can support generation, review, scheduling, provider validation, and follow-up, making the workflow easier to repeat and audit. - Reduce repeated brand explanation across every prompt and draft. - Keep different organizations and clients isolated from one another. - Make schedules, drafts, media, publishing status, and failures visible in one place. - Prepare content for the requirements of each connected social provider. - Give teams and ChatGPT controlled access to the same operational context. ## Primary capabilities ReachFlow combines several related systems without treating them as unrelated tools. | Capability | What it contributes | | --- | --- | | Organization AI Brain | Approved knowledge, audience, voice, goals, memories, and visual direction. | | AI content creation | Channel-ready copy, hashtags, visual prompts, and generated media. | | Planning and scheduling | Weekday patterns, daily schedules, calendar placement, and timing. | | Publishing connections | Permission-aware delivery to supported social networks and custom APIs. | | Readiness validation | Checks for provider, account, media, and payload requirements before release. | | ChatGPT MCP | Conversational access to authorized ReachFlow creation and operational actions. | | Operational visibility | Activity, usage, queue state, publishing results, and issues that require attention. | ## Who ReachFlow is for ReachFlow can support a single growing brand, a structured marketing team, or an agency operating several client workspaces. The organization boundary keeps the system understandable at each size. ### Founders and growing brands Create a reliable publishing rhythm without restating the brand for every post. ### Marketing teams Keep strategy, creation, review, media, scheduling, and delivery in one shared workflow. ### Agencies Separate client knowledge, permissions, channels, media, calendars, and reporting. ### Content operators Turn approved context into repeatable, visible daily publishing work. ### Developers and connected teams Use the MCP server or signed custom API where ReachFlow needs to connect with another workflow. ## How ReachFlow differs from a general AI writer A general AI writer can produce text from a prompt. ReachFlow keeps the surrounding operating system connected: which organization the content belongs to, what that organization has approved, which channel will receive it, what media it needs, when it should run, whether the provider is ready, and what happened after delivery. The AI is therefore one part of the workflow rather than the entire product. Human review, provider permissions, scheduling rules, media requirements, and publishing records remain visible and controllable. > **ReachFlow does not remove provider rules:** Publishing still depends on the permissions, account types, rate limits, media rules, review requirements, and policies of each connected platform. ## What to read next Continue with How ReachFlow works to understand the full content lifecycle, then review Core concepts before completing the Quick start workflow. --- # How ReachFlow works URL: https://www.mohuls.com/reachflow/docs/getting-started/how-reachflow-works ReachFlow works as a connected lifecycle. Every stage receives context from the previous stage and produces information the next stage can validate or use. Understanding this lifecycle makes setup easier because it explains why organization data, connected accounts, schedules, media, and permissions must be prepared before reliable publishing can happen. ## The complete lifecycle The normal lifecycle begins with the organization and ends with a visible delivery result. Teams can enter the workflow manually inside ReachFlow or invoke permitted actions through the ChatGPT MCP connection. 1. Organization context identifies the brand, audience, goals, knowledge, and rules. 2. The AI Brain prepares that context for reliable content and visual generation. 3. A schedule or direct request defines the destination, timing, and content requirement. 4. ReachFlow creates or receives the draft, hashtags, visual prompt, and media. 5. The team reviews the content and makes any required edits or approvals. 6. Readiness checks compare the payload with connection and provider requirements. 7. The approved work is scheduled or published through the selected connection. 8. ReachFlow records the status so success, failure, and required follow-up remain visible. ## Organizations are the safety boundary An organization contains its own AI Brain, connected platforms, media, schedules, usage, and operational history. This boundary is essential for teams and agencies because it prevents one brand's knowledge or credentials from being used accidentally in another brand's work. Select the correct organization before generating content, attaching media, changing a schedule, connecting a provider, or authorizing an MCP action. > **Confirm the organization first:** A polished post in the wrong organization is still an operational mistake. Verify the organization, destination, and connected account before final approval. ## Schedules turn strategy into recurring work ReachFlow supports reusable weekday rules, calendar placement, and prepared daily schedules. Reusable rules describe the recurring rhythm; daily schedules represent the actual work for a specific date and time. A schedule can carry the platform, time, content direction, and related media context that generation and publishing need later. ## Validation happens before delivery Different providers require different account states, permission scopes, media formats, text limits, and publishing fields. ReachFlow checks the information it has before delivery and exposes missing requirements when the work is not ready. Validation reduces preventable failures, but the external provider remains the final authority and can still reject a request based on its current rules or account state. - Connection and authorization state - Selected destination and publishing identity - Required text or metadata fields - Media presence, type, size, and platform compatibility - Schedule timing and current workflow state - Available permissions and explicit user confirmation ## ChatGPT MCP uses the same controls The MCP server does not create a separate hidden workflow. It gives an authorized ChatGPT conversation access to selected ReachFlow operations through OAuth and scoped permissions. Content generation, media attachment, schedule management, readiness checks, and publishing still belong to the selected organization and remain subject to ReachFlow and provider controls. > **Conversation is the interface, not the authority:** The organization, permissions, connection state, provider rules, and explicit publishing confirmation remain authoritative even when the instruction begins in ChatGPT. ## Results stay visible Once an action runs, ReachFlow keeps the relevant state and activity visible. Teams can distinguish work that is prepared, scheduled, processing, published, failed, or waiting for correction instead of relying on memory or an external message thread. --- # Core concepts URL: https://www.mohuls.com/reachflow/docs/getting-started/core-concepts ReachFlow becomes easier to operate when every team member uses the same vocabulary. These concepts appear throughout the product and establish where data belongs and which controls apply. ## Organization An organization is the primary workspace and isolation boundary for a brand, business, or client. It owns the AI Brain, social connections, media, schedules, activity, usage, and related settings used by that brand. Agencies normally create a separate organization for each client. A company with distinct brands may also separate them when their knowledge, permissions, audiences, or channels should not mix. ## AI Brain The AI Brain is the prepared organization context ReachFlow uses during generation. It can include audience information, brand voice, goals, approved source knowledge, memories, visual direction, and other rules that shape output. Treat the AI Brain as maintained operational context. Review changes before they influence future content, especially when knowledge or memory can affect claims, positioning, tone, or visual direction. ## Platform connection A platform connection authorizes ReachFlow to work with a specific social provider and publishing identity. It represents real provider permissions, not only a saved platform name. Connections can expire, lose permissions, or require reauthorization. Publishing readiness therefore depends on both the saved ReachFlow configuration and the current provider state. ## Schedules, drafts, and calendar items A reusable schedule describes a recurring publishing rule, while a daily schedule or calendar item represents planned work at a particular time. A draft contains content that is not yet released. These objects are related but not interchangeable: the reusable rule defines rhythm, the dated item represents execution, and the draft holds the content and media that will be reviewed or published. | Concept | Purpose | | --- | --- | | Weekday schedule | A reusable rule for recurring content on selected days and channels. | | Daily schedule | The actual work prepared for a specific date, destination, and time. | | Calendar item | A visible planning record placed in the content calendar. | | Draft | Editable content and media that has not yet been published. | ## Media Media includes uploaded or generated images and other supported assets associated with an organization. Media should be attached to the correct draft and checked against the selected provider's requirements before publishing. The organization media library helps teams reuse approved assets without mixing files between clients or rebuilding the same creative context. ## Publishing state Publishing state explains where work currently sits in the operational lifecycle. Exact labels can vary by workflow, but teams should be able to distinguish preparation, review, scheduling, processing, success, and failure. - Draft or preparing: content is still being created or edited. - Ready: required content, media, connection, and checks are available. - Scheduled: the work is waiting for its configured publishing time. - Processing: ReachFlow or the provider is handling the request. - Published: the provider accepted the publishing action. - Failed or needs attention: something must be corrected or authorized before completion. ## AI credits and usage AI credits represent usage of eligible generation operations. Plans can include different credit allowances and organization, platform, or storage limits. Usage visibility helps teams understand consumption before it interrupts planned work. Publishing through a connected provider and generating AI content are separate operations, so a provider publishing failure does not automatically mean AI credits or generation were unavailable. ## ChatGPT MCP connection The ReachFlow MCP server exposes selected product capabilities to an authorized ChatGPT connection. OAuth identifies the user, scopes limit available actions, and the selected organization determines which ReachFlow context the conversation can use. Publishing and destructive actions require explicit confirmation. Never paste secret API keys into a normal prompt; use the secure MCP connection and ReachFlow authorization flow. --- # Quick start URL: https://www.mohuls.com/reachflow/docs/getting-started/quick-start This quick start takes a new team through one small, complete workflow. The goal is not to configure every feature; it is to prove that the organization context, connection, content, media, validation, and delivery path work together. ## Before you begin Choose one real organization and one social account you are authorized to manage. Keep the first workflow small so every stage can be checked clearly. - An active ReachFlow account with permission to create or manage an organization. - Accurate brand information, audience, voice, and approved source material. - Access to a supported social account with the provider's required account type and permissions. - One simple content goal and an approved media asset or visual direction. - A safe test date and time for scheduling or publishing. ## Complete the first workflow Work through the steps in order. Do not continue past a failed connection or readiness check. 1. Sign in to ReachFlow and create or select the correct organization. 2. Complete the organization profile and confirm its business context. 3. Prepare the AI Brain with audience, voice, goals, approved knowledge, and visual direction. 4. Connect one supported social account and approve only the permissions required for the workflow. 5. Create a direct draft or a schedule for one platform, date, and time. 6. Generate or write the content, then review the wording, claims, hashtags, and destination. 7. Attach suitable media and confirm that it meets the selected provider's requirements. 8. Run readiness validation and correct every blocking issue. 9. Schedule or publish with explicit approval. 10. Return to ReachFlow activity or schedule status and confirm the final result. ## Review before publishing A readiness check verifies technical conditions, but the human reviewer remains responsible for the meaning and appropriateness of the final post. - The correct organization and provider identity are selected. - The message matches the approved brand voice and current source knowledge. - Claims, links, dates, prices, and calls to action are accurate. - The media belongs to the organization and is permitted for this use. - The post is appropriate for the selected platform and audience. - The schedule uses the intended timezone, date, and time. > **Validation is not editorial approval:** Passing a technical readiness check does not verify business claims, legal rights, brand judgment, or campaign accuracy. A responsible reviewer should still approve the final content. ## Confirm the result After scheduling, confirm that the item appears at the intended time with the expected destination and status. After publishing, confirm that ReachFlow records success or clearly reports any provider error requiring attention. If the workflow fails, preserve the visible error context, check the connection and provider requirements, correct the blocking condition, and retry only when the state is understood. ## Scale only after the first success Once one workflow succeeds, add the next channel, reusable schedule, additional team member, or MCP connection gradually. This makes permission, content, and provider problems easier to isolate. > **A reliable small workflow is the baseline:** Use the first successful post as a reference for organization context, connection health, media preparation, review responsibility, and publishing verification before increasing volume. --- # Supported social platforms URL: https://www.mohuls.com/reachflow/docs/getting-started/supported-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. ## 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 | | --- | --- | | Facebook | Prepare and publish supported Page content, media, and related operational follow-up. | | Instagram | 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. | | LinkedIn | 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. | | Pinterest | Create visual Pin content for supported boards and publishing identities. | | Reddit | 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. ## Provider rules remain authoritative ReachFlow depends on official provider APIs and approved access. A feature can be limited by the provider's current API, the connected account type, the granted scopes, geographic availability, review status, or policy changes. > **Available actions can change:** Provider APIs evolve independently of ReachFlow. The connection screen and readiness result should be treated as the current operational source of truth for a specific account. ## 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.