How to Automatically Convert Documents to PDF Using PDF.co and Zapier

Step 1: Prepare the Google Drive Folder

Create or select a Google Drive folder for the source documents.

Add a sample document to the folder so Zapier has a file it can use while testing the workflow. This tutorial uses a DOCX file, but you can select another supported format.

Step 2: Create the Zap

Sign in to Zapier and create a new Zap.

Select Google Drive as the trigger app and choose New File in Folder as the trigger event. This trigger runs when a file is created, moved, or uploaded directly into the selected folder.

Connect your Google Drive account when prompted.

Step 3: Configure the Google Drive Trigger

Configure the trigger:

• Drive: Select My Google Drive or the appropriate Shared Drive.
• Folder: Select the folder containing the documents you want to convert.
• Include Subfolders: Enable this if files added to subfolders should also trigger the Zap.
• Subfolder Depth Limit: If subfolders are included, specify how deeply Zapier should monitor them.
• Include Deleted Files: Leave this disabled for this workflow.

Test the trigger. Zapier should return a recent file from the selected folder.

Confirm that the test result includes a File property. PDF.co recommends mapping this property when processing files received from Google Drive.

Step 4: Add the PDF.co Action

Add an action and select PDF.co.

Choose Anything to PDF Converter as the action event. Connect your PDF.co account using your API key.

Step 5: Configure Anything to PDF Converter

Complete the following fields:

• Input Format: Select the option that matches the source file type.
• Input Source: Map the File property returned by the Google Drive trigger.
• Output PDF Name: Enter a filename such as converted-document.pdf. You can also map the original filename from Google Drive.
• Worksheet Index: For spreadsheet files, optionally enter the zero-based index of the worksheet to convert. Enter 0 for the first worksheet or leave the field empty to process all worksheets.
• Custom Profiles: Add PDF.co conversion settings only if the workflow requires advanced options.

The input format must correspond to the source file. If the monitored folder contains several unrelated file types, add Zapier filters or paths so that each format is processed with the correct settings.

Step 6: Test the Conversion

A successful response should include:

• A status code indicating success.
• The generated PDF’s filename.
• A temporary output URL.
• The date and time until which the URL remains valid.

Open the output URL and verify that the document was converted correctly.

Check the page layout, fonts, images, tables, and page breaks. Complex source documents may require additional conversion settings through the Custom Profiles field.

Step 7: Save the Generated PDF

PDF.co output URLs are temporary. Add a Google Drive Upload File action if the converted PDF must be retained.

Configure the action:

• Select the destination drive and folder.
• Map the PDF.co output URL into the file field.
• Map the PDF.co filename or provide another filename.
• Disable conversion to a Google Workspace document if you want to preserve the result as a PDF.

You can instead save the file to Dropbox, OneDrive, Box, or another storage service supported by Zapier.

Step 8: Publish the Zap

Run one final test of the complete workflow. Confirm that adding a supported document to the monitored folder produces and stores the expected PDF.

Publish the Zap when the test succeeds. New files added to the selected Google Drive folder will now be converted automatically.