Build your first workflow

This walkthrough uses the Order router template. It is built from rules only, so it needs no connected app and no AI key, and it runs on the Free plan. It checks an order, routes it by size, holds large orders for a moment and then records the order by calling a webhook.

Create a project

Open the Projects page.
Press New project.
Enter a name, such as “Orders”, and an optional description.
Press Create. The project’s page opens.

Start a workflow from a template

On the project’s page, press New workflow.
Enter a name, such as “Order router”.
Under Start from, choose Order router. The list starts on AI debate, which needs an agent.
Press Create. The builder opens with the template’s diagram as your draft.

The builder has three parts: the node library on the left, the canvas in the middle and a panel on the right. Select a node on the canvas to see its settings in the panel’s Step tab. See The builder for the full tour.

Read the diagram

Node	Type	What it does
New order	Trigger	Starts the run with a payload, such as `{"customer": "ACME", "amount": 750}`.
Valid order?	Conditional	Continues only if `{{trigger.amount}}` is greater than 0.
Route by size	Decision	Takes Large (≥ 500) or Standard (< 500) depending on the amount.
Hold for review	Delay	Waits 3 seconds. Only large orders pass through it.
Record order	Notification	Sends a webhook with the customer, the amount and the chosen route.

The {{ }} parts are template variables. {{trigger.amount}} reads the trigger’s payload, and {{nodes.route.selectedBranch}} reads the output of the node with the id route. See Templates and variables.

Run the draft

Open the Test tab in the right panel. The template’s sample payload is already filled in.
Press Run draft in the header, or Run draft with this payload in the tab.
Click a step in the run’s list, or a node on the canvas, to see its input and output.

Running saves the draft first, then switches the panel to the Runs tab. Each node on the canvas shows its status and how long it took, and the edges the run followed are highlighted.

Each output field is labeled with the name later steps use to read it. Route by size shows nodes.route.selectedBranch with the value Large (≥ 500). Record order shows nodes.record.status, the HTTP status the webhook answered.

Try the other paths

Change the payload in the Test tab and run the draft again.

With {"customer": "ACME", "amount": 200}, the run takes the Standard branch. Hold for review is marked skipped, because no edge into it fired.
With {"customer": "ACME", "amount": 0}, Valid order? is false. Nothing after it runs, and every later step is marked skipped.

Publish version 1

Press Publish in the header. Super Flows saves the draft, checks it, and freezes it as version 1. A message reads “Version 1 is live”, and the status next to the workflow’s name changes from Draft to Live · v1. The dashboard’s setup step “Build and publish a workflow” is now done.

If a node needs fixing, publishing is refused with a message that names the node, and that node’s panel opens. Fix it and press Publish again.

From now on, editing the draft doesn’t change what runs. The live version keeps running unchanged until you publish again. See Versions and publishing.

Let it run without you

Run draft always runs the draft. The live version starts from its trigger:

With the Manual trigger this template uses, the live version starts through the API. See Starting runs.
To run it on a timetable, select New order, set Type to Schedule, choose when it repeats, and publish again.
To run it when something happens in an app, set Type to App event. This needs a connected app.

See Triggers for each kind. To see every run of the workflow, open More in the builder’s header and choose Full history.

Where to go next

Add an Agent step for work that needs judgment.
Connect an app and add an Action step.
Browse the other workflow templates.