> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pdf.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating File Sources with PDF.co

> Supercharge your **Make** workflows by seamlessly integrating with leading file storage services like **Google Drive**, **Dropbox**, **OneDrive**, and **Box**. This guide meticulously outlines how to use these services in harmony with **PDF.co**’s **Make** plugin, enhancing your document management capabilities.

Supercharge your **Make** workflows by seamlessly integrating with leading file storage services like **Google Drive**, **Dropbox**, **OneDrive**, and **Box**. This guide meticulously outlines how to use these services in harmony with **PDF.co**'s **Make** plugin, enhancing your document management capabilities.

## URL Accessibility for PDF.co

<Info>
  The API supports TLS 1.2 and 1.3 for secure connections. Earlier versions such as TLS 1.0 and 1.1 are deprecated and should be avoided.
</Info>

For successful integration, any publicly accessible URL can be used. Whether you're using services like Google Drive, Dropbox, or others, ensure the URLs are accessible to PDF.co. We recommend using **Make.com**-generated URLs (detailed in the sections below) as they are guaranteed to be compatible with PDF.co. If you're using direct URLs not provided via Make.com, please verify their public accessibility to ensure PDF.co can process your files efficiently.

## Google Drive

Effortlessly integrate **Google Drive** into your workflows:
\- Set up a **Google Drive** Trigger to `Watch Files in a Folder`
\- Follow with **Google Drive**'s `Download a File` action to fetch file binary data for subsequent steps.
\- Use the acquired data as input for **PDF.co** actions.

Here's the complete scenario with all steps:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-google-drive-input-source-whole.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=8774ea16ced39cc9282c3a8591febf5c" alt="Google Drive - Whole scenario" width="1491" height="514" data-path="images/integrations/make/make-google-drive-input-source-whole.png" />
</Frame>

In the `Download a File` step, utilize the `File ID` from the Trigger as shown below:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-google-drive-input-source-downloadfile.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=5da2cffa7a6284c4c7ea41c5c5d6e2bb" alt="Google Drive - Download a File Step" width="1291" height="519" data-path="images/integrations/make/make-google-drive-input-source-downloadfile.png" />
</Frame>

Finally, feed the data from `Download a File` into your **PDF.co** action:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-google-drive-input-source-pdfco.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=946beacb2f54e7d21a8d131f80967daa" alt="Google Drive - PDF.co Utilization" width="1341" height="727" data-path="images/integrations/make/make-google-drive-input-source-pdfco.png" />
</Frame>

## Dropbox

Integrate **Dropbox** with ease:

* Start with the **Dropbox** Trigger to `Watch Files`.
* Add **Dropbox**'s `Download a File` action for acquiring file data.
* Direct this data into **PDF.co**'s action steps.

Visualize the entire flow:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-dropbox-input-source-whole.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=b6f099907daff4f0d5f3ff4cc80782b3" alt="Dropbox - Whole scenario" width="1405" height="490" data-path="images/integrations/make/make-dropbox-input-source-whole.png" />
</Frame>

When setting up `Download a File`, use `Path lower` from the Trigger:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-dropbox-input-source-downloadfile.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=ab72ec6e6c11d3e9f914bf91962af1f1" alt="Dropbox - Download a File Step" width="1259" height="553" data-path="images/integrations/make/make-dropbox-input-source-downloadfile.png" />
</Frame>

The data from `Download a File` now serves as input for **PDF.co** actions:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-dropbox-input-source-pdfco.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=0135c5c36e1d5c807cfa11f685a41c5e" alt="Dropbox - PDF.co Utilization" width="1287" height="603" data-path="images/integrations/make/make-dropbox-input-source-pdfco.png" />
</Frame>

## OneDrive

Integrating **OneDrive** is straightforward:

* Use the **OneDrive** Trigger to `Watch Files/Folders`.
* Proceed with **OneDrive**'s `Download a File` action.
* Channel the downloaded data into **PDF.co**'s functionalities.

Here's the setup in its entirety:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-onedrive-input-source-whole.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=a3a011cbc290eff64294c078b5c1a3b5" alt="OneDrive Input Source" width="1398" height="503" data-path="images/integrations/make/make-onedrive-input-source-whole.png" />
</Frame>

Configure `Download a File` using `Item ID` from the Trigger:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-onedrive-input-source-downloadfile.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=6b64571e035304f2551195bb1f9523b3" alt="OneDrive Input Source" width="1279" height="704" data-path="images/integrations/make/make-onedrive-input-source-downloadfile.png" />
</Frame>

Finally, use the `Download a File` data as input for **PDF.co**:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-onedrive-input-source-pdfco.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=fc7223d187bafafe192021c67a71d24c" alt="OneDrive Input Source" width="1246" height="555" data-path="images/integrations/make/make-onedrive-input-source-pdfco.png" />
</Frame>

## Box

Follow these steps for **Box** integration:

* Set the **Box** Trigger to `Watch Files`.
* Use **Box**'s `Download a File` action to obtain file data.
* This data is then ready for use with **PDF.co** actions.

View the full integration process:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-box-input-source-whole.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=4b8a7c02fd78e9a394f32aac18de1bd6" alt="Box Input Source" width="1226" height="447" data-path="images/integrations/make/make-box-input-source-whole.png" />
</Frame>

In `Download a File`, fill in the `File ID` using the Trigger's output:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-box-input-source-downloadfile.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=ba3e23dad5f74073e177aca92d3eb030" alt="Box Input Source" width="1019" height="406" data-path="images/integrations/make/make-box-input-source-downloadfile.png" />
</Frame>

The data from `Download a File` is now primed for **PDF.co** actions:

<Frame>
  <img src="https://mintcdn.com/pdfco/jvNpJlS3eEFjK2tL/images/integrations/make/make-box-input-source-pdfco.png?fit=max&auto=format&n=jvNpJlS3eEFjK2tL&q=85&s=01d16479b7bf5402744a9412da6b0691" alt="Box Input Source" width="946" height="433" data-path="images/integrations/make/make-box-input-source-pdfco.png" />
</Frame>

***
