# Open-source workflows for humans and AI agents · Open Flow

Source: https://openflow.run/en/

OPEN SOURCE · AGENT READY

# From an idea  
to a running flow.

Build with an AI agent. Refine on a visual canvas. Run on infrastructure you choose. One workflow, from first draft to live automation.

[Start building](https://openflow.run/en/quickstart/)[Watch the demo](https://www.youtube.com/watch?v=CIF5I11VpLM)

Apache-2.0oo flowBeta

Open Flow / Workbench

![The real Open Flow Workbench: a Gmail-to-Feishu workflow, with execution results.](https://openflow.run/_astro/workbench-overview.DEKyma8B_Z2j1kus.webp)

The real Open Flow Workbench: a Gmail-to-Feishu workflow, with execution results.

01 / BUILD WITH YOUR AGENT

## Describe the work. Keep the workflow.

Your terminal agent can discover actions, create typed nodes, check a draft, run it, and publish it. Every change appears in the same visual Workbench.

[Install oo CLI](https://github.com/oomol-lab/oo-cli)

oo flow⌘

**❯**Read my unread Gmail messages, summarize them, and send the summary to Feishu.

01 / Draft

02 / Check

03 / Run

04 / Live

Works through oo flow with Codex, Claude Code, and other terminal agents. Publishing happens when you ask.

02 / UNDERSTAND EVERY CONNECTION

## The graph is how it runs.

Named, typed inputs and outputs make every data dependency explicit. Nodes run when their inputs are ready; independent branches can run concurrently.

![Named, typed inputs and outputs make every data dependency explicit. Nodes run when their inputs are ready; independent branches can run concurrently.](https://openflow.run/_astro/typed-node-details.BtJOC4f3_26lxso.webp)

![Visual where it helps. Code where it counts.](https://openflow.run/_astro/code-task-editor.D-RBNMP6_1WyMVO.webp)

### Visual where it helps. Code where it counts.

Write custom JavaScript in Code Tasks with declared inputs, outputs, and capabilities. The server runs each code task in a fresh V8 isolate.

![Connect services. Keep credentials separate.](https://openflow.run/_astro/connector-actions.gIc61q4i_1Y7uas.webp)

### Connect services. Keep credentials separate.

OpenConnector handles provider credentials and actions. Open Flow stores opaque connection identities, keeping your workflow and account authorization separate.

[OpenConnector](https://openconnector.io/)

## From a single run to daily automation.

Start manually, on a Cron schedule, through a Webhook, by polling, or from Provider events. Inspect node outputs and the event history of every run.

CronWebhookPollProvider event

03 / CHOOSE YOUR DEPLOYMENT

## Your flow. Your place to run it.

The same Workbench and versioned Control API, whether you use OOMOL or run your own deployment.

### OOMOL Hosted

Start without operating a server. OOMOL manages the deployment and OAuth apps for supported integrations.

[Use OOMOL Hosted](https://oomol.com/)

### Docker

Run the included server on your infrastructure. You own storage, backups, upgrades, and connector setup.

[Quick start](https://openflow.run/en/quickstart/)

### Fly.io

Deploy the same image with TLS and a persistent volume. You manage secrets, backups, upgrades, and connector setup.

[Fly.io](https://github.com/oomol-lab/open-flow/blob/main/docs/server/fly-io/README.md)

Open Flow is in beta. Contracts are versioned; the first stable release is still ahead.

## Give your next idea a workflow.

Start with the hosted service or run Open Flow on your own infrastructure.

[Use OOMOL Hosted](https://oomol.com/)[View on GitHub](https://github.com/oomol-lab/open-flow)