> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/form-builder/creating-conditional-fields-in-a-form.md).

# Creating Conditional Fields in a Form

1. Add a **Single Choice** field, for example, “Are you currently employed?” with **Yes** and **No** options.
2. Add a **Short Text** field to ask for the company name.
3. Open the **Conditional** settings for the company name field and enable the condition.
4. Add a condition where the employment field **equals Yes**.
5. Add another field for users who select **No**.
6. Enable the **Conditional** setting for this field and add a condition where the employment field **equals No**.
7. Save and **Publish** the form.
8. Open the form link and test both options to verify that the relevant fields appear based on the user's selection.

{% embed url="<https://www.youtube.com/watch?v=r2Mv9rJRS-U>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/form-builder/creating-conditional-fields-in-a-form.md?ask=<question>&goal=<user_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.