> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/core-concepts/formsort-quickstart-guides/review-your-variable-schema.md).

# Review your variable schema

Manage the data you are collecting from responders and sending to your integrations.

As responders go through your flow, you will build up a **schema** of answer variables from them — either through answers they have given directly, or other methods. You can view and edit all of your variables in the Schema tab.

<figure><img src="https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJPnL__mOdr_mLZ8nwf%2Fuploads%2F2EyEk2bjbAC6lkoMmUIv%2Fimage.png?alt=media&amp;token=a63c3ba8-cf70-4bc8-be99-f547c69563ce" alt=""><figcaption></figcaption></figure>

### Types of variables:

* [Variables from questions:](/response-data-collection-and-management/variable-schema/variables-from-questions.md) Variables you collect from the responder directly when they answer a question. Examples: `first_name`, `dog_breed, pet_type`
* [Externally provided](/response-data-collection-and-management/variable-schema/external-answers.md): Variables you can pass through the URL of the flow. This can be helpful to add in information about the responder that they might not be able to answer directly, like their unique ID, or Common examples: `UTM source`, \`
* [API lookups:](/response-data-collection-and-management/variable-schema/api-answers.md) you can fetch a new answer from a server that returns JSON responses. This lookup can even use other variables collected with the flow as inputs or parameters. Examples are calling your own healthcare provider database, finding the nearest store location, or looking up current pricing.
* [Calculated inline](/response-data-collection-and-management/variable-schema/calculated-answers.md): Allow you to define new answers based on other answers present within the flow, by writing simple javascript functions that are evaluated within Formsort. A common example is calculating age from a responder’s inputted date of birth (see [here](/response-data-collection-and-management/variable-schema/calculated-answers.md#get-age-from-dob))
* [System library](/response-data-collection-and-management/variable-schema/system-library-answers.md): Variables you can collect about the responder's experience with your flow. Examples include: `current_step_id, is_mobile, is_returning_responder`.


---

# 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.formsort.com/core-concepts/formsort-quickstart-guides/review-your-variable-schema.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.
