Altan's Flow Builders provide a suite of powerful modules that work together to enable dynamic and complex workflow automation. Some of these modules are interlinked, meaning they complement each other to create seamless processes. Understanding these relationships will help you build workflows more effectively.
π§ AI Agent#
What it does: Integrates AI agents to handle complex problems, providing intelligent decision-making within workflows.
When to use: For workflows requiring AI-powered reasoning, text generation, or data processing.
π² Router#
What it does: Splits your workflow conditionally, executing only the path of the first condition that matches.
Interlink: Works alongside the Brancher for advanced conditional paths, and the Octopus to merge split paths back together.
When to use: For workflows where only one path needs to execute.
π Brancher#
What it does: Splits your workflow into multiple paths, checking every condition and executing all that apply.
Interlink: Use the Octopus to reunite multiple paths after branching.
When to use: For workflows where multiple paths may need to execute simultaneously.
π Octopus#
What it does: Reunites multiple workflow paths into a single unified path.
Interlink: Essential when using Router or Brancher, as it consolidates their split paths.
When to use: To converge workflows after theyβve been split into separate branches.
π Iterator#
What it does: Processes collections by iterating over each element, applying actions one at a time.
Interlink: The Aggregator is required to combine the outputs of the iterator into a single collection.
When to use: For tasks that process each item in a list or array (e.g., sending emails to multiple recipients).
β Aggregator#
What it does: Merges outputs from an Iterator into a single collection (e.g., an array of processed data).
Interlink: Must be paired with an Iterator to work effectively.
When to use: To combine the results of iterated actions into one dataset.
π§βπ» Code#
What it does: Executes custom code in a sandboxed environment to perform specific tasks beyond the standard modules.
When to use: For advanced scenarios requiring custom logic or external API calls not natively supported.
π Set Variables#
What it does: Saves reusable variables for later steps in the workflow.
When to use: To avoid recalculating or re-fetching the same data multiple times, especially in workflows with cloned or repeated steps.
π― Invoke Flow#
What it does: Calls another workflow and passes custom data to it.
When to use: To create modular workflows or reuse a set of actions across multiple workflows.
π Response#
What it does: Enables the workflow to return a response payload, typically for API interactions.
When to use: For workflows that need to return data (e.g., webhooks or API integrations).
π Interlinked Modules: How They Work Together#
1.
Iterator splits a collection into individual elements for processing.
Aggregator then merges the processed results back into a single collection.
Example: Sending an email to a list of users and aggregating the delivery status of each.
2.
Router, Brancher, and Octopus:Router executes only one matching path, while Brancher can execute multiple paths simultaneously.
Octopus reunites these split paths back into a single workflow.
Example: Branching workflows to handle different user types, then converging all paths to finalize the process.
Modified atΒ 2025-07-28 16:00:26
