Resources · Make integration

APITemplate.io Make integrationAutomate APITemplate.io with Make.

Need PDFs and images to appear on their own when something happens in your other tools? In Make, APITemplate.io offers 8 modules: 7 actions and 1 search. This APITemplate.io Make integration guide covers the connection, a first scenario and when each module fits.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the APITemplate.io Make integration do for you?

The APITemplate.io Make integration lets Make produce documents and images in your APITemplate.io account without you clicking anything. You build a scenario (the automation itself, a chain of steps) out of modules (one brick each: an action, a search). Another app supplies the data, APITemplate.io turns it into a PDF or a picture.

Proposals straight from the CRM. A deal moves to won in your sales tool and Create a PDF turns its fields into a document ready to send. Nobody retypes the client name or forgets a line.

Web pages kept as a fixed copy. An online shop shows an order confirmation, a partner shares a report link: Create a PDF from URL saves the page as it looks at that moment, and List Objects finds every file produced later.

A visual for each new product. Create an Image builds a picture from catalog data once the item is added, which saves a round trip to a design tool.

What Make does not give you here is a trigger. APITemplate.io never starts a scenario by itself; another app or a schedule does. Make's documentation for this app is also thin, with no listed limits and no specific connection steps, so testing each module on real data is how you learn what it returns. The same app exists as an APITemplate.io n8n integration, the n8n vs Make comparison helps you pick a side, and Make training walks through the editor from zero.

Connect

How do you connect APITemplate.io to Make?

  1. 01

    Add an APITemplate.io module

    In your scenario, click the +, type APITemplate.io and pick any module, Create a PDF for instance. The connection (your APITemplate.io account linked to Make) will then serve all eight modules, so you set it up once.

  2. 02

    Create and name the connection

    Click Create a connection. Make lets you give it a name: use the workspace or client it belongs to. That label saves confusion the day you handle several accounts.

  3. 03

    Authorize and save

    Make then asks you either to approve access on the APITemplate.io side or to paste the key APITemplate.io gives you. Click Save and the module fields open up.

First scenario

Your first scenario: a PDF for every new form entry

GoalWhen someone fills in your form, Make asks APITemplate.io for a PDF built from the answers.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. This first module is the event that starts everything.

  2. 02

    Pick the starting app

    Search your form app, choose its module for new entries and connect your account. APITemplate.io has no trigger of its own, so another app always opens this flow.

  3. 03

    Add Create a PDF

    Click the + on the right of the first module, search APITemplate.io and pick Create a PDF. Select your connection, then map the form answers into the fields Make displays.

  4. 04

    Test with Run once

    Submit a test entry and click Run once. Open the bubble above each module to read its bundles (the items passed along): what the form sent, what APITemplate.io returned.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default on a new scenario) and turn the scenario on. From then on, each entry gets its PDF without you.

Modules

What each APITemplate.io module does

APITemplate.io gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

APITemplate.io1

Create an Image

Action

In MakeCreates an image.

Pictures rather than documents: this module asks APITemplate.io to produce an image from the data your scenario collected, so a visual exists without anyone opening a design tool. The result travels on as a bundle for the next module.

When to use it
a new product lands in your catalog and the listing or social post needs a matching visual.
Watch out
Make's documentation describes no size or format for it, so check with Run once what comes back before mapping it further.
APITemplate.io2

Create a PDF

Action

In MakeCreates a PDF.

The everyday document module. Data gathered earlier in the scenario goes in, and APITemplate.io hands back a finished PDF: a quote, a certificate, a delivery note.

When to use it
a deal is marked won in your CRM and the client should get a clean document without someone copying fields by hand.
Watch out
each document costs one operation (one run of one module on one bundle), so a search with many results placed before it means many PDFs.
APITemplate.io3

Create a PDF from HTML

Action

In MakeCreates a PDF from HTML

If an earlier step already writes the page in HTML, this module prints that markup straight to PDF, so the layout is the one your HTML already has.

When to use it
your helpdesk or shop app produces an HTML summary and you want it archived as a PDF on the customer record.
Watch out
what you send is what gets printed, so test on a real bundle; one empty variable leaves a visible gap in the page.
APITemplate.io4

Create a PDF from URL

Action

In MakeCreates a PDF from URL

Here the content already lives online. Give the module a web address and it saves that page as a PDF, frozen as it looked at that moment.

When to use it
an order confirmation page or a published report needs a lasting copy once its link shows up in another app.
Watch out
open the PDF from your Run once test and confirm it shows the page you expected, not a login screen or an error page.
APITemplate.io5

Delete an Object

Action

In MakeDeletes a generated image or PDF.

Cleanup duty. It removes an image or a PDF that APITemplate.io generated earlier, so your account keeps only the files that still matter.

When to use it
at the end of a scenario, once the document has been emailed or stored somewhere else.
Watch out
a deletion cannot be taken back from Make, so make sure the mapped value points to the right file and try the module on a test document first.
APITemplate.io6

Get Account Information

Action

In MakeGets account information.

Nothing gets created with this one. It reads the details of the connected APITemplate.io account and passes them on as data for the modules that follow.

When to use it
at the top of a scenario that generates a large batch, to check the account answers before the heavy work, or right after setting up a new connection.
Watch out
Make does not detail which fields come back, so run it once and read the bundle before building a filter on it.
APITemplate.io7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Your way around missing features. It sends a request to any endpoint of the APITemplate.io API through the connection you already have, so there is no second login to manage.

When to use it
the feature you need exists in the APITemplate.io API but none of the seven other modules covers it.
Watch out
you have to know the endpoint and its parameters from APITemplate.io's API documentation; when a ready module fits, it is the simpler choice.
APITemplate.io8

List Objects

Search

In MakeLists generated images and PDFs.

The only search module of the app. It returns the images and PDFs your account has already generated, one bundle per file, so later modules can act on each of them.

When to use it
before a cleanup with Delete an Object, or to keep a register of every document in a spreadsheet.
Watch out
a search can return zero, one or many items, and every module after it runs once per item, which adds operations quickly.
Need help

Need help automating APITemplate.io with Make?

A person reads every message.

FAQ

APITemplate.io and Make: common questions

01Is the APITemplate.io Make integration free?
Yes. APITemplate.io is a standard app in Make, so its modules work from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios every 15 minutes at the shortest, stops each run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Make counts every module run as an operation, so one PDF per bundle adds up. Your APITemplate.io subscription is a separate matter, handled on its side.
02What do you need to connect APITemplate.io to Make?
An APITemplate.io account and a Make account. Make's documentation for this app lists no prerequisite and no specific steps, so the generic flow applies: add a module, click Create a connection, name it if you like, approve access or paste the key APITemplate.io gives you, then click Save. One connection serves all 8 modules, Make an API Call included. If you produce documents for several brands or clients with separate accounts, create one connection per account and name each clearly, so no PDF ever comes out of the wrong one.
03Does APITemplate.io start Make scenarios in real time?
No, because APITemplate.io has no trigger module in Make. All 8 modules are actions or a search, so they always sit after something else. Two ways to start a scenario anyway. Put another app's trigger first, such as a form, a CRM or an online shop, so the document follows that event. Or run the scenario on Make's schedule, set on the first module: every 15 minutes by default, down to 1 minute on paid plans. How fast the scenario reacts then depends on that first module, not on APITemplate.io.
04What if an APITemplate.io module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the APITemplate.io API with the connection you already set up, so a feature the seven other modules skip stays within reach. You will need the endpoint and its parameters from APITemplate.io's own API documentation. Make's documentation lists no specific limits for this app; if a run fails, read the error in the bundle after Run once. Check your Make plan as well, since the Free plan caps each run at 5 minutes and files at 5 MB.
05Make or n8n for APITemplate.io?
It depends on where the rest of your automations run. APITemplate.io also has an n8n node, so both tools can generate your documents. In Make you get 8 ready modules, a visual editor where each step is a bubble, one shared connection and Make an API Call for anything the list leaves out. If your other workflows already live in n8n, keeping APITemplate.io there avoids splitting one process across two tools. If your team already builds in Make, these modules cover the core document jobs. The deciding factor is your existing setup, not the app.