Skip to content
Nappai Documentation

Sub Flow

The Sub Flow component in Nappai helps you organize and reuse your automated workflows. If you’ve created a complex automation process, you can use Sub Flow to turn it into a smaller, self-contained component that you can easily add to other automations. This makes your workflows more efficient and easier to manage.

Relationship with Nappai Flows

This component directly interacts with Nappai’s Flow system. It takes an existing Flow (a sequence of automated actions) and transforms it into a reusable component. This means you can use the same pre-built process multiple times in different automations without having to recreate it each time.

Inputs

The inputs of a Sub Flow component are inherited from the original Flow it’s based on. This means the inputs will vary depending on the specific Flow you’re using. Essentially, the inputs are the data your original Flow needs to run correctly. You’ll see these inputs listed when you create a Sub Flow component.

Outputs

The Sub Flow component’s output is a new, reusable component. This component contains all the steps of the original Flow, ready to be used in other automations. The output of the new component will be the same as the output of the original Flow.

Usage Example

Imagine you have a Flow that automatically generates a sales report and sends it via email. Using the Sub Flow component, you can package this Flow into a reusable component. Then, you can easily add this “Generate and Send Sales Report” component to other automations, such as a monthly reporting process, without having to rebuild the report generation and email steps each time.

Templates

[List of templates where the component can be seen and its configuration] (This section requires information not provided in the original prompt)

This section lists some components that often work well with Sub Flow. They represent various actions you might include in your original Flows, which then become part of your Sub Flow component:

  • PGVector: For working with vector databases.
  • Speech to Text: For converting audio to text.
  • Scorer: For assigning numerical scores to data.
  • Categorizer: For classifying data into categories.
  • Describe Image: For generating descriptions of images.
  • Entities extraction: For extracting key information from data.
  • Summarizer: For summarizing text.
  • Google Drive File Manager: For managing files in Google Drive.
  • (And many more components listed in the original prompt, each with its own specific function within Nappai)

These are just a few examples; many other Nappai components can be incorporated into your Flows and subsequently packaged as Sub Flow components.

Tips and Best Practices

  • Keep it simple: Design your original Flows to be focused and efficient before creating a Sub Flow component. Smaller, well-defined Flows make for better reusable components.
  • Clear naming: Give your Sub Flow components descriptive names that clearly indicate their function.
  • Document your Flows: Add comments and descriptions to your original Flows to make them easier to understand and maintain.

Security Considerations

(This section requires more information about the specific security implications of the Sub Flow component and the data it handles. Without this information, a generic statement is provided.)

Ensure that the original Flows used to create Sub Flow components are secure and handle sensitive data appropriately. Review Nappai’s security best practices for more information.