Resources · Make integration

Templated Make integrationAutomate Templated with Make.

Need an image or a PDF each time new data shows up in another app? The Templated Make integration gives you 5 modules: 4 actions and 1 search. This guide takes a Templated user from the API key to a first scenario that runs on its own.

Try the Templated integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Templated Make integration let you automate?

The Templated Make integration links your Templated account to Make, a visual tool that chains apps without code. Inside a scenario (the automation you build, one building block, called a module, after another), Templated produces an image or a PDF, fetches a render, merges renders into one PDF and lists your templates. It has no trigger, so another app or Make's schedule starts the flow.

A document for every new record. A row lands in a spreadsheet, a form gets a reply, an order comes in: the next module, Create a Render (image or PDF), turns that data into a finished file you can email or store.

One PDF instead of a stack of files. When a scenario already produces several renders, Merge Renders packs two or more of them into a single PDF, which suits a report or an onboarding pack.

A clear view of your designs. List Templates returns every template of your account as bundles (one item passed from a module to the next), so a scenario can log them in a table, the way the Airtable Make integration stores records.

What Make will not do here: Templated cannot start a scenario by itself, because the app has no trigger module. The Make documentation for Templated also says it was generated with AI from the vendor's docs, so verify anything critical with Templated. Many apps also have an n8n node; the n8n vs Make comparison lays out the criteria, and Make training helps if the editor is new to you.

Connect

How do you connect Templated to Make?

  1. 01

    Copy your API key

    Log in to Templated and open the API Integration tab of your dashboard. Your API key is listed there. Copy it now, since Make asks for it in the next step to reach your account.

  2. 02

    Add a Templated module

    In your scenario, click the +, search for Templated, pick a module such as Create a Render (image or PDF) and click Create a connection. A connection is your Templated account linked to Make once, and every Templated module reuses it.

  3. 03

    Paste the key and save

    Type a label in Connection name if you want one. It is optional, but it helps when several accounts sit side by side. Paste the API key you copied, confirm, and the module is ready to fill.

First scenario

Your first scenario: a file from fresh data

GoalWhen new data arrives in another app, Make runs Create a Render and Templated sends back an image or a PDF.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Start from the source of your data

    Pick the app where your data lives, such as the spreadsheet or form tool your team already uses, and choose its module. Templated has no trigger, so this first bubble starts the flow.

  3. 03

    Add Create a Render

    Click the + on the right of the first module, search for Templated and choose Create a Render (image or PDF). Select your connection, then map the data of the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can check that the render came back before going further.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Keep it or change it, then switch the scenario on.

Modules

What the 5 Templated modules do

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

Templated1

Create a Render (image or PDF)

Action

In Make“Generates a render for an image or PDF.”

You get a finished image or PDF back from Templated, produced inside your scenario instead of by hand in the editor. Most Templated scenarios are built around this module.

When to use it
a new signup, order or form reply should become a visual or a document without anyone opening Templated.
Watch out
each render costs one operation (one run of one module on one bundle, the unit Make counts on your plan), so a search that returns many bundles creates many renders.
Templated2

Get a Render

Action

In Make“Retrieves a single Render object referenced by its unique ID.”

This one hands you back a render that already exists, looked up by its unique ID, so a later step can reuse the file without generating it again.

When to use it
a render was created in an earlier run, its ID was saved in a sheet or a record, and you need that same file now.
Watch out
without an ID stored from Create a Render, there is nothing for this module to fetch.
Templated3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This is your way out when no ready-made module fits. It reaches any endpoint of the Templated API from your scenario, through the connection you already set up.

When to use it
the four other modules do not cover your case and the Templated API reference describes the call that does.
Watch out
you write the request yourself, so keep that reference open and test the call with Run once before you rely on it.
Templated4

Merge Renders

Action

In Make“Merge two or more renders into a single PDF”

Merge Renders leaves you with one PDF assembled from two or more renders, instead of a pile of separate files to send around.

When to use it
a scenario has produced several pages, say a cover, a detail sheet and a summary, and the recipient should get them as one document.
Watch out
the renders have to exist first, which usually means Create a Render runs earlier in the same flow.
Templated5

List Templates

Search

In Make“Lists all templates of the user.”

List Templates gives you every template stored in your Templated account, each one coming out of the module as its own bundle.

When to use it
you want to keep an inventory of your designs in a table your team reads, or pick the right template before a render.
Watch out
as a search, it can return zero, one or many bundles, and every module placed after it runs once per template.
Need help

Need help automating Templated with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Templated Make integration free?
Yes, on the Make side. Templated is a standard app, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a gap of at least 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, each month. You still need your own Templated account and API key.
02What do you need to connect Templated to Make?
An active Templated account and its API key. Once you are logged in to Templated, the key sits in the API Integration tab of your dashboard. In Make, add any Templated module, click Create a connection, type a Connection name if you want one, then paste the key. Make stores that connection once and every Templated module in your scenarios reuses it, so you go through this step a single time per account. The Make documentation lists no other prerequisite for this app.
03Can Templated start a Make scenario in real time?
No. Templated has no trigger module in Make, neither scheduled nor instant, so the app never starts a scenario by itself. You have two ways around that. The first module can belong to another app, the one where your data appears, with Templated placed right after it. Or Make's schedule opens the scenario: the clock on the first module runs it every 15 minutes by default, and no more often than that on the Free plan. In both cases Create a Render comes next in the flow.
04What if a Templated module is missing in Make?
Use Make an API Call. It can call any endpoint of the Templated API from inside your scenario, with the connection you already have, so it covers whatever Create a Render, Get a Render, Merge Renders and List Templates leave out. You write the request by hand, which means reading the Templated API reference first. Keep in mind that the Make documentation for this app carries a warning: it was generated with AI from the vendor's docs, so confirm anything important with Templated directly.
05Should you use Make or n8n with Templated?
It depends on where your automations already live. On Make, Templated offers 5 modules, a connection through an API key and Make an API Call for anything else, which is what this page covers. Many apps also have an n8n node, so check whether Templated has one before you decide. Base the choice on your own criteria: which tool your team already uses, who will maintain the scenarios and which editor they find easier to read. This page does not rank the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations