Skip to content
Nappai Documentation

Sub Project flow

The Sub Project flow component lets you run an existing project flow inside your current workflow.
It pulls in all the inputs that the sub‑flow expects, so you can reuse that flow without having to rebuild it from scratch.

How it Works

When you add this component, you give it the name of a flow that already exists in Nappai.
The component then loads that flow, passes the values you provide for its inputs, and runs it.
After the sub‑flow finishes, the component returns whatever data the sub‑flow outputs.
Everything happens locally inside Nappai, so no external services are called.

Inputs

Input Fields

  • Flow Name: The name of the flow you want to run.
    Enter the exact name that appears in the flow list.

Outputs

  • Flow Outputs: The data produced by the sub‑flow.
    This is the result you can feed into other components in your main workflow.

Usage Example

  1. Create a sub‑flow called Customer Data Processor that takes a customer ID and returns a report.
  2. In your main workflow, add a Sub Project flow component.
  3. Set Flow Name to Customer Data Processor.
  4. Connect the customer ID from a previous component to the Flow Name input.
  5. Use the Flow Outputs to display the report or pass it to another component.

Now, whenever the main workflow runs, it will automatically execute the Customer Data Processor flow and use its results.

  • SubFlowInternalComponent – The underlying component that powers Sub Project flow.
  • Flow Runner – A component that runs a flow by ID instead of name.
  • Data Mapper – Helps connect outputs from one component to inputs of another.

Tips and Best Practices

  • Double‑check the flow name for typos; the component will not run if the name is wrong.
  • Keep the inputs of the sub‑flow simple and well‑documented so you know what data to provide.
  • Test the sub‑flow on its own first to ensure it behaves as expected before embedding it.
  • If the sub‑flow changes, update the main workflow to match any new input or output names.

Security Considerations

  • Sub‑flows run in the same environment as the main workflow, so any sensitive data they handle must be protected by Nappai’s standard security settings.
  • Avoid passing confidential information through the Flow Name field; it is only a text identifier.
  • Ensure that any outputs from the sub‑flow are sanitized before being displayed or stored.