← Back to blog

Zapier Document Generation: How to Create PDFs from Any App with Documint

José Cruz · November 13, 2026

Zapier workflow sending form data to a Documint template that produces a contract PDF

Zapier document generation is when a Zap takes data from an app you already use, such as a form, a CRM or a spreadsheet, and turns it into a PDF with Documint. A new form response or a deal stage change fills your template, and the finished document is saved or emailed without anyone copying data by hand.

This guide shows how the workflow fits together, how to set it up step by step, and three Zaps worth building first.

How does Zapier document generation work?

Every Zap has a trigger and one or more actions. For documents, the flow looks like this:

Trigger appNew form response, deal stage change, new row
ZapierPasses the data to Documint
Documint templateFills fields, rules and line items
Save or sendGoogle Drive, email or e-signature
A typical document Zap: one trigger, then Documint, then a storage or email step.

Documint's job is the middle of the flow. You design the layout once in the drag-and-drop designer and add fields where the data goes. Zapier sends the values for those fields, and Documint returns a PDF.

How do you set up Zapier document generation with Documint?

You need a Zapier account, a Documint account and a template with fields that match your data. If you want a working example first, the Zapier quickstart guide lets you clone a ready-made template, Google Form and Zap.

  1. 1

    Design your template

    In Documint, create a new template and lay out the document with rows, columns, text and images. Open Manage fields and add the fields your Zap will send, such as client_name, start_date and total. Drag each field onto the page where its value should appear. The Fields Editor guide explains the field types.

  2. 2

    Create an API key

    In Documint, go to Settings > API keys, click New API key, give it a name such as "Zapier" and copy it. Zapier uses this key to connect to your account.

  3. 3

    Set up the trigger in Zapier

    Create a Zap and pick the app where your data starts, such as Google Forms, Typeform, HubSpot or Airtable. Choose the trigger event, for example New Form Response, connect your account and test it to pull in sample data.

  4. 4

    Add the Documint action

    Add an action step, search for Documint and choose Generate Document. When Zapier asks for an account, paste your API key.

  5. 5

    Select the template and map the fields

    Choose your template. Zapier shows its fields, and you match each one to a value from the trigger step, such as the form answer for the client's name. Test the step to create a sample document.

  6. 6

    Save or send the PDF

    Add one more action that uses the PDF URL from the Documint step. Upload it to Google Drive or Dropbox, attach it to an email, or save it back to the original record.

How do you map Zapier data to template fields?

Field mapping is where most Zaps succeed or fail. Name your template fields after the data they hold, and the mapping screen becomes easy to read. Here is an example for a service contract built from a Google Form:

Google Forms · Service request

Service contract

1Client name
2Client email
3Service start date
4Services table
5Total
6Company logo
Hover or tap a field to see where it lands in the service contract.

Clean the data before it reaches Documint. Documint prints exactly what it receives. Use Zapier's Formatter step to fix capitalization, number formats or dates first. You can also format dates and numbers inside the template with token formatting.

How do you handle different versions of the same document?

You don't need a separate template for every variation. Two features in the template designer cover most cases:

  • Display rules show or hide an element based on the data. Select the element, click Edit Logic and add a rule, for example "show this clause if plan equals Enterprise". See Display Rule.
  • Repeat/Loop repeats a row once for each item in a list, such as line items or services. See Repeat/Loop.

One template with rules is easier to maintain than ten near-identical copies.

Which Zaps should you build first?

Start with a document you make often, from data that already lives in one app.

Trigger: a deal in HubSpot or Salesforce moves to "Contract requested".

Documint: fills the client name, terms and price table. A display rule adds the right clauses for the plan.

Then: email the contract to the client, or send it for signature with Documint Sign (Silver plan and up).

Should you use Zapier, or connect directly?

Zapier is the right choice when your data lives in an app Documint doesn't connect to directly. If your data is in Airtable or HubSpot, a direct integration needs fewer steps. See all the ways to connect on the Zapier integration page.

Recommended

Zapier

Best for apps without a direct integration

  • Connects forms, CRMs and thousands of other apps
  • No code, set up in the Zapier editor
  • Easy to add storage, email or signature steps
  • Each run uses Zapier tasks as well as Documint merges

Direct integration

Best for Airtable and HubSpot

  • Generate from a button or automation in Airtable
  • Generate from a record in HubSpot
  • Saves the PDF back to the record
  • Only for the apps Documint connects to directly

Prefer Make? The same flow works there too. See our Make document generation guide.

Frequently asked questions

Do I need to know how to code to use Zapier with Documint?

No. You design the template in a drag-and-drop editor and map fields in Zapier's interface. The only thing you copy is an API key from Documint's settings.

The PDF URL from the Documint step is temporary. Add a step after it that uploads the file to storage, like Google Drive, or attaches it to an email.

Can I test my Zap without using my document quota?

Yes. Generating from an inactive template creates test documents with Documint branding at the bottom. These don't count toward your usage. Activate the template when you're ready to go live.

Can Zapier send line items to Documint?

Yes, as long as your template has a list field and a Repeat/Loop row. Each item in the list becomes a row in the document. How you build the list depends on the trigger app.

Turn your next Zap into a document

Design a template once, connect it to Zapier, and let every trigger create the PDF for you.

How Document Generation Works: A Non-Technical Guide

Next Blog →

Order data feeding a Documint template that produces a quote PDF