Automating Google Docs to PDF with Make.com: Step-by-Step Guide

Introduction

If your team still manually copies data from Google Sheets into a Google Docs template and then exports a PDF for sharing, you know the pain. It’s slow, error prone, and hard to audit. The moment data changes, you risk rework and miscommunication. This post shows how to build an end to end pattern in Make.com that outputs a polished PDF from a Google Docs template, stores it in Drive, and sends it to the recipient with a single, repeatable workflow.

By the end you will know how to trigger from Google Sheets, fill a Docs template with data, convert the result to PDF, save the PDF to Google Drive, and deliver it via email. No more manual copy paste or frustrating version drift.

Note: No related posts found for this exact Google Docs to PDF Make.com pattern. If you’ve seen similar docs, you’ll still find this version practical for production use.

What You'll Need

• A Make.com account with Google Docs, Google Drive and Gmail connections
• A Google Docs template containing placeholders such as {{ClientName}}, {{Date}}, {{Amount}}
• A Google Sheet or other data source with columns that map to the placeholders
• A Google Drive folder to store the generated PDFs
• Optional: a Gmail account or calendar as a delivery mechanism

Prerequisites: your Google Docs template must be accessible by Make.com and you should know the data mapping for each placeholder. It helps to have a consistent naming convention for placeholders that exactly matches the data fields in your sheet.

How It Works (The Logic)

Trigger: A new row is added to Google Sheets (or an existing row is updated, depending on your needs). Make.com reads the row data, creates a new Google Docs document from your template, replaces placeholders with the row values, exports the document to PDF, saves the PDF in Drive, and emails the PDF to the recipient.

Optional enhancements include logging the generated PDF in a separate sheet for auditing and posting a notification to Slack when a PDF is created.

Step-by-Step Setup

1. Prepare your Google Docs template

• Create a template with placeholders for client data that will be replaced by Make.com.
• Examples: {{ClientName}}, {{ClientEmail}}, {{Date}}, {{Project}}, {{Amount}}.
• Keep a consistent placeholder naming strategy to avoid mapping mistakes.

2. Prepare your data source

• Create a Google Sheet with columns that match each placeholder name, or plan to map fields from another source like a CRM.
• Include a recipient email field so the PDF can be emailed automatically.

3. Create a Make.com scenario

• Start a new scenario and add a Google Sheets module set to Watch Rows or Search Rows depending on your trigger pattern.
• Connect your Google Sheets account and select the file and sheet that contains your data.

4. Add a Google Docs action to create the document from a template

• Add the module Google Docs Create Document from Template.
• Choose your template document and specify the new document name, for example Proposal - {{ClientName}} - {{Date}}.
• Map fields that will be used to replace placeholders via a subsequent step.

5. Replace template placeholders with data

• Add Google Docs Replace Text steps to map each placeholder to the corresponding sheet field.
• For example, replace {{ClientName}} with {{ClientName}} from the sheet, replace {{Date}} with the date field, and so on.
• Ensure all required placeholders are filled before proceeding.

6. Export the document to PDF

• Add a Google Drive Export File as PDF action or a similar export step.
• Use the created Google Docs file as the source and set the export to PDF, naming the PDF consistently, for example Proposal_{{ClientName}}_{{Date}}.pdf.
• Save the PDF back to Drive in your designated folder.

7. Deliver the PDF

• Add a Gmail action Send Email with the PDF attached or a shareable link.
• Populate recipient fields from the sheet data and set a clear subject like Your Proposal.
• Include a brief summary and a link to the Drive file for easy access.

8. Update your source and logs

• Optionally, update the Google Sheet with the PDF link or file ID for auditability.
• You could also write a row to a separate log sheet with the document name, recipient, and timestamp.

9. Test and deploy

• Create a test row in your sheet with sample data and run the scenario.
• Verify that the Google Docs template is filled correctly, the PDF is created, saved to Drive, and the email arrives with the attachment.

Real-World Business Scenario

A marketing agency uses this pattern to turn client data into a ready to send proposal PDF. When a new row lands in Google Sheets, Make creates a personalized PDF from a Google Docs template, exports it to Drive, and emails the deliverable to the client. The team eliminates manual drafting and reduces turnaround from hours to minutes while maintaining an auditable trail of each proposal.

If you want the exact steps tuned to your fields and template, Olmec Dynamics builds end to end Cross-Platform Automation patterns for teams that rely on document templates. Learn more about our approach Cross-Platform Automation Cross-Platform Automation.

Common Variations

• Add a Slack notification when a PDF is generated so the team knows a new deliverable is ready.
• Extend to multiple templates by routing based on a project type field.
• Store a copy of the generated PDF in a dedicated Drive folder per client.

Closing thoughts

This pattern takes you from manual PDF generation to a repeatable, auditable workflow that scales with your data. If you want this level of automation implemented for your stack, Olmec Dynamics can design and deploy it for you. See what we do at Olmec Dynamics and explore our Cross-Platform Automation approach for production-grade workflows.