Now with real-time collaborative canvases

An agent that actually does the work.

Give it a job, a way to check its own logic, and the tools to follow through then watch it run, live, with your whole team in the room.

Amara
Theo
Priya
Kenji
Noor

Six pieces any shape workflow

No hidden logic every step in a run is one of these, sitting right on the canvas.

Start

Where every run begins.

Agent

Runs a model against your instructions and the conversation so far.

Condition

Checks what just happened and picks the next path.

HTTP Request

Calls a real endpoint and hands the response back to the workflow.

End

Marks where a run finishes and what it hands back.

Note

Leaves context for the next person who opens the canvas.

Everything a workflow needs nothing it doesn't

Six node types. One canvas. No separate tools for building, testing, and running.

Agents that call real tools

Connect an Agent node to an HTTP Request step and it can act, not just answer.

Branch on your own logic

Condition nodes route the workflow based on what happened in the step before.

Build with your team, live

See everyone's cursor moving on the same canvas, in the same moment.

Test before you ship

Chat with the workflow directly on the canvas — no separate staging step.

Scoped to your organization

Every workspace, workflow, and run stays inside your org — nothing crosses over.

Any model behind the scenes

Swap the model running your agents without touching a single node.

What happens when you hit send

A message comes in

Through the test panel, or wherever the workflow is triggered from.

01

The agent reads the graph

Every connected node's instructions become one system prompt, in order.

02

It can call a real step

An HTTP Request node becomes a tool the model can actually use.

03

You see the result

Streamed back in real time, with each tool call visible in the thread.

04

Your workspace is yours

Multi-tenant by design every workflow is scoped to your organization at the database layer, not just hidden in the interface.

One org, one boundary

Every workspace, workflow, and run belongs to a single organization — nothing crosses over, ever.

Checked on every request

Access is verified server-side on each call, not assumed from what the page shows you.

Built to fail closed

If something can't be confirmed as yours, you get a clear 'not found' — not a guess.

From empty canvas to working agent

01

Drop nodes on the canvas

Start, Agent, Condition, HTTP Request, End — click any of them into place.

02

Connect the path

Draw edges between nodes to define what happens after each step.

03

Chat with it, live

Open the test panel and talk to the workflow exactly as a user would.

Questions answered

A workspace holds one canvas — its nodes, edges, and the graph you save. The Free plan includes one; Pro removes the limit.

You pick a label per Agent node; the underlying model can change without touching your workflow.

Yes — every workspace is a live, collaborative canvas. You'll see teammates' cursors moving as they work.

Yes, if it's connected to an HTTP Request node, an Agent can call it as a tool during a conversation.

The test panel locks with a clear upgrade prompt — your saved workflow itself is never affected.

Your first workflow is free to build

One workspace, real agents, no card required.