Resources · Make integration

DynamicPDF API Make integrationAutomate DynamicPDF API with Make.

Need PDFs built and read by your automations, without writing code? The DynamicPDF API Make integration gives you 10 action modules: create PDFs and reports, pull text and metadata, turn pages into images. This page shows how to connect your key and build a first scenario.

Try the DynamicPDF API integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DynamicPDF API Make integration let you automate?

The DynamicPDF API Make integration links your DynamicPDF API account to Make, so a scenario (the automation you build, a chain of modules) can create PDF files and read what is inside existing ones. Each module is one brick of that chain, and all ten here are actions: something else has to start the scenario.

Documents that write themselves. An order or a signed form lands in another tool, and Create PDF (pdf json) or Create Report (dlex-layout DlexPath) turns that data into a PDF, which the next module can send or store.

PDFs you can search. A supplier sends a document, Get PDF text (pdf-text) extracts the words, and a later module files them in a sheet or a CRM. Get PDF security info (pdf-security-info) tells you, before any of that, whether the file is protected.

Pages turned into pictures. Rasterize PDF (pdf-image) renders a PDF as an image for a preview, and Get image metadata (image-info) describes an image file.

What Make does not do here: the app has no trigger, no Make an API Call module, and the Make documentation gives no description for any module, so open each module and read its fields before you count on it. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and Make training covers the editor from the ground up.

Connect

How do you connect DynamicPDF API to Make?

  1. 01

    Open the connection window

    Add any DynamicPDF API module to your scenario, then click Create a connection. A connection is your DynamicPDF API account linked to Make once, and every module of the app reuses it afterward.

  2. 02

    Name it and paste your key

    Give the connection a name if you like, for example the workspace it belongs to. Then paste the API key from your DynamicPDF API account. Without an active account and a key, Make has nothing to connect to.

  3. 03

    Save and check the fields

    Click Save. Make returns to the module, which now shows its fields. If the key is wrong, this is where the connection fails, so fix it here before you build the rest of the scenario.

First scenario

Your first scenario with DynamicPDF API

GoalWhen another app hands Make a PDF, DynamicPDF API first checks whether the file is protected, then pulls its text for the next step.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since DynamicPDF API has no trigger, pick the module of the app where your PDFs arrive as the first brick.

  2. 02

    Add the security check

    Click the + on the right of that first module, search for DynamicPDF API and choose Get PDF security info (pdf-security-info). Select your connection, or create it now, and map the file coming from the first module.

  3. 03

    Add Get PDF text

    Add Get PDF text (pdf-text) next and map the same file. Each file travels as a bundle, one item passed from a module to the next, so both steps handle one PDF at a time. A filter between the two can hold back locked files.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and lets you open the bundles each module received, so you can read the extracted text before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module that runs on a bundle counts as one operation on your Make plan.

Modules

What each DynamicPDF API module does in Make

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

DynamicPDF API1

Create PDF (pdf json)

ActionIn the docs only

You get a new PDF built from instructions your scenario sends to DynamicPDF API. The "json" in its name says those instructions go out as structured data, so reach for it when everything the PDF needs already sits in earlier modules.

When to use it
an order or a form entry arrives upstream and you want a matching PDF without leaving Make.
Watch out
Make documents no fields for it, so open the module and read what it asks before mapping anything.
DynamicPDF API2

Create PDF (pdf multipart-form)

ActionIn the docs only

Another PDF comes out of this module, but its name says the request travels as a multipart form rather than as JSON. That variant is worth a look when your inputs are files coming from earlier modules rather than plain data.

When to use it
your source material is a file from another app rather than a set of values; check in the module how it takes files.
Watch out
the documentation describes neither variant, so compare the fields of both modules before you choose.
DynamicPDF API3

Create Report (dlex-layout DlexPath)

ActionIn the docs only

A finished report lands in your scenario, built on a layout, which the module name calls a DLEX layout. Judging by that name, this variant points to the layout through a path rather than sending it, which suits a template you reuse.

When to use it
every invoice or statement follows the same design and only the data changes.
Watch out
the path format is not documented in Make; test with Run once on a single bundle first.
DynamicPDF API4

Create Report (dlex-layout form)

ActionIn the docs only

Your scenario receives a report built on a DLEX layout here too, but the name suggests the layout goes out as a form upload with the request. That makes it the option when the template lives in another tool rather than in your DynamicPDF API account.

When to use it
your team keeps layout files in a shared drive and the scenario fetches them first.
Watch out
fields are undocumented in Make, so check the module before mapping.
DynamicPDF API5

Get PDF Metadata (pdf-info)

ActionIn the docs only

Your scenario learns the basic facts stored in a PDF, which lets later modules route the file without opening it. As its name says, it returns metadata, not the page content, which is often all a sorting step needs.

When to use it
you want to label incoming files before deciding where each one goes.
Watch out
Make lists no output fields; run it once and read the bundle to see what it returns.
DynamicPDF API6

Get PDF XMP metadata (pdf-xmp)

ActionIn the docs only

The XMP metadata of a PDF lands in your bundle: a second set of descriptive data that some tools write into the file. Choose it over Get PDF Metadata when the details you need were written by publishing or archiving software.

When to use it
a library of published PDFs must be catalogued with the data their authors embedded.
Watch out
a PDF without XMP data may return little, so test it on a real file from your own flow first.
DynamicPDF API7

Get PDF security info (pdf-security-info)

ActionIn the docs only

A clear view of the security settings of a PDF reaches you before your scenario tries to read or change it. That check keeps a protected file from breaking the steps that come after it.

When to use it
supplier files arrive from many sources and some of them may be locked.
Watch out
add a filter after it so locked files take another path; Make does not document the fields it returns, so read one bundle first.
DynamicPDF API8

Get PDF text (pdf-text)

ActionIn the docs only

You get the words inside a PDF as text your next modules can search, copy into a sheet or send to a CRM. It is the module to pick when the content matters more than the file itself.

When to use it
quotes or contracts land in a shared folder and you need their content in your records.
Watch out
the documentation says nothing about scanned pages, so try a scan through Run once before trusting the result.
DynamicPDF API9

Get image metadata (image-info)

ActionIn the docs only

Image details reach your scenario with this one: it reads the metadata of a picture rather than a PDF, as its name states. It fits scenarios that check visuals before they go into a document built by one of the Create modules.

When to use it
product photos must be checked before they are placed in a catalog PDF.
Watch out
no fields are documented in Make, so test it on one real image and read the bundle before building on it.
DynamicPDF API10

Rasterize PDF (pdf-image)

ActionIn the docs only

Pictures of your PDF pages are what you end up with: rasterizing means turning pages into images, so any app can display the document. Use it when the receiving tool shows images but cannot open a PDF.

When to use it
a preview of a generated report should appear in a chat message or a web page.
Watch out
image files can grow large, and the Free plan caps files at 5 MB in Make.
Need help

Need help automating DynamicPDF API with Make?

A person reads every message.

FAQ

Questions about the DynamicPDF API Make integration

01Is the DynamicPDF API Make integration free?
Yes, on the Make side. DynamicPDF API is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute and lift the limit on active scenarios. You still need an active DynamicPDF API account with an API key, and its subscription is set on the DynamicPDF API side.
02What does it take to connect DynamicPDF API to Make?
An active DynamicPDF API account and the API key that comes with it. In Make, you add any module of the app, click Create a connection, optionally name it, paste the key and click Save. That connection is then shared by all ten modules, so you only do it once. If Make refuses the key, the account itself is the first thing to check, since the key only works while the DynamicPDF API account is active.
03Can DynamicPDF API start a Make scenario in real time?
No, because the app has no trigger module. A DynamicPDF API module always runs after something else starts the scenario. You can open the scenario with a trigger from the app where your documents arrive, instant or scheduled depending on that app, or simply let Make run it on a schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval between scheduled runs, while paid plans go down to 1 minute.
04What if a DynamicPDF API module is missing in Make?
It depends on what you need. This app has no Make an API Call module, so you cannot send a custom request through your DynamicPDF API connection. First check the ten existing modules, since several variants exist for creating PDFs and reports. If none fits, another app in Make may cover the step, or the team at Hackceleration can look at your case and suggest a way to build it.
05Make or n8n for DynamicPDF API?
It depends on your criteria. In Make, DynamicPDF API brings 10 action modules and works from the Free plan, but it has no trigger and no Make an API Call module, so any request outside those ten is out of reach there. Many apps also have an n8n node; check whether this one does and compare its operations with the list on this page. Choose the tool whose modules cover your steps and whose editor your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations