> For the complete documentation index, see [llms.txt](https://docs.zellify.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zellify.app/platform-introduction/funnel-builder/flow-system.md).
# Flow System
The Flow System lets you visualize how users move through your funnel and define how pages connect to each other.
It allows you to create conditional paths, route users to different pages, and show different questions or content based on how users interact with the funnel.
### Flow Canvas
The Flow page displays a canvas where you can pan and zoom to view the entire funnel structure.
Each page in the funnel is shown as a node. Pages are connected by lines that represent the path a user will follow after completing a page. By default, funnels use a simple horizontal flow with no conditional routing.
***
### Conditions and Routing
You can create conditional routing by hovering over a connection line and clicking **Add**.
This opens a condition editor where you define rules that are evaluated when the user proceeds to the next page. Based on these rules, users can be routed to different pages.
Conditions can reference:
* Any question
* Any answer
* Any user input collected before the condition is evaluated
Multiple rules can be combined to create more advanced routing logic.
***
### Personalization
The condition system enables deep personalization.
You can tailor the funnel experience by showing different pages, questions, or offers based on user intent, preferences, or previous answers. This makes it possible to create highly targeted flows instead of a single linear experience.
***
### Resetting the Flow
If the flow becomes complex or breaks due to incorrect routing, you can reset it at any time.
The reset button in the bottom-right corner restores the funnel to a simple horizontal flow without any conditions or custom routing.
***
### Common Use Cases
The Flow System is commonly used for:
* Routing users into different paths based on their answers
* Showing or skipping questions dynamically
* Presenting different value propositions
* Displaying personalized paywalls based on user intent
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.zellify.app/platform-introduction/funnel-builder/flow-system.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
