Skip to content

Flow Node

Flow Node

Module ID: ion.action.flow

The Flow node executes another flow as a subflow, enabling modular and reusable flow design.

Overview

Use the Flow node to break complex automations into smaller, reusable components. A subflow receives input from the parent flow, executes its logic, and returns results back to the parent.

Handles

Input

Handle	Description
`input`	Data passed to the subflow

Outputs

Handle	Description
`output`	Result from the subflow
`error`	Subflow execution failed

Configuration

// node.data structure
{
  flow_id: string  // UUID of the flow to execute
}

Behavior

Receives input data
Loads the referenced flow by flow_id
Executes the subflow with input data as initial payload
Waits for subflow completion
Returns subflow result to output handle

graph TB
  subgraph Parent Flow
    A[Start] --> B[Flow Node]
    B --> C[Continue]
  end

  subgraph Subflow
    D[Trigger] --> E[Process] --> F[End]
  end

  B -.->|input| D
  F -.->|result| B

Example

Reusable Notification Flow

Parent Flow:

[Order Created] → [Process Order] → [Flow: Send Notifications]
                                     └→ [Complete]

Subflow “Send Notifications”:

[Trigger] → [Send Email] → [Send SMS] → [End]

Common Patterns

Modular Error Handling

[Main Flow] → error → [Flow: Handle Error] → [Log]

Reusable Integration Logic

[Order Flow] → [Flow: Sync to Shopify]
[Return Flow] → [Flow: Sync to Shopify]
[Update Flow] → [Flow: Sync to Shopify]

Best Practices

Keep subflows focused - Each subflow should do one thing well
Document inputs/outputs - Make clear what data the subflow expects
Handle errors - Connect the error handle in the parent flow
Avoid deep nesting - Limit subflow depth for debuggability

See Also