> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/readme.md). # Docupilot Help Documentation Docupilot is a document automation/generation software that allows you to create efficient document workflows for your business. ## Overview {% embed url="" %} **Docupilot** replaces manual filling in of repetitive documents with a template-based system which reduces the amount of time spent on generating the content manually and also human errors. With Docupilot, you can automatically create any business document, below are just a few documents widely used. * Proposals & Quotes * Contracts & Agreements * HR Documents * Educational Certificates * Purchase & Sales Orders * Invoices & Receipts * Real Estate Contracts & Rentals * Legal documents * Fillable PDF You can then send the auto-generated documents to your clients, partners or anyone through different delivery methods like emailing as attachments, sending it for digital signing, or storing it and even integrating with your favorite apps like SalesForce, Zoho CRM & Google Drive, Zapier, etc. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.docupilot.app/readme.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 `build a script that syncs our docs to a CMS` 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.