Flows

Flows is a visual workflow builder for creating multi-step AI pipelines. Drag integrations onto a canvas, wire them together, and run — no code required.

How it works

Open Flows from the sidebar
Click + New or describe a flow in the text box
Drag integrations onto the canvas and wire them together
Configure each integration in the properties panel
Click Run to execute the flow

Integration types

Every step in a flow is an integration. There are 10 kinds:

Kind	Icon	Purpose
Trigger	⚡	Event that starts the flow — webhook, cron, or user input
Agent	🤖	AI agent processing step — sends a prompt and gets a response
Tool	🔧	MCP tool invocation — call any connected tool
Condition	🔀	If/else branch — route data based on expressions
Data	📊	Data transform — map, parse, format, convert
Code	💻	Inline JavaScript — sandboxed execution with `input`/`context`
Output	📤	Terminal step — log, send, store, or post to chat
Error	⚠️	Error handler — catches failures from upstream integrations
Group	📁	Sub-flow — compound integration containing nested steps
Event Horizon	🌀	Synchronization barrier — collects outputs from parallel tesseract cells before continuing

Edge types

Edges connect integrations. Four kinds control data flow direction:

Edge	Meaning
Forward	Normal `A → B` — data flows from source to target
Reverse	Pull `B ← A` — target requests data from source
Bidirectional	Handshake `A ↔ B` — two-way data exchange
Error	Fallback `A --err→ B` — routes to error handler on failure

Building flows

Canvas controls

Action	How
Pan	Click and drag the canvas background
Add integration	Click an add button in the toolbar, or type in the text box
Select	Click an integration on the canvas
Move	Drag a selected integration
Connect	Drag from an output port (right side) to an input port (left side)
Delete	Select an integration or edge, then press the delete button
Zoom	Scroll wheel on the canvas

Text-to-flow

Type a natural-language description in the text box at the top and press Enter. The parser recognizes keywords and creates a flow automatically:

webhook → agent summarize → if important → send email

Keyword detection maps words to integration types:

Keywords	Maps to
`trigger`, `webhook`, `cron`, `on`, `when`	Trigger
`agent`, `ai`, `llm`, `ask`, `think`	Agent
`tool`, `mcp`, `call`, `api`, `fetch`	Tool
`if`, `condition`, `branch`, `check`	Condition
`data`, `transform`, `map`, `parse`	Data
`output`, `send`, `email`, `notify`, `save`	Output

Properties panel

Click any integration on the canvas to open its configuration panel:

Label — display name on the canvas
Description — sub-label (model name, tool ID, etc.)
Kind — integration type (trigger, agent, tool, etc.)
Config — kind-specific settings:
- Agent: prompt text, assigned agent (dropdown of your real agents)
- Code: inline JavaScript with input and context variables
- Condition: expression to evaluate
- Tool: MCP tool name and parameters

When no integration is selected, the panel shows flow properties — name, description, folder, and stats.

Folders

Flows can be organized into folders:

Open flow properties (click canvas background)
Set the Folder field (e.g. Production, Drafts)
Flows are grouped by folder in the sidebar with collapsible headers

Drag and drop flows between folders in the sidebar.

Templates

Switch to the Templates tab in the sidebar to browse pre-built flow patterns.

Category	Examples
AI & Agents	Daily Digest, Multi-Agent Debate, Agent Chain
Communication	Email Auto-Responder, Team Notifications
DevOps & CI	Deploy Pipeline, Health Monitor
Productivity	Task Triage, Meeting Prep
Data & Transform	CSV Pipeline, Data Enrichment
Research	Deep Research, Literature Review
Social & Content	Content Calendar, Social Listener
Finance & Trading	Portfolio Monitor, Price Alerts
Support	Ticket Router, FAQ Bot
Custom	Build your own from scratch

Search & filter

Type in the search box to filter by name, description, or tags
Click a category chip to filter by category
Click All to reset

Execution

Running a flow

Select a flow from the sidebar
Click the Run button (▶) in the toolbar
Watch integrations execute in order — status indicators show progress:
- 🔴 Running — red breathing pulse
- 🟢 Success — sage green border
- ❌ Error — red border
- ⏸ Paused — gold oscillating border

Data flows along edges with animated signal sweep.

Debug mode

Step through a flow one integration at a time:

Click the Debug button (🐛) in the toolbar
Set breakpoints by right-clicking integrations
Use Step to advance one integration at a time
Inspect intermediate data values shown on edges
View the debug inspector panel for full input/output of each step

The execution cursor highlights the current integration with a gold ring.

Error handling

Error edges route failures to error handler integrations
Error integrations catch and process failures (log, alert, retry)
The flow report in chat shows step-by-step results with timing

Scheduling

Flows can run on a schedule using cron expressions:

Open a flow’s properties panel
Enable the Schedule toggle
Enter a cron expression

9 * * *       Every day at 9 AM
*/2 * * *     Every 2 hours
9 * * 1-5     Weekdays at 9 AM
*/30 * * * *    Every 30 minutes

The scheduler checks every 30 seconds for flows due to fire. The hero stat counter shows how many flows have active schedules.

Code integrations

Code integrations run sandboxed JavaScript:

// Available variables:
// input  — output from the previous integration
// context — { flowId, nodeId, runId }

const data = JSON.parse(input);
return data.items.filter(item => item.score > 0.8);

Code runs in a sandboxed Function() constructor — no access to DOM, fetch, or filesystem
Return value becomes the integration’s output, passed to downstream integrations
Timeout enforced to prevent infinite loops

Chat reporter

When a flow runs, a flow report appears in the chat conversation showing:

Flow name and step count
Progress bar
Each step’s status, duration, and output
Final summary with success/error counts and total duration

Conductor Protocol

The Conductor is an automatic optimization layer that analyzes flow graphs before execution. When the graph contains parallelizable structures, the Conductor compiles an ExecutionStrategy with optimized units:

Primitive	What it does
Collapse	Merges a sequence of non-branching nodes into a single execution unit
Extract	Isolates a node with no internal dependencies for early execution
Parallelize	Runs independent branches concurrently via `Promise.all`
Converge	Waits for all parallel branches to finish before continuing
Tesseract	Orchestrates parallel cells across phase and depth, synchronized at event horizons

The Conductor activates automatically when a flow has 4+ nodes, any parallel branches, or a mix of agent and non-agent nodes. No manual configuration is needed. → Deep dive: Conductor Protocol reference

Tesseract flows

A tesseract flow partitions the graph into independent cells — sub-graphs that share no data edges between them. Each cell executes its agents in topological order, and all cells run in parallel. An event horizon node acts as a synchronization barrier, collecting outputs from every cell via mergeAtHorizon before the flow continues. Tesseract flows are detected automatically when the graph contains 2+ disconnected agent clusters separated by non-agent boundaries.

Memory integration

Before any node executes, the flow executor pre-recalls relevant long-term memories from the Engram memory system. Agent nodes receive these memories in a [Relevant Memory] section in their prompts. In tesseract flows, each cell gets its own cell-scoped memory — resolved from the cell’s specific agent prompts — so parallel cells never race on shared memory state. → Deep dive: Memory guide

Persistence

Flows are stored locally in localStorage under key openpawz-flows
All data stays on your machine — no cloud sync
Export/import via JSON serialization

Keyboard shortcuts

Key	Action
`Delete` / `Backspace`	Delete selected integration or edge
`Escape`	Deselect all

Core

Integrations

Workflows

Tools

Platform

Flows

Flows

How it works

Integration types

Edge types

Building flows

Canvas controls

Text-to-flow

Properties panel

Folders

Templates

Categories

Search & filter

Execution

Running a flow

Debug mode

Error handling

Scheduling

Code integrations

Chat reporter

Conductor Protocol

Tesseract flows

Memory integration

Persistence

Keyboard shortcuts

​Flows

​How it works

​Integration types

​Edge types

​Building flows

​Canvas controls

​Text-to-flow

​Properties panel

​Folders

​Templates

​Categories

​Search & filter

​Execution

​Running a flow

​Debug mode

​Error handling

​Scheduling

​Code integrations

​Chat reporter

​Conductor Protocol

​Tesseract flows

​Memory integration

​Persistence

​Keyboard shortcuts

Flows

How it works

Integration types

Edge types

Building flows

Canvas controls

Text-to-flow

Properties panel

Folders

Templates

Categories

Search & filter

Execution

Running a flow

Debug mode

Error handling

Scheduling

Code integrations

Chat reporter

Conductor Protocol

Tesseract flows

Memory integration

Persistence

Keyboard shortcuts