Another Flow Node

Instead of continuing within the same flow, Elpidan:

1. Jumps into a second flow (the sub-flow)
2. Executes that flow from its start
3. Returns back to the original flow when the sub-flow ends

This enables modular automation design.

👉 learn about what is Flow Builder

What the Another Flow Node is used for

• Reusing logic across multiple flows
• Keeping flows short and readable
•  Centralizing common actions (welcome messages, qualification steps, follow checks, and reusable data-collection forms that can be called from multiple flows)

Reusable Flows & Modular Design

Large automations quickly become hard to manage if everything lives in one flow.
Sub-flows solve this by enabling modular design.

What is a reusable flow?

A reusable flow is a flow that:

• Has a clear purpose
• Can be triggered by Another Flow Node
• Is designed to run as part of a larger automation

Common examples:

• Lead qualification logic
• Smart follow gating
• Welcome or intro sequence
• Data validation or cleanup
• Data-collection forms

Benefits of modular design

Using sub-flows helps you:

• Avoid duplicated logic
• Update behavior in one place
• Reduce errors
• Keep the main flow easy to read

Example:

• 5 different flows need a follow check
• Instead of copying the logic 5 times:
• • Create one “Follow Check” flow
  • Call it using Another Flow Node

Sub-flows can be triggered or trigger-less

A flow that is used as an Another Flow (sub-flow) can be designed in two ways:

Option 1: Trigger-less sub-flow (internal-only)

A sub-flow can have no Trigger configured.

In this case:

• The flow will never run automatically
• Users cannot enter it directly from Instagram
• The flow can only run when it is called from another flow using an Another Flow node

This is the recommended approach for:

• Shared data-collection forms (name, email, phone)
• Follow-check modules
• Qualification steps used in multiple flows

Option 2: Triggered sub-flow (can run standalone too)

A sub-flow can also have a Trigger configured (with required keywords).

In this case:

• The same flow can run in two ways:
• 1. As a sub-flow when called via Another Flow
  2. As a standalone automation when its Trigger is activated (for example, when a user sends a message matching its keywords)

👉Read the full Trigger Node guide

Returning to the Main Flow Safely

After a sub-flow finishes, Elpidan returns execution to the original flow and continues from the next connected node.

How return behavior works

• The parent flow waits while the sub-flow runs
• Once the sub-flow reaches its end:
• • Control returns to the parent flow
• The next node after Another Flow is executed

This makes sub-flows feel like functions in programming.

Safe return patterns
Recommended pattern:
Parent flow calls sub-flow
Sub-flow performs its task
Sub-flow ends cleanly
Parent flow continues

Common mistakes to avoid
❌ Infinite loops
Flow A calls Flow B
Flow B calls Flow A