> For the complete documentation index, see [llms.txt](https://docs.backupflows.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.backupflows.com/welcome/backup-flows.md). # Backup Flows Welcome to the official Backup Flows documentation. This documentation is designed to help you understand, configure, and use the Backup Flows system in a clear and efficient way. ### What you will find here * Setup and installation guides * Backup configuration instructions * Troubleshooting and common issues * Recommended best practices * Advanced features and technical references ### Getting started If you are new to Backup Flows, start with the installation guide and follow the setup steps in order. ### Support If you need help, you can: * Open a support ticket * Join our Discord community * Check the FAQ section ### Updates This documentation is updated regularly to reflect new features and improvements in Backup Flows. --- # 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.backupflows.com/welcome/backup-flows.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.