Resources · Make integration

Pdforge Make integrationAutomate Pdforge with Make.

Need a PDF or an image built from your data without opening an editor? The Pdforge Make integration gives you 4 modules: 3 actions and 1 search. It suits anyone who already designs templates in Pdforge. This page shows how to connect the account and build a first working scenario.

Try the Pdforge integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pdforge Make integration let you automate?

The Pdforge Make integration links your Pdforge account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, here an action or a search on Pdforge. In practice, data from another app fills one of your Pdforge templates and comes out as a PDF or an image.

Documents that write themselves. A new row lands in a spreadsheet or a form is submitted, and Generate a PDF turns those values into a finished document from the template you designed in Pdforge. Each row becomes one bundle, the item that travels from one module to the next, so each one gets its own file.

Visuals for every record. A marketing team can feed product names or event details into Generate an Image and get a matching visual per record, ready to post or attach, without redrawing anything by hand.

A quick look at what you have. List all Templates returns the templates stored on your account, which helps when you want a scenario to pick the right one or simply check what exists.

Pdforge has no trigger in Make, so the scenario always starts from another app or from a schedule. When the listed modules fall short, Make an API Call reaches the rest of the Pdforge API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make training walks through scenario building step by step.

Connect

How do you connect Pdforge to Make?

  1. 01

    Copy your API key in Pdforge

    Sign in to your Pdforge account, open the API Keys menu in the sidebar and copy the key shown on screen. An active Pdforge account is required before anything else works.

  2. 02

    Add a Pdforge module in Make

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

  3. 03

    Paste the key and save

    Give the connection a label in Connection name if you like (it is optional), paste the key you copied, and confirm. Make can now read your templates and generate files.

First scenario

Build your first scenario with Pdforge

GoalWhen a new record appears in another app, Make fills a Pdforge template and produces a PDF.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pdforge has no trigger, so pick the app that holds your data, such as a form or a sheet.

  2. 02

    Add Generate a PDF

    Click the + on the right of that first module, search for Pdforge and choose Generate a PDF. Click Create a connection and paste your API key.

  3. 03

    Map the data into the template

    Select the template to use, then drag values from the first module into the matching places. Make shows what it can read once the connection exists, so nothing needs typing from memory.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the PDF output before trusting it with real records.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. From then on, each new record produces its own document.

Modules

What the Pdforge modules do

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

Pdforge1

Generate an Image

Action

In Make“Generate Image synchronously from template”

You get a finished image built from one of your Pdforge templates, with the values from earlier modules dropped into place, returned right away in the same run.

When to use it
a social visual, a badge or a product card per record, where a picture works better than a document.
Watch out
each generated image counts as an operation, one execution of a module, so a large batch of records uses as many operations.
Pdforge2

Generate a PDF

Action

In Make“Generate PDF synchronously from template”

This one hands back a complete PDF from a template, filled with the data your scenario carries, and the file is ready for the next module in the same run.

When to use it
an invoice, a certificate or a report that must follow a fixed layout every time a record is created elsewhere.
Watch out
the output only looks right if the template in Pdforge is finished, so test with Run once before activating.
Pdforge3

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call”

With this module you reach any endpoint of the Pdforge API from your scenario, using the connection you already set up, without building authentication yourself.

When to use it
when the three other modules do not cover what you need from Pdforge.
Watch out
you write the request yourself, so keep the Pdforge API documentation open next to the module while you fill it in.
Pdforge4

List all Templates

Search

In Make“Lists all created templates on your account.”

Here you receive the templates saved on your Pdforge account, one bundle per template, which lets a scenario see what is available before generating anything.

When to use it
to check your library or to route records toward the right template later in the flow.
Watch out
as a search it can return zero, one or several bundles, and every module placed after it runs once per template.
Need help

Need help automating Pdforge with Make?

A person reads every message.

FAQ

Pdforge and Make: frequent questions

01Is the Pdforge Make integration free?
Yes, on the Make side. Pdforge is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow 40 minutes of execution. You still need an active Pdforge account, whose pricing is set by Pdforge. Enterprise apps are the only ones reserved to the Enterprise plan, and Pdforge is not one of them.
02What do you need to connect Pdforge to Make?
An active Pdforge account and its API key. In Pdforge, open the API Keys menu from the sidebar and copy the key. In Make, add a Pdforge module, click Create a connection, optionally name it, then paste the key. The same connection is reused by all four Pdforge modules, so you only do this once per account. If Make rejects the connection, copy the key again from the API Keys menu and paste it in full.
03Does Pdforge trigger Make scenarios in real time?
No, because Pdforge has no trigger module in Make. Its modules are actions and one search, so a scenario starts somewhere else: a trigger from another app, such as a new form entry, or the schedule on the first module, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, and 1 minute on paid plans. To react to a specific event, place that app's trigger first and add Generate a PDF or Generate an Image right after it.
04What if a Pdforge module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Pdforge API with the connection you already created, so you can cover actions the three other modules leave out. You write the request based on the Pdforge API documentation. The Make documentation for this app is AI-generated from the vendor docs, so verify important details with Pdforge directly. Because it shares the existing connection, there is no second authentication to configure before sending your first request.
05Should you use Make or n8n for Pdforge?
It depends on your criteria. Make gives you four ready Pdforge modules, including Make an API Call for the rest of the API, inside a visual editor. Many apps also have an n8n node, so check whether one exists for Pdforge before deciding. Compare how each tool fits the apps around Pdforge in your workflow and the way your team prefers to build. Whatever you choose, test the flow with a single record first so you can see exactly what Pdforge returns.
Same platform

Other docs you might need on this stack.

Browse all integrations