Workflow compose tool

Workflow Builder

Drag generic automation nodes onto a canvas, connect them, and export a JSON sketch—useful for scoping flows before you pick a platform.

How to use this builder

Sketch an automation as a platform-agnostic graph — compose steps, connect them, and export JSON for handoff or discussion.

  1. Drag nodes onto the canvas

    Pull entry points, logic, and actions from the left panel onto the canvas. Each node is a generic building block — not tied to a specific automation platform.

  2. Connect the flow

    Drag from an output port (right side of a node) to an input port on another node. Click an edge to select it; press Delete to remove it.

  3. Configure steps

    Fill in fields and descriptions on each node. Use Condition nodes to build AND/OR rules with values or variables.

  4. Navigate the canvas

    Pan by dragging empty space, zoom with the mouse wheel or the bottom-right controls, and use Fit all to frame every node.

  5. Export or reset

    Export JSON downloads a simple nodes-and-edges sketch you can share or refine later. Load example restores a sample pipeline; Clear canvas starts over.

Workflow Builder FAQ

What is the Workflow Builder for?
It is a sketching tool for automations. You lay out triggers, logic, and actions as generic nodes so you can agree on how a process should run before committing to a platform such as n8n, Make, or Zapier.
Do I need an account, and is my sketch uploaded anywhere?
No account is needed. The builder runs entirely in your browser and nothing you compose is sent to a server; exporting simply downloads a JSON file to your device.
What does the exported JSON contain?
A simple nodes-and-edges description of what you drew, including each node type, its fields, and the connections between nodes. It is meant for sharing and discussion, not for execution.
Can I import the export into n8n or Make?
Not directly. The nodes are platform-agnostic, so the file is a design sketch rather than a platform-native workflow. Use it as the blueprint when you rebuild the flow in your automation tool.
When is sketching a workflow first worth the time?
When more than one person has to agree on a process, when a flow has branching rules, or when you are scoping work before pricing it. A shared diagram surfaces missing steps and edge cases earlier than building does.