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

# Publishing and Deployment

- [Live preview overview](https://docs.formsort.com/publishing-and-deployment/preview-window.md): See the current state of a flow without deploying.
- [Environments](https://docs.formsort.com/publishing-and-deployment/environments.md): Configure integrations.
- [Loading different environments](https://docs.formsort.com/publishing-and-deployment/environments/setting-the-environment.md)
- [Embedding](https://docs.formsort.com/publishing-and-deployment/embedding.md): Place Formsort flows within a larger webpage.
- [Web-embed API](https://docs.formsort.com/publishing-and-deployment/embedding/web-embed-api.md): Embed your flows within other webpages, with communication between the embed and the parent page
- [React-embed](https://docs.formsort.com/publishing-and-deployment/embedding/web-embed-api/react-embed.md): Embed Formsort flows within react components.
- [Embedding forms in iOS and Android](https://docs.formsort.com/publishing-and-deployment/embedding/embedding-in-ios-and-android.md): Manage forms in native applications from Formsort
- [Setting up a dev environment](https://docs.formsort.com/publishing-and-deployment/embedding/setting-up-a-dev-environment.md): Troubleshoot your embed before going live
- [Pre-deployment checklist](https://docs.formsort.com/publishing-and-deployment/preflight-checklist.md): Check all the boxes below to guarantee a healthy flow!


---

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