Resources · Make integration

DocuPotion Make integrationAutomate DocuPotion with Make.

Can Make create DocuPotion documents for you while you work on something else? Yes: the DocuPotion Make integration has 2 action modules. This guide is for anyone who already uses DocuPotion and wants to link it to their other tools, with a first scenario to build and test.

Try the DocuPotion integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DocuPotion Make integration do?

The DocuPotion Make integration links your DocuPotion account to Make, a visual automation tool. You build a scenario, the automation itself, as a chain of modules, and each module is one brick doing one job. With DocuPotion, that job is creating a document, or calling its API directly when you need more.

A document created from a form answer. A new submission arrives in your form tool, Make passes its answers along as a bundle (one item moving from one module to the next), and Create a document produces the matching DocuPotion document. The 123FormBuilder Make integration is one way to feed it.

Paperwork after a booking. An appointment app confirms a slot, and the scenario turns that booking into a document without anyone copying details by hand. See the 10to8 Make integration for that starting point.

Anything the two modules skip. Make an API call reaches any endpoint of the DocuPotion API through the same connection, so you are not stuck with what the module list shows.

Know the limits before you start. DocuPotion has no trigger in Make, so it never starts a scenario on its own. The official documentation lists its modules without groups or descriptions, and it flags itself as AI-generated content to double-check with DocuPotion. Comparing platforms? Read n8n vs Make.

Connect

How do you connect DocuPotion to Make?

  1. 01

    Copy your API key

    Log in to DocuPotion and open the API Integration section of the dashboard. The API key is shown right there on screen: copy it and keep it handy for the next step.

  2. 02

    Add a DocuPotion module

    In your Make scenario, add any DocuPotion module and click Create a connection. The Connection name field is optional, but a clear name helps if you later link a second account.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, and confirm. That connection, your DocuPotion account linked to Make, is then reused by both DocuPotion modules.

First scenario

Build your first scenario with DocuPotion

GoalWhen new data lands in another app, Make creates the matching document in DocuPotion.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Since DocuPotion has no trigger, the first module comes from the app that holds your data, such as a form or booking tool.

  2. 02

    Add Create a document

    Click the + on the right of that first module, search for DocuPotion and pick Create a document. Choose the connection you made, or click Create a connection now.

  3. 03

    Map the fields

    Fill in the fields the module shows. For each one, click in the box and pick a value from the first module, so every document is built from the data that started the run.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; open them to check the document came out the way you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Modules

What the DocuPotion modules do

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

DocuPotion1

Create a document

ActionIn the docs only

This action produces a new DocuPotion document from the data your scenario carries, one document per bundle it receives. It is the module most DocuPotion scenarios are built around.

When to use it
right after the module that brings in the source data, like a signed order or a form reply, so the paperwork follows by itself.
Watch out
the official documentation gives no field list, so check what the module asks for in the editor before mapping.
DocuPotion2

Make an API call

ActionIn the docs only

Here you send your own request to any endpoint of the DocuPotion API, signed with the connection you already set up. It covers what Create a document alone does not.

When to use it
a task that has no dedicated module in Make, when you know which API endpoint handles it.
Watch out
you write the request yourself, so keep the DocuPotion API documentation open and test with Run once first.
Need help

Need help automating DocuPotion with Make?

A person reads every message.

FAQ

DocuPotion and Make: common questions

01Is the DocuPotion Make integration free?
Yes, on the Make side. DocuPotion is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. You still need an active DocuPotion account with an API key, and its subscription is set by DocuPotion, not by Make.
02What do you need to connect DocuPotion to Make?
An active DocuPotion account and its API key. You find the key in the API Integration section of the DocuPotion dashboard and copy it. In Make, add a DocuPotion module, click Create a connection, optionally give it a name, then paste the key or follow the on-screen instructions. The connection is saved once and both DocuPotion modules reuse it, so you never paste the key again for this account. Name it clearly if you plan to link more than one account.
03Does DocuPotion have a real-time trigger in Make?
No. DocuPotion has no trigger module in Make, scheduled or instant, so it cannot start a scenario by itself. The scenario starts elsewhere: either on the schedule you set on the first module, every 15 minutes by default, or with a trigger from another app. If that other app offers an instant trigger, it calls Make through a webhook as soon as something happens, and your DocuPotion document follows in the same run.
04What if the DocuPotion module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the DocuPotion API with the connection you already have, so you are not limited to Create a document. You need to know which endpoint does the job, and the DocuPotion API documentation is the place to check. Keep in mind that the Make documentation for this app is marked as AI-generated, so confirm anything important directly with DocuPotion. Test each new request with Run once before switching the scenario on.
05Should you use Make or n8n for DocuPotion?
It depends on where the rest of your automations already run. Make gives DocuPotion 2 modules, Create a document and Make an API call, available from the Free plan among more than 3000 standard apps. n8n often has a node for the same apps, so check whether it offers one for DocuPotion before choosing. If your other scenarios live in Make, adding DocuPotion there keeps everything in one place and one set of connections.
Same platform

Other docs you might need on this stack.

Browse all integrations