Olmec Dynamics
A
·6 min read

Automating PDF generation from Google Docs templates with PandaDoc using Make

Learn how to generate PDFs from Google Docs templates using Make.com and PandaDoc. Step by step setup, template mapping and reliable error handling for docs.

Introduction

If you still generate client documents by manually duplicating Google Docs templates, filling in fields, exporting as PDF, and then sending to PandaDoc for signing, you know how slow and error prone that process is. This guide shows a practical pattern to automate the whole thing using Google Docs as the templating engine, PandaDoc for final PDF handling, and Make.com to glue it together. By the end you’ll have a reliable flow that turns data in Google Sheets into polished PDFs without touching a keyboard.

This pattern is ideal for proposals, statements of work, or client briefs where you want consistent branding and an auditable trail. Real teams use this to free up time for high value work while keeping documents on brand and legally compliant. For context on similar Make.com driven document patterns, see our Shopify to Google Sheets guides Shopify to Google Sheets and Slack: A Simple Make.com Automation Guide and Shopify to Google Sheets: Automate Orders with Make.

What You’ll Need

  • A Google Docs template with clearly named placeholders (for example {{client_name}}, {{project_title}}, {{due_date}}, {{amount}})
  • A PandaDoc account with a prepared template that matches your intended PDF output
  • A Make.com account with Google Docs, Google Sheets, PandaDoc, and optional Slack connectors
  • A Google Sheet that captures the data you want merged into the document (new row triggers the flow)
  • Access to the Google Drive folder where generated PDFs will live (optional)

Note: A Make.com paid plan is recommended if you expect production scale or need reliability features like error handling and higher run limits.

As a reminder, this post references patterns we’ve implemented for other automation problems, including Shopify to Google Sheets workflows. See our related guides for broader patterns.

How It Works (The Logic)

Trigger: A new row is added to Google Sheets (your data source). Action 1: Make creates a Google Docs document from a template, filling in placeholders with values from the sheet. Action 2: Make calls PandaDoc to generate a PDF from the newly created Google Docs content or to create a PandaDoc document using the data and a template. Action 3: Optional: Save the resulting PDF to Google Drive or attach it to the PandaDoc workflow for signing. Action 4: Notify a channel or send an email with the PDF link for quick distribution.

This keeps your document creation auditable, repeatable and branding-consistent with minimal manual work.

Step-by-Step Setup

  1. Create the Make.com Scenario
  • In Make.com, create a new scenario and give it a clear name like “Docs to PandaDoc PDF automation.”
  • Connect your Google Sheets, Google Docs, PandaDoc accounts and test connections.
  1. Add Google Sheets trigger
  • Module: Google Sheets > Watch Rows (or Get Rows depending on your data source)
  • Configure: select the spreadsheet and the sheet containing your form or data source. Add a simple trigger to only process new rows (avoid reprocessing the same data).
  1. Create the Google Docs document from template
  • Module: Google Docs > Create a Document from Template
  • Template: select your Google Docs template that contains placeholders like {{client_name}}, {{project_title}}, {{due_date}}, {{amount}}
  • Map fields from the Google Sheets row to the placeholders. Example mappings:
    • client_name → {{client_name}}
    • project_title → {{project_title}}
    • due_date → {{due_date}}
    • amount → {{amount}}

Tip: Use a consistent placeholder naming convention to avoid mapping mistakes. If your data requires date formatting, add a date formatter step to convert to your desired format before mapping.

  1. Generate PDF in PandaDoc
  • Module: PandaDoc > Create Document (or Create Document from Template, depending on your PandaDoc configuration)
  • Choose a PandaDoc template and map fields from the Google Docs output or the original sheet data to PandaDoc fields. For instance:
    • Client Name = {{client_name}}
    • Project Title = {{project_title}}
    • PDF Content = content from the Google Docs output (or mapped text blocks)

Note: If PandaDoc requires separate fields or a specific template, you may need to perform an intermediary transformation to align field IDs.

  1. Retrieve PDF URL or status
  • Module: PandaDoc > Get Document or Download PDF
  • Capture the PDF URL or the final document status to pass to downstream steps.
  1. Optional: Save PDF to Google Drive
  • Module: Google Drive > Upload a File
  • Source: the PDF binary or URL from PandaDoc
  • Destination: a designated folder for generated documents
  1. Notify the team
  • Module: Slack > Post a Message (or Gmail/Outlook for email delivery)
  • Craft a concise message with a link to the PDF and a brief summary of client and project details.
  1. Test end-to-end
  • Add a test row to Google Sheets and verify that:
    • A Google Doc is created from your template with correct data
    • PandaDoc generates a PDF from the document
    • The PDF is saved to Drive (if enabled) and the notification is received
  1. Activate and monitor
  • Turn on the scenario and watch the first few runs. Check for field mapping mismatches, authentication issues, or PDF generation failures. Tweak timeouts and retries as needed.

Real-World Business Scenario

A marketing agency uses this pattern to auto generate client proposals. When a new client submission lands in Google Sheets, a branded PDF proposal is created from a Google Docs template, a PandaDoc document is generated for e-signature, and the final PDF is saved to Drive and shared with the client via email. The team reports faster proposal turnaround and fewer copy-paste errors, with a clean audit trail from submission to signature. For broader pattern context, see our Shopify to Google Sheets guides and other Make.com workflows we’ve built for Ops teams.

If you want a tailored implementation for your stack, Olmec Dynamics builds these document generation automations end to end. Learn more about our approach at Olmec Dynamics.

Common Variations

  • Add an approval step in PandaDoc before sending for signature, and route approvals by client type or deal size.
  • Extend to generate multiple documents per row, such as a proposal plus a contract, both PDF’d and stored in Drive.
  • Trigger delivery by email only after PandaDoc shows a signed status, ensuring you share only finalized documents.

What This Enables

This workflow eliminates manual document creation, ensures consistent branding, and delivers reliable PDFs to clients faster. If you need a production-grade setup with field-level validation, scalable retries, and enterprise-grade sign-off, Olmec Dynamics can tailor this exact pattern for you. Learn more about our approach at Olmec Dynamics.

For more practical patterns built with Make.com and Google Docs, you can explore related guides including Shopify to Google Sheets workflows and other data pipelines we’ve documented in our blog.