Skip to content
Nappai Documentation

Sub Flow

The Sub Flow component lets you run another flow that you have already created in Nappai.
You just pick the flow you want to execute, and the component will handle all the details for you.

How it Works

When you drop the Sub Flow component onto your dashboard, it first asks you to choose a flow name from a list of flows that exist in your Nappai account.
Once you select a flow, the component:

  1. Loads the chosen flow’s definition.
  2. Looks at all the inputs that the flow expects.
  3. Adds those inputs as new fields in the Sub Flow component so you can provide values for them.
  4. Runs the flow with the values you supplied (or with any tweaks you add).
  5. Collects the results that the flow produces and returns them as a list of data items.

All of this happens inside Nappai, so you don’t need to write any code or call external APIs.

Inputs

  • Flow Name: The name of the flow you want to run.
    This field lets you pick which pre‑built flow will be executed.

Outputs

  • Flow Outputs: A list of data items that the selected flow produced.
    Each item contains the result of a step in the flow and can be used by other components in your dashboard.

Usage Example

  1. Drag the Sub Flow component onto your canvas.
  2. In the Flow Name field, select Customer Onboarding.
  3. The component will automatically add new input fields for the onboarding flow (e.g., “Customer Email”, “Plan Type”).
  4. Fill in those values or connect them to outputs from other components.
  5. Run the dashboard.
  6. The Flow Outputs will contain the onboarding results, which you can feed into a “Send Email” component or store in a database.
  • Flow Builder – Create and edit the flows that Sub Flow can run.
  • Data Input – Provide static or dynamic values that can be passed to Sub Flow.
  • Data Output – Store or display the results that Sub Flow returns.

Tips and Best Practices

  • Keep flow names short and descriptive so you can find them quickly.
  • Use the “Tweaks” field to override specific inputs without editing the flow itself.
  • Test a flow independently first; then use Sub Flow to embed it in larger workflows.
  • If a flow has many inputs, consider creating a separate “Input” component to keep the Sub Flow panel tidy.

Security Considerations

  • Sub Flow runs entirely within the Nappai environment, so it inherits the same security settings as your other components.
  • If the underlying flow accesses external services (e.g., APIs, databases), ensure those connections are secured with proper authentication and permissions.
  • Avoid exposing sensitive data in flow inputs unless the flow is designed to handle encryption or masking.