> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reviewing-and-exporting/cloud-storage-and-auto-export.md). # Cloud storage integrations and auto-export Connect Google Drive, Dropbox, Box, Microsoft 365, Clio or Zoho WorkDrive, export a request's files into organized folders, and set up auto-export. Connect a cloud storage account and Pipefile can put a request's files straight into it, organized by checklist item. You can export by hand whenever you like, or turn on auto-export so each file lands in your storage as soon as you accept it. {% hint style="info" %} Connecting cloud storage and exporting by hand are available on every plan. **Auto-export** and **Zapier** are available on the **Professional** and **Enterprise** plans. {% endhint %} ## Supported services | Service | What you can export to | | ------------------ | ---------------------------------------------------------------------------------- | | **Google Drive** | My Drive and shared drives | | **Dropbox** | Your Dropbox folders | | **Box** | Your Box folders | | **Microsoft 365** | OneDrive, and SharePoint document libraries you can access | | **Clio** | Your Clio documents, in the United States, Europe / UK, Canada or Australia region | | **Zoho WorkDrive** | Your WorkDrive folders | ## Connect an account Only a team admin can connect a storage account. Once connected, everyone on your team can export to it. {% stepper %} {% step %} ### Open Integrations Go to **Integrations & Apps** in your settings, at . {% endstep %} {% step %} ### Connect Select the service's connect button, such as **Connect to Google Drive** or **Connect to OneDrive** (for Microsoft 365). For Clio, pick your region first. You can connect more than one Clio region. {% endstep %} {% step %} ### Sign in and allow access Sign in to the service and approve Pipefile's access. You return to Pipefile and see **Account Connected!** {% endstep %} {% endstepper %} To remove a connection, select **Disconnect** on the service's card. For Clio, select **Manage Connections** and choose the region. {% hint style="warning" %} If your Google Drive connection expires, Pipefile shows **Google Drive Authentication Required** on the Integrations page. Connect again to keep exporting. {% endhint %} ## Export a request by hand {% stepper %} {% step %} ### Open Export On the request page, select **Export** above the file list (it's also in the **More options** (…) menu). Pick your connected service from the list. If nothing is connected yet, select **Add integration**. {% endstep %} {% step %} ### Choose a folder Select **Choose Folder** and browse to the destination. Pick a folder rather than the top level of the drive, then select **Choose Folder**. For Google Drive, Pipefile opens Google's own file picker. {% endstep %} {% step %} ### Add subfolders (optional) Select **+** next to the destination to add a subfolder to the path. You can type a custom name or use a variable that's filled in from the request (see the table below). Pipefile creates any folders that don't exist yet. {% endstep %} {% step %} ### Export Select **Export Documents**. You'll see **Export in process!** and get an email with a link to the destination folder when it finishes. If the export fails, you get an email saying so. {% endstep %} {% endstepper %} ### Folder variables | Variable | Filled in with | | --------------- | ---------------------------------------- | | `{{name}}` | The primary recipient's name | | `{{subject}}` | The request subject | | `{{user_name}}` | The request owner's name | | `{{date}}` | The request's creation date (YYYY-MM-DD) | | `{{datetime}}` | The request's creation date and time | | `{{tag0}}` | The request's first tag | For example, a path of `Clients / {{name}} / {{date}}` gives every recipient their own folder. ### How exported files are organized Inside the destination, Pipefile creates a folder for each checklist item, inside a folder for each section if your checklist has sections. Each file goes into its item's folder. Rejected files are not exported. Files that were already exported to the same place are skipped, so exporting again only sends what's new. To check a single file, select the export history icon next to it on the request page. It shows whether the export completed, failed or is still pending, and where it went. ## Export when you mark a request complete The **Mark completed** dialog includes a destination picker. Choose a folder there and Pipefile exports the request as it closes. If the request already has a destination, it's filled in for you. ## Auto-export {% hint style="info" %} Available on the **Professional** and **Enterprise** plans. {% endhint %} With auto-export, you don't have to export at all. Set a destination when you create or edit a request, and Pipefile exports each file a few seconds after you accept it: * Accepting a file in a [file review](/reviewing-and-exporting/understanding-reviews.md) exports it. * Approving a checklist item or marking it incomplete accepts its files, so they're exported too. * Rejecting a file that was already exported deletes the exported copy from your storage. To set it up, open **Send Request** or **Edit Request** and choose a folder with **Choose Folder** in the destination picker above the advanced options. The request page then shows the destination under **Exports to**. If your plan doesn't include auto-export, the form shows **Upgrade to Professional to enable auto-exports**, and you can still export by hand. Auto-export doesn't send a confirmation email for each file. You get an email only if an export fails. ### Save a destination on a template Set an export destination on a [template](/templates/create-and-edit-templates.md) and every request you send from it uses the same destination and folder path. Folder variables make this work for every recipient: a template path of `Clients / {{name}}` puts each recipient's files in their own folder. ## Zapier {% hint style="info" %} Available on the **Professional** and **Enterprise** plans. {% endhint %} Zapier connects Pipefile to thousands of other apps without code. Select **Connect to Zapier** on the Integrations page to browse ready-made Zaps for Pipefile. To build your own integration instead, see the API Reference section. ## Related * [Download and export to PDF](/reviewing-and-exporting/download-and-pdf-export.md) * [Understanding reviews](/reviewing-and-exporting/understanding-reviews.md) * [Send from a template](/templates/send-from-a-template.md) --- # 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://support.pipefile.com/reviewing-and-exporting/cloud-storage-and-auto-export.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.