ElpidanElpidanLead

Create reusable form and reusable Product Category by Another Flow Node

This video explains how the Another Flow Node works in Elpidan and why it is useful for reusable automation design. It shows how one flow can call another flow and continue after the called flow finishes.

****Here : movie 10****


In this tutorial, you learn how to use the Another Flow Node to avoid rebuilding the same logic again and again. This node helps you keep flows modular, easier to maintain, and more scalable.

 👉To explore the Action Node options in more detail, read the Another Flow Node guide

Reuse a Shared Form Flow

The first example focuses on a reusable form. Instead of rebuilding the same lead form in multiple flows, the form is moved into its own separate flow.

That form flow can remain without a configured trigger if it is intended to run only when called from another flow. This makes it an internal reusable component.

Check Completion Before Running the Form

Inside the reusable flow, a Condition Node checks whether the user already has the lead_form_completed tag. If the tag exists, the flow ends immediately and returns to the main flow.

If the tag does not exist, the reusable form collects the user’s details, assigns the completion tag, and then ends.

Return to the Main Flow

Once the reusable flow reaches its end, control automatically returns to the original parent flow. This allows the main flow to stay short and clean while still using all the logic stored in the reusable sub-flow.

Build Connected Category Flows

The second example shows another use case: product or service category structures. A main flow can display categories, and each category can connect to a separate flow using the Another Flow Node.

Inside each service flow, another button can send the user back to the main category flow. This creates connected navigation between a main category experience and individual detail flows.

Standalone and Internal Use

The video also explains that some flows can work in two ways. They can be called internally through Another Flow, and they can also run directly if they have their own trigger configured.

This makes the Another Flow Node useful not only for forms, but also for structured navigation and reusable automation patterns.

What You Learn from This Video

By the end of this tutorial, you will understand how to build reusable sub-flows, reduce duplicated logic, return safely to the main flow, and use the Another Flow Node to create modular automation systems in Elpidan.

Was this article helpful?

Didn't find your answer?

Contact us