Auto-Generate PDFs in Make

Why Auto-Generate PDFs in Make?

Invoices, contracts, shipping labels, certificates, quote sheets — any document that follows a repeatable layout but pulls in different data each time is a candidate for automated PDF generation. Doing this by hand in Google Docs or Word, then exporting and emailing, is the kind of task that eats an hour a day in a growing operations team. Make (formerly Integromat) can watch for a trigger — a new row in Airtable, a completed Stripe payment, a form submission — and spit out a filled, branded PDF without anyone touching a template.

The Two Practical Approaches

There isn’t one “PDF module” in Make that does everything. In practice, teams land on one of two approaches depending on how much design control they need.

1. Google Docs / Slides template + Make’s native modules

Build your document as a Google Doc or Slides deck with placeholder tags like {{customer_name}} and {{invoice_total}}. Make’s Google Docs module has a “Create a Document from Template” action that replaces those tags with data from the trigger step, then a second action exports it as PDF. This is the fastest route to set up — usually under 30 minutes — and it’s free beyond your existing Google Workspace and Make plan.

2. Dedicated PDF-generation service (PDFMonkey, Docupilot, PDF4me)

For documents that need pixel-precise layout, dynamic tables (line items on an invoice, for example), or conditional sections, a template built in a purpose-made tool like PDFMonkey or Docupilot gives you HTML/CSS-level control. Make connects to these via their native modules or a generic HTTP/Webhooks module, sending JSON data and receiving back a PDF URL. This costs a small monthly fee on top of Make (PDFMonkey’s free tier covers light use; paid plans start around $20-30/month) but scales far better once you need repeating line items or multi-page documents.

Step-by-Step: Google Docs Route

1. Build the template. In Google Docs, write your document exactly as it should look, and insert double-curly placeholders anywhere data should be swapped in, e.g. {{client_name}}, {{project_scope}}, {{amount_due}}.
2. Set your trigger. Common triggers: a new Airtable record (new client onboarded), a new Google Sheets row (order placed), or a Typeform submission (quote requested).
3. Add the “Create a Document from Template” module. Map each placeholder to the corresponding field from your trigger data.
4. Add “Export a Document” (Google Docs module) set to PDF format, pointing at the document just created.
5. Deliver it. Attach the resulting PDF to a Gmail/Outlook “Send an Email” module, or upload it to Google Drive / Dropbox and share a link.
6. Clean up. Add a final module to delete or archive the intermediate Google Doc so your Drive doesn’t fill up with one-off files — you only need the PDF.

Handling Repeating Data (Line Items, Tables)

The Google Docs template method struggles with variable-length tables — an invoice with 3 line items versus one with 12. Google Docs’ template tags don’t natively loop over an array. Two workarounds are common: pre-format a fixed number of blank rows and leave unused ones empty (fine for low-volume, imperfect for polish), or switch to a tool built for it. PDFMonkey and Docupilot both support Handlebars-style loops ({{#each line_items}}) directly in the template editor, so a Make module sending an array of 2 items or 20 renders correctly either way. If your PDFs regularly have variable-length tables, this alone is worth the switch.

Common Pitfalls

• Rate limits on Google Docs API. If you’re generating dozens of PDFs in a burst (e.g., bulk-invoicing at month end), Google’s API can throttle you. Add a small delay (Make’s “Sleep” module, 1-2 seconds) between iterations in a loop, or batch overnight.
• Leftover Google Docs cluttering Drive. Always add the delete/archive step — skipping it is the single most common complaint in Make community threads about this exact workflow.
• Placeholder text getting cut off or reformatted. Google Docs templating occasionally drops bold/italic formatting that was inside a placeholder run. Keep formatting applied to the surrounding text, not the placeholder tag itself.
• Special characters breaking JSON. If data flows in from a webhook or form, sanitize quotes and ampersands before they hit the PDF module — an unescaped & in a client name has broken more than one automation silently.

FAQ

Can Make generate a PDF without Google Docs at all?
Yes — using the generic HTTP module to call a service like PDFMonkey, Docupilot, or even a self-hosted tool like Gotenberg (which converts HTML/CSS you build directly in Make via a Text Aggregator) removes the Google Docs dependency entirely.

Is there a native “PDF” app in Make?
Not a standalone universal one. Make treats PDF generation as an export step of another app (Google Docs, Google Slides) or a request to a third-party PDF API. Search the Make app directory for “PDF” and you’ll find several third-party integrations (PDFMonkey, PDF.co, PDF4me) built specifically for this.

How many PDFs can I generate on Make’s free plan?
Make’s free tier gives 1,000 operations/month. A single PDF generation typically uses 2-4 operations (trigger, create doc, export, cleanup), so roughly 250-500 PDFs/month before you need a paid Make plan — separate from whatever the PDF service itself charges.

Verdict

For a handful of simple, fixed-layout documents (certificates, single-item receipts, basic contracts), the Google Docs template route in Make is genuinely the fastest way to get automated PDFs running today, and it costs nothing extra. The moment your documents need repeating tables, conditional sections, or brand-perfect design, move the templating layer to PDFMonkey or Docupilot and keep Make as the orchestration glue — that combination is what most production no-code stacks settle on.