Resources · Make integration

DocuGenerate Make integrationAutomate DocuGenerate with Make.

What if every contract, quote or certificate filled itself in? The DocuGenerate Make integration gives you 4 modules: 2 triggers and 2 actions. This guide is for anyone who builds documents from templates, and it walks you from the connection to a first working scenario.

Try the DocuGenerate integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DocuGenerate Make integration do for you?

The DocuGenerate Make integration links your DocuGenerate account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Data from your other apps fills your DocuGenerate templates, and new documents or templates can start the next step on their own.

Paperwork that writes itself. A sales rep closes a deal in the CRM, or a client submits a form. Generate a Document takes that data and pours it into your template. Pair it with a form tool such as the one described in the 123FormBuilder Make integration and each submission becomes a finished document.

Every new file reaches the right people. Watch New Document notices each document generated from a template, so a following module can email it, store it or log it in a spreadsheet. Nobody has to download and forward it by hand.

A heads-up when the template library grows. Watch New Template picks up each template someone creates, which lets you post a message to the team channel or keep an inventory list current.

Both triggers are scheduled: Make checks DocuGenerate on the scenario's schedule, not the second something happens. For anything the listed modules skip, Make an API Call reaches the rest of the DocuGenerate API with the same connection. Weighing another tool? The n8n vs Make comparison lays out both, and the Make training covers the editor from scratch.

Connect

How do you connect DocuGenerate to Make?

  1. 01

    Generate your API key

    In DocuGenerate, open the Settings page, go to the Developers tab and click Generate API Key. Confirm in the dialog box, then copy the key shown in the window. You need an active DocuGenerate account for this.

  2. 02

    Add a DocuGenerate module

    In your Make scenario, add any DocuGenerate module and click Create a connection. A connection is your DocuGenerate account linked to Make once, then reused by every DocuGenerate module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like, it helps when several accounts coexist. Paste the API key you copied, then save. Make can now read your templates and documents.

First scenario

Your first scenario with DocuGenerate

GoalWhen a form or another app sends new data, Make turns it into a DocuGenerate document.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that holds your data first, for example your form tool, and choose its trigger.

  2. 02

    Add Generate a Document

    Click the + on the right of that first module, search for DocuGenerate and pick Generate a Document. Select your connection, or click Create a connection if this is your first time.

  3. 03

    Map the data

    Choose the template in the module, which Make lists once the connection exists. Then map each value from the previous module, such as a name or an amount, into the matching part of the template.

  4. 04

    Test with Run once

    Click Run once and send one test entry through your form. Open the bubble above each module to read the bundle it received, a bundle being one item passed from module to module.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on each new entry becomes a document without you opening DocuGenerate.

Triggers

DocuGenerate triggers in Make

2 modules start a scenario when something happens in DocuGenerate. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by DocuGenerate as soon as it happens.

DocuGenerate1Watch New Document

Watch New Document

Scheduled trigger

In Make“Triggers when a new document is generated from a template.”

This trigger hands your scenario each document that DocuGenerate generates from a template, so the file can travel on without anyone downloading it. Every document arrives as its own bundle, ready for the next module.

How it fires
scheduled. Make checks DocuGenerate on the scenario's schedule, so a document shows up at the next check rather than instantly.
When to use it
documents are created inside DocuGenerate by your team and you want each one filed in shared storage or sent to the client.
Watch out
each document processed counts operations on your Make plan, one per module that handles it.
DocuGenerate2Watch New Template

Watch New Template

Scheduled trigger

In Make“Triggers when a new template is created.”

You learn about every template created in your DocuGenerate account, without checking the library yourself. The scenario receives one bundle per new template and can pass its details to a chat tool, a spreadsheet or a task list.

How it fires
scheduled. Make checks DocuGenerate on the scenario's schedule and only sees new templates at that moment.
When to use it
several people design templates and a manager wants to review each one before it goes into daily use.
Watch out
a new template carries no customer data yet, so turning it into a real document still takes Generate a Document with values mapped from another app.
Modules

DocuGenerate actions in Make

DocuGenerate gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DocuGenerate1

Generate a Document

Action

In Make“Generates a document based on a template and a dynamic data set.”

Here is the module that produces the finished file: it takes one of your templates and fills it with the data mapped from earlier modules, a signed deal or a form entry for instance.

When to use it
a record in another app should become a quote, a contract or a certificate without copy and paste.
Watch out
run it once on test data first and open the result, a value mapped to the wrong spot shows up on every document after that.
DocuGenerate2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any part of the DocuGenerate API that the other modules leave aside, using the connection you already set up. No second key, no separate login.

When to use it
you need a DocuGenerate feature that none of the three other modules offers, and the vendor's API documentation describes the request.
Watch out
you write the request yourself here, so keep the DocuGenerate API reference open and test with Run once before going live.
Need help

Need help automating DocuGenerate with Make?

A person reads every message.

FAQ

DocuGenerate and Make: frequent questions

01Is the DocuGenerate Make integration free?
Yes, on the Make side. DocuGenerate is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need your own DocuGenerate account and subscription, whose pricing is set by DocuGenerate itself.
02What does it take to connect DocuGenerate to Make?
An active DocuGenerate account and an API key. You create the key in DocuGenerate under Settings, in the Developers tab, with the Generate API Key button, then confirm and copy it. In Make you add a DocuGenerate module, click Create a connection, optionally name it and paste the key. That connection is then shared by every DocuGenerate module in your scenarios, so the setup happens only once per DocuGenerate account.
03Do DocuGenerate triggers in Make work in real time?
No. Both Watch New Document and Watch New Template are scheduled triggers: Make checks DocuGenerate on the schedule of the scenario, which is every 15 minutes by default on a new scenario. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. If you need a document produced right after a form entry, start the scenario from the form app instead and use Generate a Document as the action.
04What if a DocuGenerate module is missing in Make?
Use Make an API Call. This module calls any endpoint of the DocuGenerate API with the connection you already have, so you can reach what the other three modules do not cover. You write the request from the DocuGenerate API documentation, then test it with Run once. The Make documentation for this app lists no specific limit, and it notes that its text is AI-generated from the vendor documentation, so check important details with DocuGenerate.
05Make or n8n for DocuGenerate?
It depends on which tool your team already works in. On Make, DocuGenerate offers 4 modules: two scheduled triggers, Generate a Document and Make an API Call, all reachable from the Free plan and built visually in the scenario editor. Apps like this one often have an n8n node as well, so check what exists there for your case. Compare the criteria that matter to you, such as the editor, the plan and the modules available, rather than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations