Resources · Make integration

Docupilot Make integrationAutomate Docupilot with Make.

Need a filled-in document each time a record lands in another tool? The Docupilot Make integration has 1 action, Create a Document, and no trigger of its own. This guide is for teams who already use Docupilot templates and want Make to fill them without code.

Try the Docupilot integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Docupilot Make integration do for you?

With it, a Make scenario, the automation you build in Make, produces a Docupilot document from one of your templates using data that comes from another app. There is exactly one module, a brick of the scenario, called Create a Document. Something else starts the flow, and Docupilot does the writing.

A contract that drafts itself. A sales tool marks a deal as won, the scenario passes the client name and terms to Create a Document, and the contract template comes back filled. The person who closed the deal no longer copies fields by hand.

Onboarding paperwork on arrival. A new hire appears in your HR spreadsheet or form tool. Make maps the row into a welcome letter template, so the file exists before anyone asks for it.

Quotes built from a form. A prospect fills in a request form. Each answer becomes a value in a quote template, and the generated document can travel to the next module, such as an email or storage app.

What Make cannot do here matters just as much. Docupilot has no trigger, no search and no Make an API Call module in Make, so the scenario always starts in another app or on a schedule, and it cannot look up documents that already exist. The Make review gives the wider picture of the platform. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training walks through mapping data between modules.

Connect

How do you connect Docupilot to Make?

  1. 01

    Generate an API key in Docupilot

    In Docupilot, open the Dashboard, click the Settings icon in the left menu and choose API Settings. Click Add API Key, give the token a name, press Generate and copy the key. Keep your Workspace ID at hand as well.

  2. 02

    Add the module and open the connection

    In your scenario, add the Create a Document module and click Create a connection. A connection is your Docupilot account linked to Make once, then reused by any Docupilot module. The Connection name field is optional.

  3. 03

    Paste your credentials and save

    Enter the API key with its secret and your Workspace ID, exactly as copied from Docupilot, then confirm. If the on-screen instructions ask for something else, follow them: they reflect what Docupilot currently expects.

First scenario

Build your first scenario with Docupilot

GoalWhen a new record appears in another app, Make fills a Docupilot template and creates the document.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Docupilot has no trigger, this first module comes from the app that holds your data.

  2. 02

    Pick the starting app

    Search that app by name, choose the trigger that watches for new records and create its connection. Make then lists the objects it can read, so you pick the right source from a menu.

  3. 03

    Add Create a Document

    Click the + on the right of the first module, search Docupilot and pick Create a Document. Connect your account, choose the template and map values from the previous module into it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles, the items passed from one module to the next, and check the document that came out.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run counts as an operation on your Make plan.

Modules

What the Docupilot module does

Docupilot gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Docupilot1

Create a Document

Action

In Make“Create document from selected template”

You get a finished Docupilot document built from the template you pick, filled with values mapped from earlier modules and ready to pass further down the scenario.

When to use it
every time data sitting in another tool should end up as a contract, letter or quote without anyone retyping it.
Watch out
it is an action, so it works on one bundle at a time; if the previous module sends ten records, it produces ten documents and uses ten operations.
Need help

Need help automating Docupilot with Make?

A person reads every message.

FAQ

Docupilot and Make: frequent questions

01Is the Docupilot Make integration free?
Yes, on the Make side. Docupilot is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and files at 5 MB, and includes 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Docupilot account with API access, and its subscription is set by Docupilot, not by Make.
02What does it take to connect Docupilot to Make?
You need three things from an active Docupilot account: an API key, the secret that comes with it, and your Workspace ID. The key is generated under Settings, then API Settings, with the Add API Key button. In Make, add the Create a Document module, click Create a connection, optionally name it, and paste the credentials. The connection is stored once and every future Docupilot module in your scenarios can reuse it.
03Can Docupilot start a Make scenario in real time?
No. Docupilot has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. The scenario begins elsewhere: with the trigger of the app that holds your data, which may be instant if that app offers one, or with a schedule set on the first module, every 15 minutes by default. Create a Document then runs as the next step once that first module hands over its bundles.
04What if a Docupilot module is missing in Make?
It depends on what is missing. The Docupilot app in Make only offers Create a Document and has no Make an API Call module, so there is no generic way to reach other Docupilot features from this app. If you need to list, search or react to documents, look at whether another app in your stack can cover that part, or ask the team for help to design a workaround that fits your process.
05Make or n8n for Docupilot: which one fits?
It depends on your criteria. On Make, Docupilot gives you one action, Create a Document, available from the Free plan, and every other step comes from the rest of your scenario. Many apps also have an n8n node, so check whether one exists for Docupilot and what it covers before choosing. Compare the modules each side offers for your exact use case, the way each tool counts usage and the setup your team is comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations