Skip to main content

Subflow Editor

The Subflow Editor works the same way as the Flow Editor, but what you build here is a Subflow: a set of instructions grouped together so it can be used as a single block inside a main Flow.

Subflows let you bundle program logic into reusable snippets that can be used across all Flows, which reduces redundancy and keeps the main Flow readable.

In this section​

How a Subflow differs from a Flow​

  • There is no concurrency — branches do not execute in parallel inside a Subflow.
  • The same Subflow can be used within any other Flow, multiple times.
  • The Subflow Node waits for the Subflow to finish before it triggers its output.

Working with Subflows​

  • Create or select a Subflow directly from the Subflow Node in the main Flow, then press the pencil button to edit it here.
  • Define which output is triggered on completion with the Subflow Output Node. If none is set, Output 1 is triggered by default.
  • A Subflow starts from the Subflow Start Node.

A Subflow's UUID appears in the URL while you are in the Subflow Editor, for example http://192.168.3.1/subflow/0994c0e2-f43b-438f-87de-c3fcf1fd68cc/. That UUID is what a String Variable holds when you select a Subflow dynamically at runtime.