PDFs from Google Docs Templates: Automating document generation with Make.com and PandaDoc

Introduction

If your team uses Google Docs to draft client proposals, invoices, or project briefs, you know the pain of copying templates, exporting PDFs, and sending them for signature manually. This intermediate Make.com and PandaDoc workflow automates the whole process: pull data from Airtable, fill a Google Docs template, export a PDF with a click, and prep a PandaDoc document for e sign. By the end you’ll know exactly how to wire up this end-to-end automation.

This pattern fits professional services, design studios, and agencies that rely on templated documents but want to avoid repetitive manual steps. It keeps your branding consistent while speeding up proposal and contract cycles.

What You'll Need

• Airtable base with a target table (for example Proposals) and fields like ClientName, ClientEmail, ProjectName, ProposalDate, Amount
• A Google Docs template prepared with placeholders such as {{ClientName}}, {{ProjectName}}, {{ProposalDate}}, {{Amount}}
• PandaDoc account and a template ready to receive data
• A Make.com (Integromat) account with connectors for Airtable, Google Docs, Google Drive, and PandaDoc
• A Google Drive setup to export PDFs from Google Docs
• Optional: a Gmail/Outlook connection for sending the final PDF or a signed document link

How It Works (The Logic)

Trigger: a new record is added in Airtable. Action: Make.com creates a new Google Docs document from your template and fills placeholders using the Airtable fields. Next, Google Drive exports the filled document to PDF. Then PandaDoc creates a document from that PDF (or uses a PandaDoc template filled with the same data). Finally, PandaDoc sends the document for signature and you optionally save the PDF link back to Airtable or share it with stakeholders.

This flow minimizes manual touch points while ensuring consistency and traceability.

Step-by-Step Setup

1. Prepare your Google Docs template with clear placeholders

• Create a Google Docs template that includes placeholders like {{ClientName}}, {{ProjectName}}, {{ProposalDate}}, {{Amount}}.
• Keep placeholders consistent to simplify mapping in Make.com.
• Save the template in Google Drive so Make.com can access it.

2. Prepare your Airtable data structure

• Create a base table named Proposals with fields matching your placeholders: ClientName, ClientEmail, ProjectName, ProposalDate, Amount, Currency, etc.
• Ensure you have read access from Make.com to this Airtable base.

3. Create a new Scenario in Make.com

• In Make.com, start a new Scenario and add Airtable as the first module.
• Choose the trigger: Watch Records (or similar) for the Proposals table and set a practical limit (e.g. 5–20) for testing.

4. Map Airtable fields to Google Docs placeholders

• Add Google Docs module: Create document from template.
• Pick the Google Docs template you prepared.
• Map placeholders to Airtable fields, for example:
  • {{ClientName}} → ClientName
  • {{ProjectName}} → ProjectName
  • {{ProposalDate}} → ProposalDate
  • {{Amount}} → Amount
• Validate that the output document name is unique per run to avoid overwriting.

5. Export the filled document as a PDF

• Add Google Drive or Google Docs export action to convert the filled document to PDF.
• Configure export to produce a PDF file and store it in a designated folder in Google Drive.

6. Create a PandaDoc document from the PDF

• Add PandaDoc module: Create Document (or Create Document from Template) using the PDF and the same data values.
• Set the recipient to ClientEmail and configure any required template data fields.

7. Send for signature

• Use PandaDoc actions to Send Document for signature or prepare a link for sharing.
• Include a friendly message and ensure the signer role matches your contract flow.

8. Log the outcome and attach the PDF link back to Airtable or share with stakeholders

• Add Google Drive or Airtable Update step to store the PDF link or a signed document status back into the Airtable record.
• This ensures your proposals have a single source of truth in Airtable for status and retrieval.

9. Test and deploy

• Run a few test records in Airtable to verify mapping, PDF export, PandaDoc creation, and signature sending.
• Check for edge cases such as missing ClientEmail or amounts with currency formatting.
• Once confident, turn on the scenario and monitor the first production runs for a week.

Real-World Business Scenario

A professional services firm uses this setup to auto-generate proposal PDFs from a single Airtable request form. The document is created in Google Docs, exported as a branded PDF, loaded into PandaDoc, and sent to the client for e sign. This reduced the proposal cycle from hours to minutes and kept branding consistent across teams. If you want to see how similar automation improves client delivery, we’ve covered patterns like ClickUp to Slack status alerts and Typeform to HubSpot lead sync. For Shopify patterns see Shopify orders to Google Sheets and Slack.

Common Variations

• PDF to email: add a Gmail or Outlook step to email the PDF as an attachment to the client and your internal team.
• Signature routing: add second signers or multiple recipients; use PandaDoc routing to manage the signing order.
• Versioning: keep a versioned file in Google Drive each time a proposal template is filled. This helps with compliance and audits.

If you want this level of automation built across Airtable, Google Docs, PandaDoc, and Make.com, Olmec Dynamics builds these end-to-end solutions for real businesses. Learn more about our work at Olmec Dynamics.

What this means for your team

This template shows how to turn templated documents into a scalable, auditable process. You get consistent PDFs, faster contract cycles, and clear ownership from data to signature. If you are ready to implement or extend this workflow for proposals, contracts, or client briefs, Olmec Dynamics can tailor it to your stack and processes.