Resources · Make integration

TemplateDocs Make integrationAutomate TemplateDocs with Make.

What if every new deal or signup produced its document without anyone opening a template? The TemplateDocs Make integration gives you 2 action modules. This guide shows how to link your account, build a first scenario and pick the right module.

Try the TemplateDocs integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TemplateDocs Make integration do for you?

The TemplateDocs Make integration lets Make create documents for you from templates you already keep in TemplateDocs. You build a scenario, the automation you design in Make as a chain of modules, and each module is one brick of it: here, the step that produces the document.

Proposals that write themselves. When a deal moves forward in your CRM, a scenario passes the client details to Generate a Document, which creates the proposal from your standard template. Your sales team starts from a finished file instead of a blank copy.

Onboarding packs on signup. A new form entry or a new row in a sheet can feed the same module, so each customer gets their welcome document built from the same template, with their own data mapped in.

Anything the listed module skips. Make an API Call reaches any endpoint of the TemplateDocs API with the connection you already set up, which covers what the ready-made module does not.

One thing to know up front: TemplateDocs has no trigger in Make, so it never starts a scenario on its own. Another app, or the schedule you set in Make, kicks things off. If you are new to the editor, the Make training walks through it, and Make pricing explains how runs are counted. The same app may also exist as an n8n node; n8n vs Make lays out the criteria for choosing.

Connect

How do you connect TemplateDocs to Make?

  1. 01

    Copy your API key

    You need an active TemplateDocs account and an API key. In your TemplateDocs dashboard, open the API Keys section and copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a TemplateDocs module

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions.

First scenario

Your first scenario with TemplateDocs

GoalWhen a new record arrives in another app, Make generates a document from your TemplateDocs template.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since TemplateDocs has no trigger, start with the app where your data lives, such as your form tool or CRM.

  2. 02

    Set up the starting module

    Pick that app's module, link your account with Create a connection and fill its fields. Each record it returns travels as a bundle, one item passed from one module to the next.

  3. 03

    Add Generate a Document

    Click the + on the right of the first module, search for TemplateDocs and choose Generate a Document. Link your TemplateDocs connection, then fill the fields by mapping data from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check the document Generate a Document produced.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon, every 15 minutes by default, then switch the scenario on. From now on, each new record produces its document without you.

Modules

What the TemplateDocs modules do

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

TemplateDocs1

Generate a Document

Action

In Make“Create a new document from an existing template”

This action turns each incoming record into a new document, built from a template you have already designed in TemplateDocs. The layout stays in one place; Make supplies the details.

When to use it
right after the module that brings in your data, such as a new form entry or a deal that just closed.
Watch out
it acts on each bundle it receives, so a test with Run once creates a real document and counts one operation, a single run of a module on your Make plan.
TemplateDocs2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here you get a door to the whole TemplateDocs API, reusing the connection you already created, so you are not limited to the one ready-made action. It sends any authorized request you write yourself.

When to use it
when Generate a Document does not cover the task and the TemplateDocs API documentation lists an endpoint that does.
Watch out
you build the request yourself, so keep the vendor's API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating TemplateDocs with Make?

A person reads every message.

FAQ

Questions about TemplateDocs and Make

01Is the TemplateDocs Make integration free?
Yes, on the Make side. TemplateDocs is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one run of one module on one bundle. Your TemplateDocs subscription is separate: check the TemplateDocs pricing page for what your account includes.
02What do you need to connect TemplateDocs to Make?
An active TemplateDocs account and its API key. In the TemplateDocs dashboard, the API Keys section shows the key to copy. In Make, add a TemplateDocs module, click Create a connection, optionally give it a name, then paste the key or follow the on-screen instructions. The connection is then shared by both TemplateDocs modules, so you only set it up once per account, and every new scenario can pick it from the list.
03Can a TemplateDocs scenario start in real time?
Not from TemplateDocs itself, because the app has no trigger module in Make. The scenario starts from another app instead. If that app offers an instant trigger, it calls Make through a webhook as soon as something happens, and the document follows right after. If it offers a scheduled trigger, Make checks it on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. You can also run a scenario on a schedule alone.
04What if the TemplateDocs module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the TemplateDocs API with the connection you already have, so an action that Generate a Document does not offer can still run inside your scenario. You write the request yourself from the TemplateDocs API documentation. Make also notes that its TemplateDocs help page was drafted with AI from the vendor's documentation, so confirm important details with TemplateDocs directly before relying on them in production.
05Should you use Make or n8n for TemplateDocs?
It depends on the tool your team already works in. In Make, TemplateDocs is a standard app with 2 action modules, reachable from the Free plan, and Make an API Call covers the rest of its API. Many apps also have an n8n node, so check whether TemplateDocs has one before deciding. The deciding criterion is where your other scenarios already live, and whether the two TemplateDocs modules cover your documents.
Same platform

Other docs you might need on this stack.

Browse all integrations