Browse docs

Get Started with Flow

Flow is OOMOL’s workflow automation product. AI agents and people create and edit the same typed workflow through oo flow and Workbench. OOMOL Flow is the official hosted path; Open Flow is the open-source, self-hosted path.

Choose a deployment

Open Workflows in OOMOL Console for the official hosted version. OOMOL operates the deployment and provides managed OAuth apps for supported integrations.

Use Open Flow to operate the runtime on your own infrastructure. You manage persistent storage, tokens, networking, backups, upgrades, and any Connector or OAuth setup. Open Flow is in beta; it has not reached its first stable release.

Build a first Flow

  1. Install oo CLI for an agent that can run terminal commands.
  2. Choose the deployment to use, and connect the accounts required by your task.
  3. Ask the agent to create a Draft, check it, run it, and inspect the outputs.
  4. Open that same Flow in Workbench to review the graph and code. Publish to Live only when you are ready to enable the automation.

Build a workflow that reads unread Gmail messages, formats them, and sends them to Feishu.

This is the task shown in the Open Flow repository demo. Successful execution depends on the required accounts, permissions, and configured host capabilities.

Connect oo CLI to your own Open Flow

In the shell used by the agent, set the URL and operator token for your Open Flow deployment. The token must match the deployment’s configured OPEN_FLOW_TOKEN.

export OO_OPEN_FLOW_URL="https://flow.example.com"
export OO_OPEN_FLOW_TOKEN="<your-open-flow-operator-token>"

Follow the Open Flow, OpenConnector, and oo CLI deployment guide for the complete setup. A self-hosted Open Flow does not require an OOMOL account or oo login; authentication and external services depend on your deployment.

Understand the Connector boundary

Open Flow can run without a Connector. Tasks that call external Apps and Provider Triggers require a configured Connector runtime. That Connector stores provider credentials and executes Actions; Flow stores connection identities. A self-hosted OpenConnector requires your own provider OAuth apps when OAuth is used.

Next steps

Read the Flow product overview to compare the hosted and self-hosted paths. For account authorization and tools, see OpenConnector and access control.