> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/flow-logic-graph/page-branching-graph.md).
# Page Branching Graph
Page branching allows you to define a set of [condition rules](/form-management/form-designer/condition-rules/conditions-rules.md) that will lead the respondent to go to a page of your choice if one or more of these rules are met.
The branching graph let you set and see all the rules that you have defined for your survey. You can either branch to another page, the end of the survey or redirect to an external website.
Setting a branching condition using the graph editor
If you want to display the branching graph of a page you can select that page in the Page flow tab to display only the branching logic starting from that page.
---
# 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.ngsurvey.com/form-management/flow-logic-graph/page-branching-graph.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.
