← Back to blog

Make Document Generation: How to Create PDFs in Make.com with Documint

Josh Mamroud · September 22, 2026

Make scenario creating an invoice PDF with a Documint template

Make document generation is when a Make scenario takes data from an app, such as a form, a CRM or a spreadsheet, and turns it into a PDF using a Documint template. When a new form response or record arrives, the scenario fills your template and saves the document, with nobody copying data by hand.

This guide walks through the modules you need, the setup step by step, and how to handle line items and different document versions.

How does a Make document scenario work?

Trigger modulee.g. Google Forms: Watch Responses
DocumintCreate a Document from your template
HTTPGet a file from the PDF URL
Storage or emaile.g. Google Drive: Upload a File
A four-module scenario: watch for data, create the document, fetch it, store it.

Make handles the connections and the timing. Documint handles the document: the layout, the fields, the rules and the PDF. The Make integration page has an overview.

How do you set up Make document generation with Documint?

Want to see it working first? The Make quickstart guide lets you clone a sample template, Google Form and scenario in a few clicks. To build your own:

  1. 1

    Design your template

    In Documint, create a template and lay out the document with rows, columns, text and images. Open Manage fields and add the fields your scenario will send, such as customer_name, service and request_date. Drag them onto the page. See the Fields Editor guide for field types, including collections for line items.

  2. 2

    Create an API key

    In Documint, go to Settings > API keys, click New API key and copy it.

  3. 3

    Add your trigger module

    In Make, create a new scenario. Add the module where your data starts, for example Google Forms > Watch Responses, and connect your account.

  4. 4

    Add the Documint module

    Add the Documint module and choose Create a Document. Create a connection and paste your API key.

  5. 5

    Map the template fields

    Select your template. Its fields appear in the module, and you map each one to a value from the trigger, such as the form's name answer.

  6. 6

    Fetch and store the PDF

    Add an HTTP > Get a file module using the URL from the Documint module. Then add Google Drive > Upload a File, or an email module, to store or send the PDF.

  7. 7

    Run once and check the output

    Click Run once to test with a real record. Check the PDF, then schedule the scenario.

How do you map form or CRM data to template fields?

Keep field names close to your source data and the mapping is easy to check. Here is an example for a service request confirmation:

Google Forms · Service request

Service request confirmation

1Customer name
2Contact email
3Requested service
4Preferred date
5Notes
Hover or tap a field to see where it lands in the service request confirmation.

Format in Make or in the template. You can tidy values with Make's built-in functions before the Documint module. Or format dates and numbers inside the template with token formatting.

How do you add line items and conditional sections?

Two features in the template designer turn one template into many documents. Select an element and click Edit Logic to use either one.

Add a collection field, such as items, with properties like description, quantity and price. Select the table row and set it to repeat on items with Repeat/Loop. In Make, build the list and pass it to that field. This video on line items with Make shows the setup.

Which scenarios should you build first?

Scenario

Trigger

Document

Then

Service confirmations

New form response

Confirmation PDF

Email to the customer

Contracts

CRM deal reaches "Won"

Contract with plan-specific clauses

Send for signature

Invoices

New paid order

Invoice with line items

Upload to Google Drive

Offer letters

Candidate marked "Hired"

Offer letter

Email to the hiring manager

Start with the one your team makes most often from data in a single app.

Make or Zapier: which should you use?

Both connect Documint to thousands of apps without code. The right one is usually the tool your team already uses.

Recommended

Make

Best for multi-step, visual scenarios

  • Visual canvas for branching and data handling
  • Built-in functions to reshape data and lists
  • Explicit HTTP step to download the file
  • Takes a little longer to learn

Zapier

Best for quick, linear Zaps

  • Simple trigger-then-action setup
  • Large library of app connections
  • Formatter step for cleaning data
  • Complex branching is less visual

Using Zapier? Follow our Zapier document generation guide. If your data is in Airtable, you may not need either: see the Airtable integration.

Frequently asked questions

Do I need to code to generate documents with Make?

No. You design the template in Documint's drag-and-drop editor and map fields in Make's interface. The only technical step is pasting an API key.

The URL from the Documint module expires after a few hours. Add an HTTP Get a file module and a storage or email module after it, so the file is saved during the run.

Can I test without using my document quota?

Yes. Documents generated from an inactive template include Documint branding and don't count toward your usage. Activate the template when you're ready.

Which apps can I use as a trigger?

Any app Make connects to, such as Google Forms, Google Sheets, HubSpot, Airtable or your CRM. Documint only needs the field values the template expects.

Add documents to your Make scenarios

Design a template once, add the Documint module, and let every run produce the PDF for you.

How to Automate Document Creation in Coda (Step-by-Step)

Next Blog →

Coda projects table feeding a Documint template that produces a report PDF