Skip to content

AUTOMATE · FLOW ENGINE

Automation that survives real operations.

Compose flows on a visual canvas from twelve node types, drop agents into the graph, and run them on a durable engine that retries, routes errors, and rolls back. Watch every run land, node by node.

THE CANVAS

Twelve node types on a visual canvas.

Code in Python, JavaScript, or TypeScript. Human input, loops that fan out over batches, subflows, delays, webhook waits, decision rules, and record mutations.

Wire them on a canvas — no orchestration boilerplate, no glue services to maintain.

flow · canvas
trigger
code · py
decision
loop · batch
record
Webhook
Triage Mission
triage
support-triage-agent
Done14 · $0.42
5/5 · 100%
  • Classify new tickets
  • Draft suggested replies
  • Tag priority & route
  • Update the board
+1 more
Update board

AGENTS INSIDE THE FLOW

Drop an agent into the graph.

An agent-session node streams its work right on the canvas as the run proceeds. A mission node is goal-locked: it must return a schema-valid deliverable before the DAG moves on.

The same governed agent you bind to a screen becomes a step in an automated pipeline.

DURABLE BY DESIGN

Runs on Temporal. Built to recover.

The engine executes on Temporal, so runs are durable: retry policies, error envelopes that route to an error output, and saga-style compensation when a step must be undone.

Every published version is a snapshot. A schema diff shows what changed between versions, and rollback is one action.

Runs on Temporal. Compensation built in.

retry policy error output compensation versioned snapshot rollback
Live · v3 Draft · v4
RUN TIMELINE
run · v3 · #1187
nodestatusms
trigger done 4
code · fetch done 212
decision done 9
agent · summarize running
record · update queued

WATCH IT RUN

See the run land, node by node.

The live canvas lights its edges by node status as the run proceeds. A per-node Gantt timeline, streaming logs, and per-node IO trees show exactly where time went.

Compare two runs side by side to see what diverged.

TRIGGERS

Start it however operations start.

Run on a leader-elected cron, on an authenticated webhook, on a record-change event with a filter, or on demand. The trigger is a node like any other.

Cron

Leader-elected schedule

Webhook

Authenticated inbound

Record change

Filtered event

Manual

On demand

Compose it, govern it, and let it recover on its own.

The flow engine runs your automation the way real operations demand — durable, observable, and with your governed agents inside it.