Ask AI
Skip to main content

Subflow

Function: Subflow​

The "Subflow" action allows you to create a self-contained block of actions within your main workflow. Think of it as a mini-workflow that you can define and manage separately. This is incredibly useful for organizing complex processes, making your main workflow easier to read, and reusing common sequences of actions across different parts of your application.

Input​

This function does not require any direct inputs. It acts as a container or a structural element within your workflow.

Execution Flow​

The "Subflow" action helps you structure your workflow by grouping related steps. When your main workflow reaches a "Subflow" block, it executes all the actions defined within that subflow before continuing with the rest of the main workflow.

Real-Life Examples​

Here are some examples of how you can use the "Subflow" action to organize and streamline your no-code applications:

Example 1: Automating Customer Onboarding​

Imagine you have a detailed process for onboarding new customers, involving multiple steps like creating a user account, sending a welcome email, assigning a customer success manager, and scheduling a follow-up.

  • Inputs: None for the "Subflow" action itself. (The individual actions within the "Onboard Customer" subflow would take inputs like "New Customer Details").
  • Result: You create a "Onboard Customer" subflow that contains all these steps. Your main workflow simply calls this subflow whenever a new customer signs up, keeping the main flow clean and making the onboarding process easily manageable and reusable.

Example 2: Handling Data Validation​

Before saving any user-submitted data to your database, you often need to perform several validation checks (e.g., ensuring email format is correct, checking if required fields are filled, verifying data against existing records).

  • Inputs: None for the "Subflow" action itself. (Actions inside the "Validate User Input" subflow would take inputs like "User Form Data").
  • Result: You create a "Validate User Input" subflow that includes all your validation actions. Any workflow that receives user input can then use this single subflow to ensure data quality, centralizing your validation logic and making it consistent across your application.

Example 3: Processing Payment Transactions​

A payment transaction might involve steps like charging the customer's card, updating the order status, recording the transaction in a ledger, and sending a payment receipt.

  • Inputs: None for the "Subflow" action itself. (Actions within the "Process Payment" subflow would take inputs like "Payment Amount", "Customer ID", "Card Details").
  • Result: You define a "Process Payment" subflow that encapsulates all these actions. This allows any part of your application (e.g., an e-commerce checkout, a subscription renewal, a manual payment entry) to trigger the entire payment process with a single, clear step, ensuring all necessary actions are performed reliably.