> 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/deliveries/one-drive.md). # One Drive Save the generated documents in your OneDrive account. To add a OneDrive delivery, follow these steps: * Navigate to the '**Deliveries**' tab located in the top panel. * From the list of delivery options, select **OneDrive**. * Enter a name for the delivery. * Select your desired OneDrive account. If no OneDrive account is linked, click the "**+**" button and follow the on-screen instructions to add your OneDrive account. * Enter the name of the folder where you would like the generated documents to be uploaded.

**Advanced Settings:** If you like to get notified on delivery errors, or on successful execution of deliveries, configure advanced settings to take advantage of integrations. Following advanced integration options are available: * **On Success Callback URL** - Configure a Webhook URL which will be invoked with data containing the folder path to which the file was uploaded. * **Emails to notify on delivery failure** - Failed deliveries are typically notified to the workspace owner, workspace admins and workspace managers via email. You can configure additional email IDs here to receive notifications on delivery failures.

--- # 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://help.docupilot.app/deliveries/one-drive.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.