Flow Builder Overview
The Flow Builder is where you create and manage automations in Elpidan. This page is designed as a hub, so instead of explaining every detail in isolation, it helps you understand the big picture and then move into the right detailed guides.
If you are new, start with Getting started section. If you want the full technical structure of flows, continue with the linked guides throughout this page.
👉 Read the full Getting started guide.
Go to Flow Menu from the main menu and click on "+New Flow" to open the Flow Builder
Understand the Core Structure
A flow is a visual sequence of steps (nodes) that starts when a user triggers an event on Instagram (message, comment, story reply, live comment). From that point, the flow can send messages, collect user input, check conditions, update contact data, and move the user through different paths.
👉 Read the full Flow Node Types Overview to understand the core building blocks
Every Flow Starts with a Trigger
Every flow in Elpidan starts with a Trigger. The Trigger defines how a user enters the automation. It is the entry point of the flow and decides which Instagram event should start the journey.
👉For a complete explanation of trigger types, keyword matching, and entry rules, read Trigger Node guide.
A Trigger can start a flow when:
· A user sends a direct message
· A user comments on a post or reel
· A user replies to a story
· A user comments during a live
What Happens After the Trigger?
Once the Trigger is activated, the flow continues through one or more connected nodes. Each node has a specific role. Some nodes send content, some collect data, and some control logic.
Node Types in Elpidan
Trigger Node
Starts a flow when a specific Instagram event occurs (such as a message, comment, or story reply) and a defined keyword condition is met.
Instagram Node
Sends content to users, including text messages, images, videos, voice messages, buttons, quick replies, and galleries.
Condition Node
Checks conditions based on tags, fields, follower status, or other data and directs the flow to different paths.
User Input Node
Asks a question and collects user input, saving the response into a field for later use.
Action Node
Updates contact data by adding or removing tags, setting or clearing field values, or performing system actions.
Delay Node
Pauses the flow for a defined amount of time before continuing to the next step.
Another Flow Node
Runs another flow from within the current flow and returns after it finishes.
How Nodes Are Connected
Flows are built by connecting nodes together in a sequence. Each connection defines where the user goes next. To understand handlers, node connections, and how flow paths are visually structured, read Understanding Nodes & Handlers.
A simple flow might look like this:
1. Trigger
2. Instagram Message
3. Action
4. End of flow
How Branches Are Created
Flows do not have to be linear. They can branch based on logic or user choice.
You can create branches using Condition nodes for logic-based paths, or by using Buttons and Quick Replies to let users choose their path.
· Condition-based branching: route users based on tags, fields, follower status, or other checks
· Choice-based branching: use buttons or quick replies to let the user decide the next path
What You Can Build in the Flow Builder
The Flow Builder supports both simple and advanced Instagram automations.
👉If you want to start building immediately, read Create First Simple Flow guide. If you want to understand how flows are organized and managed at scale, continue to Flow List & Management.
· A simple keyword-based DM automation
· A comment-to-DM flow that moves users into private conversations
· A lead collection flow that asks for a name, phone number, or email address
· A support or FAQ flow
· A multi-step onboarding flow with follow-up timing
· A reusable sub-flow that can be called from multiple automations
From Draft to Published
When you create or edit a flow, you usually work in Draft mode first. Once the flow is ready, you publish it and make it active. For the full explanation of how draft and published versions work:
👉 Read the full Draft & Published Flows guide guide.
How to Think About a Flow
A useful mental model is this:
5. The Trigger decides how the user enters
6. The connected nodes decide what the system does next
7. Conditions and user choices decide which path the user follows
8. Draft and Published status decide whether the flow is being prepared or already live
If you keep this structure in mind, the Flow Builder becomes much easier to understand. When you are ready to explore related data and conversation tools outside the Flow Builder itself, continue with:
👉 Read the full Inbox & Live Chat Menu guide guide.
👉 Read the full Contacts Menu guide guide.
👉 Read the full Tags Menu guide guide.
👉 Read the full Custom Fields Menu guide guide.
Was this article helpful?
Didn't find your answer?
Contact us