H
·6 min read

How to Generate a PDF from a Google Docs Template Using Make.com and Gmail

Generate a PDF from a Google Docs template, save it to Drive, and email it automatically using Make.com, Google Docs and Gmail. With filename rules.

Introduction

You probably still create proposals or simple client PDFs by duplicating a Google Docs template, replacing a few fields, downloading as PDF, and attaching it to an email. That manual loop costs minutes every time and invites formatting mistakes, wrong filenames, and missed sends.

This guide shows a simple Make.com scenario that automates that exact task: pull data, populate a Google Docs template, export a PDF, save the file to Google Drive, and email it via Gmail. By the end you will have a repeatable flow that removes the copy/paste steps and enforces consistent filenames.

What you will know by the end: the modules to use in Make.com, how to map template fields, how to create deterministic filenames, and how to test the end-to-end flow.

What You'll Need

  • A Make.com account with access to Google integrations (free plans can work for low volume, but a paid plan simplifies larger runs)
  • A Google Workspace account with permission to edit the template and write to the target Drive folder
  • A Google Docs template with clear placeholder tokens (see below)
  • A Gmail account authorised in Make.com for sending the emails
  • Basic familiarity with Make.com scenarios and modules

Note: If you need advanced templating (conditional sections, complex tables) consider using a templating tool such as Document Studio or a dedicated document generator. This guide uses basic token replacement inside Google Docs which is reliable for proposals, contracts, and one-page summaries.

How It Works (The Logic)

When you trigger the scenario (manual run, form submission, or webhook), Make.com pulls the data, creates a copy of your Google Docs template, replaces placeholder tokens with the values, exports that copy as a PDF, saves the PDF into a defined Google Drive folder with a predictable filename, then sends the PDF as an attachment via Gmail to the recipient.

Trigger → Create Docs copy → Replace tokens → Export PDF → Save to Drive → Send email

Step-by-Step Setup

  1. Prepare your Google Docs template
  • Use obvious placeholders like {{client_name}}, {{project_name}}, {{amount}}.
  • Keep placeholders unique and use only letters, numbers, and underscores inside the braces.
  • Remove any headers/footers you do not want in the final PDF or ensure they reference stable fields.

Common gotcha: don’t use placeholders that repeat in different contexts unless they must be identical. If you need similar tokens, name them distinctly like {{client_first}} and {{client_last}}.

  1. Create a target Drive folder and note its ID
  • Create the Drive folder where PDFs will be stored.
  • Copy the folder ID from the Drive URL, you will use it in Make.com to save the file.
  1. Start a new Scenario in Make.com
  • Create a new Scenario and add the trigger you want. For a simple demo, use the Make.com “Manual trigger” so you can test with sample data. In production, you can use a webhook, Google Forms, or a CRM trigger.
  1. Add Google Docs: Copy a Document
  • Add the Google Docs module named "Copy a Document" (or "Make a copy" depending on connector version).
  • Point it at your template document ID and give the copy a temporary name like "Draft - {{client_name}} - {{project_name}}".

Gotcha: Make sure the Make.com service account has edit permission on the template. If copy fails, check sharing settings.

  1. Add Google Docs: Update Document Content (Replace tokens)
  • Add the Google Docs module to perform a text replacement on the copied document. If the connector offers a replace-text action, use it. If not, use the Google Drive + Docs combination: download the copy as plain text, replace tokens, then re-upload. The preferred path is the Docs replace action if available.
  • Map your source fields to the placeholders. Example: map {{client_name}} to the data source field containing the client name.

Common gotcha: Preserve line breaks and formatting. If you inject long text blocks, check the document formatting in tests.

  1. Add Google Docs: Export the document as PDF
  • Use the Google Docs or Google Drive module to export/download the updated copy as PDF. The module will return a binary file object you can use in following steps.
  1. Add Google Drive: Upload the PDF
  • Add the Google Drive "Upload a file" module.
  • Use the PDF binary from the previous step as the file content.
  • Construct a deterministic filename, for example: "Proposal_{{client_name}}{{project_name}}{{YYYYMMDD}}.pdf".

Filename tip: Replace spaces in mapped fields or normalise characters so filenames remain OS-safe. Use Make.com functions to format dates and remove unwanted characters.

  1. Add Gmail: Send Email with Attachment
  • Add the Gmail "Send an email" module.
  • To: map the recipient email from your trigger data.
  • Subject: "Proposal for {{client_name}} — {{project_name}}"
  • Body: short message with a link to the Drive file if you want recipients to open in browser as well.
  • Attachments: select the PDF binary or attach via file ID if Gmail module supports Drive attachments.

Gotcha: If you attach via Drive link, ensure link permissions are set so the recipient can view. For simple operations attach the binary to avoid Drive permission complexity.

  1. Clean up the temporary Google Docs copy (optional)
  • Add a Google Drive action to either move the copied doc to an archive folder or delete it. This keeps your Drive tidy.
  1. Test the full scenario
  • Run the manual trigger with sample data. Verify the PDF content, filename, Drive location, and that the email arrives with the correct attachment.
  • Check mobile and desktop email clients to ensure the PDF renders correctly.

Real-World Business Scenario

A small consultancy generates short scope-of-work proposals for new leads. Before this automation they duplicated templates, manually edited values, then emailed PDFs. After automating with this exact flow, each proposal is created in seconds, saved in a central Drive folder with consistent names, and delivered instantly to prospects. This removed repeated filename mistakes and saved 10 to 20 minutes per proposal.

If you capture lead details with an external form before generating documents, integrate the trigger with that form system. See our guide on connecting Typeform to HubSpot for a pattern you can adapt to use Typeform responses as the trigger for document generation: How to Connect Typeform to HubSpot and Auto-Create New Leads Using Make.com.

Common Variations

  • Trigger from Google Forms or Typeform: replace the manual trigger with a form submission webhook so each lead gets an automated proposal.
  • Add approval step: insert a Slack or Gmail approval request before exporting the PDF, so a manager reviews the draft first.
  • Use CRM data: source merge fields from HubSpot or Pipedrive so proposals are generated from contact records automatically.

Your next steps

You now have a compact Make.com scenario that takes a Google Docs template, merges data, exports a PDF, saves it to Drive, and emails it via Gmail. This reduces manual steps and enforces consistent filenames and storage.

If you want this built and extended across Google Workspace, forms, or your CRM, Olmec Dynamics builds these automations for businesses. Learn more about what we do at https://olmecdynamics.com.