> 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.md).

# Formsort quickstart guides

**Formsort gives you tons of flexibility to build a personalized experience for your responders—and it’s easy to experiment along the way.** Whether you’re adding dynamic content, tailoring questions, or tweaking logic, there are lots of tools at your fingertips.

Explore the guides below to get started:

* [Adding content and collecting answers ](/core-concepts/formsort-quickstart-guides/add-content-and-collect-answers.md)
* [Capturing demographic data ](/core-concepts/formsort-quickstart-guides/capture-demographic-data.md)
* [Adding informational content](/core-concepts/formsort-quickstart-guides/add-informational-content.md) 
* [Templating your variables](/core-concepts/formsort-quickstart-guides/template-your-variables.md)
* [Adding conditional logic](/core-concepts/formsort-quickstart-guides/add-conditional-logic.md) 
* [Using conditional logic with Calculated and API variables](/core-concepts/formsort-quickstart-guides/using-conditional-logic-with-calculated-and-api-variables.md)
* [Ending your flows](/core-concepts/formsort-quickstart-guides/end-the-flow.md) 
* [Reviewing the variable schema ](/core-concepts/formsort-quickstart-guides/review-your-variable-schema.md)
* [Setting up Integrations ](/core-concepts/formsort-quickstart-guides/set-up-integrations.md)

{% hint style="info" %}
💡 Want even more inspiration? Check out our guides on signup flow best practices and client intake form best practices for tips on crafting a polished, high-converting experience.
{% endhint %}


---

# 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.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.