HomePricingIntegrations

Run another flow

Invoke a sub-flow from your current flow. Inputs from the parent are passed to the sub-flow; once the sub-flow finishes, its outputs are returned to this node and can be used by downstream steps.

I. Description

**Just apply with flow, have type = App

What it does

  • Calls a sub-flow synchronously during the parent flow’s execution.

  • Passes selected inputs (files, text, objects) from the parent to the sub-flow.

  • Waits for the sub-flow to complete, then exposes the sub-flow’s outputs on the Run another flow node.

When to use

  • You want to reuse a standardized mini-workflow (e.g., “Extract text from PDF”, “Normalize entities”, “Post to CRM”).

  • You want to decompose a large flow into smaller maintainable units.

  • Multiple teams/flows should share the same logic with one change point.

Concepts

  • Parent flow (Main flow): the flow you’re currently building; it contains the Run another flow node.

  • Sub-flow: a separate, reusable flow referenced by the parent. Its outputs are returned to the parent.

II. How to use

Step 1: Create Sub-flow

**Just apply with flow, have type = App

Please follow step - by - step

Create a flow with type = App

(1) At "Trigger node":

  • Switch toggle "Use this as a sub-flow" to Enable

(2) Add another node to the flow (3) Publish the Sub-fllow

Rule

Case
Rule

(1) Sub-flow compatibility with restricted nodes

A flow that is marked as a sub-flow must not use the following nodes:

  • “Branch”

  • “Loop”

  • “Delay”

  • “Run another flow”.

(2) Flow is already marked as sub-flow, user adds a restricted node

  • Trigger: User tries to add any of the restricted nodes to a flow that has Sub-flow enabled.

  • Behavior: Block the action and show an inline error toast/banner on the canvas.

  • Error message (exact): This node is not available in sub-flow

(3) Flow already contains a restricted node, user turns on Sub-flow

  • Trigger: User toggles Sub-flow on in a flow that currently contains at least one restricted node.

  • Behavior: Do not allow enabling. Keep the toggle off/disabled.

  • Hover tooltip over the disabled toggle (exact text): This flow cannot be marked as a sub-flow if nodes "Run another flow", "Branch", "Delay", "Loop" are being used

(4) Unmarking a published sub-flow

Rule: If a flow is already marked as sub-flow and has been published, unmarking it must require explicit confirmation.

Behavior

  • Trigger: User turns off the Sub-flow toggle on a published sub-flow.

  • Action: Show a Confirm modal.

  • Modal copy (exact): Do you want to disable this sub-flow. It might be used as a sub-flow in another flow

  • Options:

    • Confirm → proceed to unmark; downstream flows that reference this sub-flow should surface a warning on next open/run.

    • Cancel → keep Sub-flow enabled; no changes applied.

Step 2: Create Parent flow (Main flow) and refer to the sub-flow

**Just apply with flow, have type = App

Please follow step - by - step

Create a flow with type = App

(1) Build new flow

(2) Add "Run another flow" node

Component settings

Parameter Name
Description

Select a flow

Select a sub-flow Rule:

  • Must be in the same workspace AND

  • The sub-flow must be set to public

Field Input

Show the fields input of the Sub - Flow

Advance configurations

On Error when running Run another flow

Single - select: - Stop workflow (default value) - Skip and record error

Step 3: Run Parent flow (Main flow)

When finish setup the Parent flow (main flow) -> Click button "Execute" to run the flow

After run the flow, at the output of "Run another flow" node will response the data of Sub-flow

III. History

View from the Parent flow (Main-flow)

When run success the parent flow, user can view the history

The history list, the user can click to view the details

At Tab "Workflow", the user clicks details of the "Run another flow" node

Will display the "Sub-flow name" and "Sub-flow ID"

User can click on the "Sub-flow name" -> The system will open a new tab and redirect to the workflow builder of the Sub-flow

View from the Subflow

When run success the parent flow, user can view the history of the subflow

At the History list, with the record run via Parent-flow, at the column VIA will show the value "Parent flow"

User can click to view the details

At detail page

Will display the "Parent-flow name" and "Parent-flow ID"

User can click on the "Parent-flow name" -> The system will open a new tab and redirect to the workflow builder of the Parent flow

Last updated

Was this helpful?