Resources · Make integration

PDF Generator API Make integrationAutomate PDF Generator API with Make.

Need a PDF filled with fresh data every time something happens in another app? The PDF Generator API Make integration gives you 2 action modules that merge a template with your data. This guide connects your account and walks you through a first working scenario.

Try the PDF Generator API integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PDF Generator API Make integration do?

The integration lets a Make scenario, the automation you build as a chain of modules, send data to one of your PDF Generator API templates and get back a finished document. You design the template once in PDF Generator API, and Make fills it with the values it picked up earlier in the flow, without any code.

A quote for every deal that is ready. A CRM or a form hands its fields to Make, and Generate Document merges them into your quote template. You get back the file itself, encoded in base64, ready for the next module to attach to an email or save to storage.

A shareable link instead of a file. Choose the public URL option and PDF Generator API hosts the document for you. Keep in mind that the link stops working after 30 days, since the stored file is deleted automatically.

Anything the listed modules skip. Make an API call reaches any other endpoint of the PDF Generator API, reusing the same connection, so you are not stuck with only one module.

The app has no trigger, so something else has to start the scenario: a module from another app, or the schedule of Make. If you are still weighing tools, the n8n vs Make comparison lays out both, and the Make pricing page explains how operations are counted. If you would rather hand it off, a Make agency can build it for you.

Connect

How do you connect PDF Generator API to Make?

  1. 01

    Gather your keys

    You need an active PDF Generator API account first. Open Account Settings there and copy three values: the API key, the API secret and the workspace identifier. Keep them in a safe spot for the next step.

  2. 02

    Open the connection window

    In your Make scenario, add a PDF Generator API module and click Create a connection. The Connection name field is optional, but a clear label helps when several workspaces live in the same Make account.

  3. 03

    Paste and save

    Paste the key, the secret and the workspace identifier into the matching fields, or follow the on-screen instructions, then save. The connection is your account linked to Make once, and every PDF Generator API module reuses it.

First scenario

Your first scenario with PDF Generator API

GoalWhen a new record shows up in another app, Make turns it into a PDF with PDF Generator API.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the +. Pick the app that holds your data, since PDF Generator API has no trigger of its own.

  2. 02

    Set up the source module

    Connect that app and fill its fields. Each record it returns becomes a bundle, one item that flows to the next module, carrying the values your PDF needs.

  3. 03

    Add Generate Document

    Click the + on the right, search PDF Generator API and pick Generate Document. Link your connection, choose your template and map the fields from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received and check the document that came back.

  5. 05

    Schedule and switch 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 PDF without you stepping in.

Modules

What PDF Generator API can do in Make

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

PDF Generator API1

Generate Document

Action

In Make“Merges template with data and returns base64 encoded document or a public URL to a document. You can send JSON encoded data in the request body or a public URL to your JSON file as the data parameter. When the public URL option is used, the document is stored for 30 days and automatically deleted.”

Hand it a template and your data, and it returns a finished document, either as a base64 file or as a public link. Your data goes in the request as JSON, or through a public URL to a JSON file.

When to use it
a signed order, a filled form or a closed deal needs its invoice, certificate or report produced without copying values by hand.
Watch out
with the public URL option, the document is kept for 30 days and then deleted, so keep a copy elsewhere.
PDF Generator API2

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

This one opens the rest of the PDF Generator API to your scenario: you write the request, and Make sends it with the connection you already set up, so there is no extra login to manage.

When to use it
you need something Generate Document does not cover, such as another endpoint described in the PDF Generator API documentation.
Watch out
you build the call yourself, so keep the vendor documentation open to get the endpoint and its parameters right.
Need help

Need help automating PDF Generator API with Make?

A person reads every message.

FAQ

PDF Generator API and Make: common questions

01Is the PDF Generator API Make integration free?
Yes, on the Make side. PDF Generator API is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 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) drop the interval to 1 minute and remove the cap on active scenarios. You still need your own PDF Generator API subscription, which is billed separately by the vendor.
02What do you need to connect PDF Generator API to Make?
An active PDF Generator API account and three values from its Account Settings: the API key, the API secret and the workspace identifier. In Make, add a PDF Generator API module, click Create a connection, optionally name it, paste the values and save. The connection is stored once and reused by both modules of the app, so the keys never have to be entered again in the same scenario or in the next one you build.
03Does the PDF Generator API Make integration have a trigger?
No. Both modules are actions, so the app cannot start a scenario by itself. Place a module from another app first, for example the tool where your orders or forms live, and let its records feed Generate Document. You can also start the scenario on the Make schedule, which runs every 15 minutes by default on a new scenario, or through an instant trigger of another app that calls Make through a webhook when something happens there.
04What if a PDF Generator API feature is missing in Make?
Use the Make an API call module. It can reach any endpoint of the PDF Generator API with the connection you already created, so a feature without its own module stays within reach. You write the request following the vendor documentation. Note that the Make documentation for this app is marked as AI-generated from the official PDF Generator API docs, so check important details with the vendor before relying on them in a live scenario.
05Should you use Make or n8n for PDF Generator API?
It depends on the tool your team already works in. Many apps have an n8n node as well as a Make app, so check whether this one does; the choice rarely comes down to a single integration. On Make, you get Generate Document, the Make an API call module and a visual editor where you can test with Run once. Compare both tools on your wider stack and on which one your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations