Workflows

Anatomy of a workflow

A workflow stores two things: the nodes placed on the canvas, and the connections between them. That's it — no hidden state, no separate config file. What you see on the canvas is exactly what gets executed and exported.

• • Name & description — shown across the dashboard and marketplace.
• • Nodes — the building blocks, see Nodes.
• • Edges — the connections that route data from one node's output to another's input.
• • Workspace — who owns and can access the workflow.
• • Project (optional) — groups related workflows together.

Creating a workflow

There are three ways to start a new workflow:

• • From scratch — an empty canvas, ready for your first node.
• • Duplicate — copy an existing workflow, including all its nodes and edges.
• • From the Marketplace — import a published template as your starting point.

Organizing with projects & workspaces

As your work grows beyond a handful of workflows, two levels of organization keep things manageable:

• • Projects group related workflows — for example, every workflow behind one product.
• • Workspaces are the sharing boundary — invite collaborators as editors or viewers, and every project/workflow inside inherits that access.

You can mark any workflow as a favorite for quick access, or archive it once it's no longer active — archived workflows stay in your account but drop out of the main list.

Publishing to the Marketplace

Any workflow can be published as a reusable template — with a name, description, category and tags of its own — so other builders can import it as a starting point. Publishing doesn't affect your original workflow; you keep working on it and can push updates to the published template whenever you're ready.

Example: a "Create Order" workflow

A small e-commerce workflow that receives an order, saves it, and confirms it to the caller — the same example is used across Execution, Debugging and Environment Variables to show the same workflow from different angles.

API Endpoint  (POST /orders)
   ↓
Validation    (order body matches schema)
   ↓
SQL           (INSERT INTO orders ...)
   ↓
Response      (201, { orderId })

Four nodes, one straight line — no code written yet, and already testable from the builder.