Resources · Make integration

Documint Make integrationAutomate Documint with Make.

Your data already lives somewhere, so why retype it into a template? The Documint Make integration gives you 3 modules: 2 actions and 1 search. This page shows how to plug in your API key and build a first scenario that fills a template for you.

Try the Documint integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Documint Make integration let you automate?

The Documint Make integration links your Documint account to a Make scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain. Here, the bricks produce documents from your templates and read the list of templates you already designed.

Quotes that write themselves. A deal moves forward in your CRM, and the next module, Create a document, merges the deal data into your quote template. Sales stops copying names and amounts by hand.

A template inventory you can act on. List Templates returns your Documint templates as bundles, the items Make passes from one module to the next. Feed them to a spreadsheet or a filter to see what exists before you build more.

Anything the menu does not show. Make an API Call reaches any endpoint of the Documint API with the same connection, so you are not stuck with the two ready-made modules.

What the integration does not do: Documint has no trigger in Make. Your scenario starts from another app or from a schedule set in Make. Compare the options in the n8n vs Make guide, check plan limits on Make pricing, or get hands-on with the Make training.

Connect

How do you connect Documint to Make?

  1. 01

    Create an API key in Documint

    In Documint, open the left sidebar and click Integrations, then Create API Key. Give it a name in API Key Name, click Create, and copy the value somewhere safe.

  2. 02

    Open a connection in Make

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

  3. 03

    Paste the key and save

    Name the connection if you like in Connection name, paste your key into API Key, and click Save. If Documint asks you to authenticate and confirm access, accept it.

First scenario

Build your first scenario with Documint

GoalWhen a new record appears in the app that holds your data, Make fills a Documint template and creates the document.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your data lives, a CRM or a sheet for instance, as the first module.

  2. 02

    Add Create a document

    Click the + on the right of that first module, search for Documint and choose Create a document. Link your account with Create a connection if you have not done it yet.

  3. 03

    Map the data

    Fill the module fields. Make shows what it can read once the connection exists, and you drag values from the first module into the template data, so each record fills its own document.

  4. 04

    Test with Run once

    Click Run once. The scenario runs a single time, and each module shows the bundles it received. Open the result of Create a document to confirm the right data landed in the template.

  5. 05

    Schedule and switch it on

    Set the clock on the first module, every 15 minutes by default, and turn the scenario on. Each run of each module counts as an operation, the unit Make bills on your plan.

Modules

What can the Documint modules do in Make?

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

Actions

2 modules
Documint1

Create a document

Action

In Make“Creates a document by merging your data into a template.”

Get a finished document without touching the template: this action takes the data coming from earlier modules and merges it into one of your Documint templates. One bundle in, one document out.

When to use it
a contract, a quote or a certificate has to go out the moment a record is ready elsewhere.
Watch out
Run once on a single record before switching on, since every bundle produces its own document.
Documint2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach the parts of Documint that the ready-made modules skip: this action calls any endpoint of the Documint API, using the connection you already set up, so no second key is needed.

When to use it
the task you have in mind is neither creating a document nor listing templates.
Watch out
you write the request yourself, so keep the Documint API reference open while you build it.

Searches

1 module
Documint3

List Templates

Search

In Make“Lists your Documint templates.”

See every template in your account as data you can reuse: this search returns your Documint templates, one bundle per template, ready to send to a sheet, a filter or a later module.

When to use it
you want an inventory of templates, or a scenario that picks one before generating anything.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
Need help

Need help automating Documint with Make?

A person reads every message.

FAQ

Documint Make integration: frequently asked questions

01Is the Documint Make integration free?
Yes on the Make side, with a condition on the Documint side. Documint is a standard app, available from the Make Free plan, which allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid Make plans lower the interval to 1 minute and remove the cap on active scenarios. Documint itself, though, requires a paid Documint account for the app to work in Make, so check your Documint subscription before building.
02What do you need to connect Documint to Make?
You need a paid Documint account and an API key. In Documint, click Integrations then Create API Key in the left sidebar, name the key and copy its value. In Make, add a Documint module, click Create a connection, paste the key into the API Key field and click Save. If Documint asks you to authenticate and confirm access, accept. The connection is then reused by all three Documint modules, so you only do this setup once per account.
03Does the Documint Make integration react in real time?
No, because Documint has no trigger in Make. Your scenario has to start somewhere else. The first option is the trigger of another app, a CRM or a form for example, placed before Create a document. The second is a schedule on the first module, which runs every 15 minutes by default and can go down to 1 minute on paid plans. On the Free plan, the minimum stays at 15 minutes between two scheduled runs.
04What if the Documint module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Documint API through the same connection, which covers what Create a document and List Templates do not. You will need the Documint API reference to write the request. The Documint documentation in Make lists no numeric limit for these modules, so the usual limits to watch are those of your Make plan, such as execution time and file size on the Free plan.
05Should you use Make or n8n for Documint?
It depends on how you like to build. In Make, Documint comes with 3 modules, runs on a standard plan from Free upward, and relies on an API key set once in a connection. Make an API Call covers the rest of the API. An n8n node may exist for the same app too; if you weigh both tools, compare the modules each one offers for Documint, how you prefer to design workflows and the plan limits that apply to your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations