Resources · Make integration

PDF Munk Make integrationAutomate PDF Munk with Make.

Need a PDF or a picture of a web page without opening a browser? The PDF Munk Make integration gives you 5 action modules that capture websites and convert HTML. This guide is for anyone who builds documents by hand today: connect your key, then build your first scenario.

Try the PDF Munk integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PDF Munk Make integration do for you?

The PDF Munk Make integration lets a Make scenario, the automation you build in Make, ask PDF Munk to turn a web address or a piece of HTML into a PDF or an image. Each step of that chain is a module, and PDF Munk brings five of them, all actions.

Archive a page as it looked. A compliance or marketing team that must keep proof of a landing page can send its address to Capture a Website Screenshot into PDF and file the result with another app. The same idea works with Capture Website Screenshot when a picture is enough, for a visual review or a report.

Produce documents from your own HTML. If your tools already hold a quote or a receipt as HTML, Convert HTML to PDF turns it into a document you can attach to an email or drop into storage. Convert HTML to an Image does the same when the destination expects a picture, such as a social post or a chat message.

Reach the rest of the API. Make an API Call reuses your connection to call any PDF Munk endpoint that the four ready-made modules leave out.

What the integration does not do: PDF Munk has no trigger in Make, so it never starts a scenario on its own. Another app or the scenario's schedule decides when it runs. The official documentation is also flagged as AI-generated by Make, so check the details with PDF Munk before relying on them. The same app may exist in n8n; the n8n vs Make comparison helps you pick, and Make pricing explains how operations are counted. For hands-on practice, see Make training.

Connect

How do you connect PDF Munk to Make?

  1. 01

    Copy your API key

    You need an active PDF Munk account. In its dashboard, open the top-left menu, click My Account and copy the API key shown on that page. Keep it at hand for the next step.

  2. 02

    Add a PDF Munk module

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, which helps when several accounts coexist. Paste the key you copied, confirm, and Make keeps it for all your scenarios.

First scenario

Build your first scenario with PDF Munk

GoalWhen another app hands Make a piece of HTML, Make asks PDF Munk to turn it into a PDF.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Since PDF Munk has no trigger, the first module comes from the app that holds your HTML.

  2. 02

    Pick the starting module

    Search for that app, choose the module that returns the HTML you need, and link its account. Once connected, Make lists what it can read so you can pick the right source.

  3. 03

    Add Convert HTML to PDF

    Click the + to the right of the first module, search for PDF Munk and pick Convert HTML to PDF. Choose your connection, then map the HTML coming out of the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles, the items passed from module to module, so you can see what PDF Munk received and returned.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks it, every 15 minutes by default, then switch the scenario on. It now runs without you.

Modules

The 5 PDF Munk modules, one by one

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

PDF Munk1

Capture Website Screenshot

ActionIn the docs only

Going by its name, you hand it a web address and get back a picture of that page for the next module. It saves you from opening a browser and taking the capture yourself.

When to use it
a new link lands in a spreadsheet or a form and your team wants a visual preview filed next to it.
Watch out
pick the PDF version below if the capture has to be printed or signed.
PDF Munk2

Capture a Website Screenshot into PDF

ActionIn the docs only

This one also starts from a web address, but the output is a PDF of the page rather than a picture. That makes it the natural choice for archiving how a page looked on a given day.

When to use it
a legal or marketing contact needs proof of a published offer, attached to a record in your CRM.
Watch out
each capture costs one operation, the unit Make counts on your plan, so filter the addresses first.
PDF Munk3

Convert HTML to PDF

ActionIn the docs only

Feed it HTML produced by another app and it returns a PDF document, the same layout turned into a file you can send or store.

When to use it
an order or a signed quote arrives as an HTML template and the customer expects a PDF by email.
Watch out
test with Run once and open the result, since what PDF Munk renders depends on the HTML you map.
PDF Munk4

Convert HTML to an Image

ActionIn the docs only

Here the HTML becomes a picture instead of a document. Useful when a design built in HTML, like a badge or a card, has to travel where only images are accepted.

When to use it
a new event registration should produce a personal visual that you post in a chat channel or attach to a message.
Watch out
choose Convert HTML to PDF whenever the result has to be printed or sent as a document.
PDF Munk5

Make an API Call

ActionIn the docs only

This module lets you call any endpoint of the PDF Munk API while reusing the connection you already created. It covers whatever the four ready-made modules do not offer.

When to use it
the PDF Munk documentation describes an option that none of the other modules shows in Make.
Watch out
you write the request yourself, so keep the PDF Munk API documentation open and test every call with Run once before switching on.
Need help

Need help automating PDF Munk with Make?

A person reads every message.

FAQ

PDF Munk and Make: frequent questions

01Is the PDF Munk Make integration free?
Yes on the Make side: PDF Munk is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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. On the PDF Munk side, you need an active account with an API key; its own pricing page tells you what the subscription includes.
02What do you need to connect PDF Munk to Make?
Two things: an active PDF Munk account and its API key. You find the key in the PDF Munk dashboard, through the top-left menu, on the account page. In Make, add a PDF Munk module, click Create a connection, name it if you want, and paste the key. That connection is then shared by the five PDF Munk modules, so you only do this once per account, even if you build several scenarios around it later.
03Does PDF Munk trigger a Make scenario in real time?
No, because PDF Munk has no trigger in Make. The scenario has to start elsewhere. Either another app starts it: an instant trigger fires as soon as that app calls Make through a webhook, while a scheduled trigger is checked by Make at regular intervals. Or you start it with the schedule of the scenario, every 15 minutes by default. PDF Munk then runs as an action in the middle of the flow, on the address or HTML it receives from the previous module.
04What if a PDF Munk module is missing in Make?
Use Make an API Call. It calls any endpoint of the PDF Munk API with the same connection, so an option that the four ready-made modules do not show can still be reached from your scenario. Read the PDF Munk API documentation to build the request, and test it with Run once. Keep in mind that Make labels the PDF Munk documentation as AI-generated content that may contain mistakes, so confirm important details with PDF Munk directly.
05Should you use Make or n8n for PDF Munk?
It depends on the tool your team already uses. The same app may also have an n8n node, so the choice rarely comes down to PDF Munk alone. In Make you get five modules, including Make an API Call for the rest of the API, and one connection shared by all of them. If your other automations already run in n8n, stay there; if you are starting out, build the scenario in Make and compare using the criteria that matter to your team.
Same platform

Other docs you might need on this stack.

Browse all integrations