Automating Proposals: Google Docs Templates to PDF with Make.com

Introduction

If you still generate client proposals by hand or with inconsistent export steps, you know how slow and error prone it feels. You pull data from your CRM, copy it into a template, manually export to PDF, and email it to the client. Any slip hurts your close rate. This guide shows how to automate proposal generation using Google Docs templates, Make.com, and a few connected services so the right data lands in the right place every time. The promise: faster proposals, fewer mistakes, and a clean audit trail.

By the end you will have a repeatable pattern: HubSpot triggers a Make.com scenario, data maps into a Google Docs proposal template, the document is exported as a PDF, saved to Google Drive, and emailed to the client with the correct recipient and attachment. If you want more context on routing and templating patterns, check out our related posts on CRM to automation workflows and document generation patterns Typeform to HubSpot lead routing and Shopify order alert patterns.

What You'll Need

• A HubSpot account with a deal you want to generate a proposal for, plus access to relevant fields (client name, company, email, deal value, close date, etc.)
• A Google Docs proposal template with placeholders like {{client_name}}, {{company}}, {{deal_value}}, {{close_date}}, {{project_scope}}, and {{proposal_link}}
• A Google Drive folder to store generated PDFs
• A Make.com account with connections to HubSpot, Google Docs, Google Drive, and Gmail
• A Gmail account to send the final PDF to the client (or use another email action if you prefer)
• A basic testing plan to verify mappings, output formats, and email delivery

Note: For production volumes you may want a paid Make.com plan and API access in HubSpot to ensure reliability and rate limits are covered.

How It Works (The Logic)

Trigger: A new deal is created in HubSpot (or a deal stage reaches a milestone suitable for a proposal).

• Make.com reads the deal data from HubSpot and fills a Google Docs template with key fields.
• The filled document is exported as a PDF.
• The PDF is saved to Google Drive with a predictable filename (e.g., ClientName_Proposal_Date.pdf).
• An email is sent via Gmail to the client with the PDF attached and a short summary in the body. Optional Slack or Teams notifications can alert your team of the completed proposal.

This pattern turns a manual quoting process into a single, auditable flow that scales with your team. If you want to see a similar document generation pattern in action, explore our doc generation posts that link to practical templates and outcomes.

Step-by-Step Setup

1. Prepare your Google Docs template

• In Google Docs, create a clean proposal template with placeholders. Use clearly named placeholders such as {{client_name}}, {{company}}, {{deal_value}}, {{close_date}}, {{project_scope}}, and {{proposal_link}}.
• Save the template in a central folder so Make.com can access it reliably.

2. Create the Make.com scenario

• In Make.com, create a new Scenario and add HubSpot as the first module. Choose the trigger that fires when a deal is created or a stage changes to the proposal-ready state.
• Connect your HubSpot account and configure the trigger to pull fields you plan to map into the proposal.

3. Map HubSpot fields into Google Docs

• Add Google Docs as the second module and choose the action to create a document from template.
• Select your prepared Google Docs template and map fields like:
  • client_name ← deal.owner or contact name from HubSpot
  • company ← company name from HubSpot
  • deal_value ← deal amount
  • close_date ← deal close date
  • project_scope ← a HubSpot property or a rich text note from the deal
  • proposal_link ← a link to the HubSpot deal or an internal approval page
• Ensure field names align exactly with your placeholders in the template.

4. Export the document to PDF

• Add a Google Docs module to export the generated document as a PDF. Confirm the output is a single, clean PDF ready for sending.

5. Save to Google Drive

• Add a Google Drive module to upload the PDF. Use a consistent filename pattern like ClientName_Proposal_Date.pdf to keep your drive organized.

6. Email the client with Gmail

• Add Gmail module "Send an email". Set the recipient to the client email from HubSpot.
• In the body, include a short executive summary and a link back to the HubSpot deal if needed. Attach the generated PDF.
• If you have multiple proposals, you can add a summary section with bullet points for the review team.

7. Optional: notify the team

• Add a Slack or Microsoft Teams module to post a concise notification that a new proposal was generated and emailed.
• Keep the message focused, for example: New proposal generated for {{client_name}} at {{company}}. PDF attached. Link to deal: {{hubspot_deal_link}}.

8. Add a de-duplication or idempotency check

• If your HubSpot trigger can re-run, add a filter or a small lookup step to ensure you do not duplicate proposals for the same deal.
• You can base this on the HubSpot deal ID or a dedicated field in Google Drive.

9. Test end-to-end

• Create a test deal in HubSpot and verify: the Google Doc is created with correct mappings, the PDF is produced, the file lands in Drive, and the email arrives with the attachment.
• Check placeholders render correctly for different clients and currencies.

10. Turn on and monitor

• Activate the scenario and watch the first production runs. Check for mapping mismatches, PDF formatting issues, or email deliverability problems.
• If you run into Gmail quota limits, consider staggering emails or using a transactional email service as an alternative.

Real-World Business Scenario

A professional services firm uses this exact flow to generate client proposals in minutes after a deal is created in HubSpot. The team no longer copies client details into a Word document, and the PDF is ready for sending within the same hour. This pattern reduces proposal turnaround from days to hours, improving win rates and customer experience.

If you want to see these patterns extended to other docs like contracts or NDAs, we have additional templates and workflows you can adapt.

Common Variations

• Add an e-signature step: integrate DocuSign or PandaDoc to route the PDF for signature after delivery.
• Multi-language templates: create separate Google Docs templates for different languages and switch templates based on client location in HubSpot.
• Staged approvals: route the proposal to a manager for quick approval within Make.com before sending to the client.

If you want this level of workflow built across HubSpot, Google Docs, Make.com, Gmail, and Google Drive for your team, Olmec Dynamics builds these automations for real businesses. Learn more about our work at Olmec Dynamics.

Closing thoughts

Automating document generation with Google Docs templates and Make.com gives you a scalable, auditable way to generate professional proposals. The pattern is repeatable, testable, and adaptable to many doc types beyond proposals. If you need help turning these patterns into production-grade automations, Olmec Dynamics can build them for you.

To explore more about our practical automation work, visit Olmec Dynamics here.