> 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/publishing-and-deployment/preflight-checklist.md). # Pre-deployment checklist Check all the boxes below to guarantee a healthy flow! To ensure a high-quality flow, make sure you... ### **Flow health** * semantic names for your [**answer variables**](/response-data-collection-and-management/variable-schema.md). * set [**readable descriptions**](/response-data-collection-and-management/variable-schema.md#readable-description) for your answer variables. * set [**data classifications**](/response-data-collection-and-management/variable-schema.md#available-data-classifications) for your answer variables. * set **Step IDs** for all your steps, especially if you’re using any analytics integrations. * set [**savepoints**](/integrations/getting-data-out/submission-frequencies.md#on-savepoint), if the submission frequency for any integrations is **On savepoint**. ### Hosting * set [**custom hostnames**](/workspace-management/custom-domains.md). * add [**DNS records**](/workspace-management/custom-domains.md#step-2-add-dns-records-to-your-domain-hosting-provider) to your domain hosting provider. * set [**default environments**](/publishing-and-deployment/environments.md#creating-new-environments), for any custom domains. * if embedding your flow, set **Allowed embedding domains.** ### Integrations * enable [**integrations**](/integrations/integration-reference.md) across [environments](/publishing-and-deployment/environments.md). * set the appropriate [**submission frequency**](https://docs.formsort.com/handling-data/getting-data-out/submission-frequencies) for any data integrations. * configure the [**events**](/integrations/getting-data-out/analytics.md) for any analytics integrations. * confirm that the schema in your [**BigQuery**](/integrations/integration-reference/bigquery.md) account is configured correctly. * set [**Allowed webhooks domains**](/integrations/integration-reference/webhooks.md), if you’re integrating with Webhooks. * [**re-deployed flows**](https://docs.formsort.com/handling-data/environments#saving-and-propagating-changes), after updating your integrations. ### Responder behavior * set [**Returning responder behavior**](/form-behavior-settings/variant-settings/returning-responder-behavior.md). * [**override Next button text** ](/adding-questions-and-content/content-reference/next-button.md)to include ex. ‘submit.’ * set [**step-level redirects**](/redirects-and-endings.md#redirects). * set flow-level [**default redirects**](/redirects-and-endings.md#redirects). * set **URL fallbacks** for any redirects with dependencies. ### Testing * tested the retrieval of submission data on staging or custom [**environments**](https://docs.formsort.com/handling-data/environments). * set **default URL params**, especially if testing on non-production environments. * tested endpoints accessed by [**API Variables**](/response-data-collection-and-management/variable-schema/api-answers.md). * tested endpoints used to [**populate dynamic choices**](/adding-questions-and-content/question-reference/select.md#dynamic-choice-loading). * **handled CORS restrictions** for any endpoints you're accessing. * tested [**branching paths**](/conditions-and-logic.md) logic. * tested [**calculated variables**](/response-data-collection-and-management/variable-schema/calculated-answers.md)**.** * tested [**styles**](/styling/customizing-appearance.md) across devices and browsers. * tested [**redirects**](/redirects-and-endings.md), especially those including any variables in the query parameters. * tested all enabled [**integrations**](/integrations/integration-reference.md)**.** * tested your published flow in incognito mode, or your browser's equivalent. --- # 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/publishing-and-deployment/preflight-checklist.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.