Resources · Make integration

TemplateFox Make integrationAutomate TemplateFox with Make.

Can Make produce your PDFs while you focus on the work that fills them? The TemplateFox Make integration gives you 2 action modules and no trigger. This guide is for people who already use TemplateFox and have never built a scenario, and it walks you through the connection and a first working flow.

Try the TemplateFox integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the TemplateFox Make integration do?

The TemplateFox Make integration links your TemplateFox account to Make, a visual tool where you chain apps together without writing code. Inside a scenario, the automation you build in Make, TemplateFox acts as a document step: something happens in another app, and Make asks TemplateFox for a PDF.

Think of it as the last mile of a process you already run. A sales team closing a deal in its CRM can pass the buyer details to Generate PDF and get the document without copying a single line by hand. An operations lead can do the same with rows collected from a form, so each submission becomes its own PDF.

When the two listed modules stop short of what you need, Make an API Call reaches any endpoint of the TemplateFox API with the connection you already set up. That is the escape hatch for anything the ready-made action does not expose.

Be clear about the limits. TemplateFox has no trigger in Make, so it never starts a scenario on its own: another app or the Make schedule has to do that. Make also says its own documentation for this app is limited, so expect to test with Run once rather than read a detailed reference. If you want a broader view of the platform first, the Make review covers its strengths and weak spots, and Make pricing explains what counts against your plan.

TemplateFox may also be reachable from n8n. If you are weighing the two tools, the n8n vs Make comparison sets out the criteria side by side.

Connect

How do you connect TemplateFox to Make?

  1. 01

    Open the connection window

    Add a TemplateFox module to your scenario, for example Generate PDF, then click Create a connection. A connection is your TemplateFox account linked to Make once and reused by every TemplateFox module you add later.

  2. 02

    Name it so you can find it again

    Giving the connection a name is optional, but it helps as soon as a colleague or a second TemplateFox account joins the picture. A label such as the workspace or client name is enough to tell connections apart in the list.

  3. 03

    Authorize Make and save

    Depending on what TemplateFox offers, either approve Make on the TemplateFox page that opens or paste the key TemplateFox gives you. Then click Save, and the module is ready for its fields.

First scenario

How do you build your first scenario with TemplateFox?

GoalWhen a new record shows up in another app, Make asks TemplateFox to generate a PDF from it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas. Pick the app that holds your data, such as your CRM or your form tool, and choose the module that watches new records.

  2. 02

    Connect the source app

    Click Create a connection for that first app and fill its fields. Once the account is linked, Make lists the folders, sheets or objects it can read, so you pick them instead of typing names.

  3. 03

    Add Generate PDF

    Click the + on the right of the first module, search for TemplateFox and choose Generate PDF. Link your TemplateFox connection, then map the values coming from the first module into the fields Make shows you.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received, one bundle being one item passed along, and check that TemplateFox returned a document.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default for a new scenario. Then turn the scenario on so it keeps running without you.

Modules

What can TemplateFox do in Make?

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

TemplateFox1

Generate PDF

ActionIn the docs only

You get a PDF produced by TemplateFox from the data your scenario feeds it, with no copy and paste. It is an action, so it runs once for every bundle that reaches it.

When to use it
right after the module that brings in a signed deal, a new order or a form answer, when that record should turn into a document.
Watch out
Make publishes almost nothing about this module, so test it with Run once and check the output before switching the scenario on.
TemplateFox2

Make an API Call

ActionIn the docs only

This module gives you access to any endpoint of the TemplateFox API while reusing the connection you already created, so you do not have to handle authentication yourself. It covers what Generate PDF does not offer.

When to use it
when a TemplateFox feature you rely on has no dedicated module in Make, and you know which endpoint handles it.
Watch out
you need the TemplateFox API reference at hand, because Make does not describe the requests this module can send for this app.
Need help

Need help automating TemplateFox with Make?

A person reads every message.

FAQ

TemplateFox and Make: common questions

01Is the TemplateFox Make integration free?
Yes, on the Make side. TemplateFox is a standard app, so its modules are available from the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module run on one bundle is an operation, and operations are what Make counts on your plan. Paid plans lift the interval to 1 minute and allow unlimited active scenarios. What TemplateFox itself charges is a separate question to check with TemplateFox.
02What do you need to connect TemplateFox to Make?
A TemplateFox account and a Make account. Make's documentation lists no special prerequisite for this app, so the connection follows the usual path: add a TemplateFox module, click Create a connection, optionally give it a name, then either authorize Make on the TemplateFox page or paste the key TemplateFox provides, and click Save. The same connection then serves both TemplateFox modules, Generate PDF and Make an API Call. Because Make describes its own documentation for TemplateFox as limited, run the module once after connecting to confirm the account responds.
03Does the TemplateFox Make integration react in real time?
Not by itself. TemplateFox has no trigger in Make, so nothing in TemplateFox can start a scenario. The first module has to come from another app. If that app offers an instant trigger, it calls Make through a webhook as soon as something happens and the PDF follows right away. If it offers a scheduled trigger, Make checks it on the scenario schedule, every 15 minutes by default and never more often than that on the Free plan. You can also start the scenario from the Make schedule alone.
04What if a TemplateFox module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the TemplateFox API with the connection you already have, which covers everything beyond Generate PDF. The catch is documentation: Make says it cannot offer complete documentation for TemplateFox because too little public information exists about the app, so you will need the TemplateFox API reference to know which endpoint to call. Test each request with Run once and inspect the bundle it returns before you rely on it in a live scenario.
05Should you use Make or n8n for TemplateFox?
It depends on the tool your team already builds in. On Make, TemplateFox comes with Generate PDF and Make an API Call, and it works from the Free plan. Many apps also have an n8n node, so check whether TemplateFox has one before you decide. Compare the modules each side offers for your use case, where your other automations already live, and who will maintain the flow. Neither answer is right for everyone, and the choice rarely depends on TemplateFox alone.
Same platform

Other docs you might need on this stack.

Browse all integrations