Nova Flow

Use Nova Flow from an AI app

Nova Flow speaks MCP, the standard way for AI apps such as Claude and Cursor to work with another service. Connect one and you can ask it about your automations, your runs, your accounts and your credits in plain words.

Connect in three steps

  1. Sign in, open Settings > AI & MCP, and ask the workspace owner to turn it on if it is not. MCP is available on every plan.
  2. Make a token there. Choose what it may do: read, create, edit. The token is shown once; copy it into your AI app.
  3. Add this server address to your app:
    https://flow.ochra.io/mcp
    In Claude Code:
    claude mcp add --transport http nova-flow https://flow.ochra.io/mcp --header "Authorization: Bearer YOUR_TOKEN"

What an AI app can do

These are the tools your connection can use, depending on its scopes and on what your workspace allows.

  • whoami — Says which workspace this connection is for, what role it acts with, what it may do, and which parts of the workspace it can reach. Call this first. (always available)
  • get_flow_guide — The rules an automation has to follow: the triggers, the kinds of step, and the limits on names, messages, buttons and menu options. Read this before describing or planning an automation. (always available)
  • list_automations — The workspace's automations, newest change first: name, status, trigger and which account it runs on. (Automations)
  • get_automation — One automation in full: its trigger, every step, the reply caps and the schedule. (Automations)
  • get_flow_schema — The JSON Schema for an automation's flow and for each trigger's settings. Read this before create_automation or update_automation, and build the flow to match it. (always available)
  • create_automation — Makes a new automation on one connected account. It is always created paused: turn it on with set_automation_status once you and the owner are happy with it. Check the shape with get_flow_schema first. (Automations, needs create)
  • update_automation — Changes an automation's name, trigger or steps. Send only what changes; a flow you send replaces the whole flow. It keeps its on or off state. Check the shape with get_flow_schema first. (Automations, needs edit)
  • set_automation_status — Turns an automation on (it starts replying to real people) or pauses it. Turning on follows the plan's limit on live automations and needs its account to be connected. (Automations, needs edit)
  • set_contact_tags — Replaces the tags on one contact. Tags are lower-cased and de-duplicated; up to 20, each up to 40 characters. (Contacts, needs edit)
  • list_runs — What the automations did, newest first: one row per conversation an automation took part in. (Activity and analytics)
  • get_run — A single run with each step it went through and how each one ended. (Activity and analytics)
  • list_accounts — The social media accounts connected to the workspace and whether each is healthy. Never includes access tokens. (Social media accounts)
  • list_contacts — People who have interacted with the connected accounts, with their tags. (Contacts)
  • get_credits — How many credits the workspace has, how they split between the monthly grant and bought credits, and what each action costs. (Credits)
  • list_comment_reviews — Comments the moderation policy looked at, what it decided, and whether it acted. (Comment policies)
  • list_support_tickets — The support tickets this workspace has raised, newest activity first. (Support)

Who is in control

  • You choose what a token may do. Read: look at things. changes nothing. Create: make new things, such as a draft automation or a support ticket. Edit: change what exists: rename, edit, switch on or off, tag.
  • The workspace owner decides whether AI apps may be used at all and which parts they can reach, and decides which roles may make tokens, on the same Role permissions page as every other part of the dashboard.
  • Roles apply. A token can only do what the role it acts as could do in the dashboard. Change a person’s role and their token follows immediately.
  • Nothing sensitive leaves. Social account access tokens, payment details and other workspaces’ data are never available to an AI app.
  • You can switch it off at any time. Revoke a token, or turn MCP off for the workspace, and the next request is refused.

Skills

A skill is a short set of instructions that teaches an AI app how to use Nova Flow well. Download one and put it in your app’s skills folder (for Claude Code, ~/.claude/skills/<name>/SKILL.md).

  • Plan an automation — Designs a comment, DM or story automation that fits the platform's real limits, using what your workspace already has.
  • Check on your automations — Finds out what ran, why a run failed, whether an account is healthy and how many credits are left.

Questions? Sign in and open a support ticket from your workspace.