How to Generate PDFs from Google Docs Templates Using Make.com and PandaDoc

Introduction

If you still assemble client documents by copy pasting data between Google Docs, local templates, and email, you know the drag. Every update to a proposal or contract forces someone to reformat, recheck fields, and re-send. A multi-tool document generation flow can reclaim hours and reduce errors. In this post you’ll learn how to generate PDFs from Google Docs templates using Make.com and PandaDoc. You will merge data, export a clean PDF, and optionally hand the document to PandaDoc for signing.

By the end, you will know how to wire up Google Docs, Make.com, and PandaDoc to produce consistent PDFs at scale without manual rework.

What You'll Need

• A Google Docs template with placeholders like {{client_name}}, {{project}}, {{due_date}}, {{amount}}
• A Google Sheet or a data source with columns for client_name, project, due_date, amount, recipient_email, sign_required
• A PandaDoc account with templates ready for use and API access if you plan to send for signing
• A Make.com account with connections to Google Docs, Google Drive, Google Sheets, and PandaDoc
• Optional: an email app (Gmail/Outlook) for sending the final PDF when you do not use PandaDoc for signing

Note that you may want a paid plan on Make.com if you need higher run volumes or retries. PandaDoc usage may require a paid tier depending on your signing and template needs.

How It Works (The Logic)

Trigger: a new row is added to Google Sheets (or a record updated in your data source). Make.com reads the fields and maps them to placeholders in a Google Docs template. It creates a new Google Docs document from the template, then exports the document as a PDF. If you want an e-signature flow, PandaDoc creates a document from a PandaDoc template using the same data and sends it to the recipient for signing. If you don’t need signing, you can finish with the PDF attachment sent via email or stored in Drive.

The two paths are complementary: Google Docs handles the formatting and merging, while PandaDoc handles signing and delivery when required.

Step-by-Step Setup

1. Prepare your Google Docs template

• Create a doc with placeholders such as {{client_name}}, {{project}}, {{due_date}}, {{amount}}.
• Save the doc as a template or locate the final editable template in Google Docs.

2. Prepare your data source

• Create a Google Sheet with columns: client_name, project, due_date, amount, recipient_email, sign_required (true/false).
• Keep data clean and consistently formatted to avoid mapping errors.

3. Create a Make.com scenario

• Start with a Google Sheets module set to watch for new rows or updates in the chosen sheet.
• Ensure you have a Make.com connection to Google Docs, Google Drive, and PandaDoc.

4. Merge data into Google Docs

• Add a Google Docs module and select Create Document from Template.
• Choose the template you prepared and map each placeholder to the corresponding sheet field:
  • {{client_name}} ← client_name
  • {{project}} ← project
  • {{due_date}} ← due_date
  • {{amount}} ← amount
• The module returns a new document_id for the created file.

5. Export the document as a PDF

• Add a Google Drive or Google Docs export step.
• Use Export File or Publish to PDF action to convert the new document into a PDF file.
• Capture the PDF link or file_id for the next steps.

6. Optional PandaDoc path for signing

• If sign_required is true, add a PandaDoc module.
• Use Create Document from Template and map data fields to PandaDoc fields, then set recipient_email and signers.
• Add a step to Send for Signing or Schedule Signing, depending on your process.
• Capture the PandaDoc document_id and the signing status.

7. Deliver the final PDF

• If you used PandaDoc, you can attach or link the PandaDoc signing link to your email
• If you did not use PandaDoc, add an Email module (Gmail/Outlook) to send the PDF to recipient_email with a clear subject and a brief message
• Alternatively store the PDF in Google Drive with a descriptive filename like Client_Project_YYYYMMDD.pdf and notify the recipient with the link

8. Test thoroughly

• Create a test row with sign_required as true and verify the PandaDoc flow requests a signature.
• Create another test row with sign_required as false and verify the PDF creation and delivery path works.
• Check field mappings if you see misaligned data in the final document.

9. Go live and monitor

• Activate the scenario and monitor a few production runs.
• Look for mismatched placeholders, missing recipient emails, or signing errors.

Real-World Business Scenario

A design agency uses this pattern to generate client proposals. They fill a Google Sheet with client data, Make.com creates a clean PDF from a Google Docs template, and PandaDoc signs off on the proposal before sending it to the client. The end-to-end process reduces proposal creation time from hours to minutes and improves accuracy across boilerplate sections.

Common Variations

• Replace the Google Docs path with a PandaDoc-only path from the start: populate PandaDoc fields directly and sign without generating a Google Docs PDF at all.
• Add versioning to templates: store a version number in a template_id column and swap templates without changing your mapping logic.
• Add validation: if critical fields are missing (email, client name), route to a human review queue in Slack or email instead of sending a document.

What this means for your document workflows

This pattern gives you a repeatable, auditable path from data to document to signature. It reduces manual steps, improves consistency, and scales with your client volume. If you want this level of automation built for your business, Olmec Dynamics builds these production document workflows for real organizations. Learn more at Olmec Dynamics.