Resources · Make integration

PDF Export by PDFCrowd Make integrationAutomate PDF Export by PDFCrowd with Make.

Need a PDF every time a piece of HTML is ready? The PDF Export by PDFCrowd Make integration gives you 2 action modules, one to convert HTML to PDF and one to call the API directly. This guide shows how to link your account and build a first working scenario.

Try the PDF Export by PDFCrowd integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PDF Export by PDFCrowd Make integration do for you?

It lets Make hand HTML to PDFCrowd and get a PDF back, inside a scenario, which is the automation you build in Make as a chain of modules. A module is one brick of that chain. This app has no trigger, so the scenario starts from another app or from a schedule, then the PDF step follows.

A quote that exists as a file, not just as data. A form or a CRM produces the details, a Make tool assembles them into HTML, and Convert HTML to PDF turns that page into a document you can send or archive.

A report someone can open without logging in. Rows from a spreadsheet become an HTML summary, and the same module renders it as a PDF that the next module drops into a shared folder or attaches to an email.

A PDFCrowd feature the listed module does not expose. Make an API Call reaches any endpoint of the PDFCrowd API with the connection you already set up, so nothing forces you to leave the scenario.

Know the limits before you start. Make's own documentation for this app is thin: it says there is not enough public information to describe it fully, so test each setting with Run once instead of assuming. Each conversion counts as one operation, meaning one execution of one module on your plan; the Make pricing guide explains how that adds up. If you also look at n8n, the n8n vs Make comparison lays out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect PDF Export by PDFCrowd to Make?

  1. 01

    Open the connection window

    Add the Convert HTML to PDF module to your scenario and click Create a connection. A connection is your PDFCrowd account linked to Make once, then reused by both modules of the app.

  2. 02

    Name it so you recognize it

    Giving the connection a name is optional, but it pays off the day you run two PDFCrowd accounts, say one for testing and one for clients. Pick a label that tells them apart at a glance.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the PDFCrowd page, or paste the key PDFCrowd gives you. Then click Save and the module shows the connection as selected.

First scenario

Build your first scenario with PDF Export by PDFCrowd

GoalWhen another app sends new data, Make builds the HTML and PDF Export by PDFCrowd returns it as a PDF.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since PDFCrowd has no trigger, the first module comes from the app that holds your data, a form tool or a CRM for instance.

  2. 02

    Add the PDF step

    Click the + on the right of that first module, search for PDF Export by PDFCrowd and pick Convert HTML to PDF. Link your account with Create a connection if it is not done yet.

  3. 03

    Map the HTML

    Fill the module with the HTML to convert, mapping values from the previous module. A bundle, one item passed from module to module, carries those values, such as a client name or an amount.

  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 actually came back before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default, or reacts at once if that app has an instant trigger) and switch the scenario on.

Modules

What each PDF Export by PDFCrowd module does

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

PDF Export by PDFCrowd1

Convert HTML to PDF

ActionIn the docs only

Hand this module a piece of HTML and it gives you back a PDF you can pass to the rest of the scenario, to store, email or attach.

When to use it
a quote, a receipt or a summary already exists as HTML and has to leave the scenario as a proper document.
Watch out
each conversion is one operation, and on the Free plan Make handles files up to 5 MB, so a heavy document can hit that ceiling.
PDF Export by PDFCrowd2

Make an API Call

ActionIn the docs only

Reach any endpoint of the PDFCrowd API from your scenario, reusing the connection you created for the conversion module. Nothing new to authorize.

When to use it
you need a PDFCrowd option that Convert HTML to PDF does not offer, and you know which endpoint provides it in the PDFCrowd API documentation.
Watch out
you write the request yourself here, so read the response in Run once before you connect anything downstream.
Need help

Need help automating PDF Export by PDFCrowd with Make?

A person reads every message.

FAQ

PDF Export by PDFCrowd and Make: common questions

01Is the PDF Export by PDFCrowd Make integration free?
Yes, on the Make side: PDF Export by PDFCrowd is a standard app, available from the Free plan. 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 drop the interval to 1 minute and raise execution to 40 minutes. Make counts usage in operations, so every conversion uses part of your monthly allowance. Your PDFCrowd account is a separate matter, handled on PDFCrowd's side.
02What do you need to connect PDF Export by PDFCrowd to Make?
A PDFCrowd account and a Make account. Make's documentation lists no other prerequisite for this app. You add a module, click Create a connection, optionally name it, then either approve Make on the PDFCrowd page or paste the key PDFCrowd provides, and save. That single connection then serves both modules, Convert HTML to PDF and Make an API Call, so there is only one setup to do, and nothing to repeat later.
03Does PDF Export by PDFCrowd trigger a scenario in real time?
No, because the app has no trigger at all. It only acts once something else has started the scenario. Two ways to start one: put the trigger of another app first, the app where your data lives, or rely on Make's scheduling on that first module, which runs every 15 minutes by default. If the first app offers an instant trigger, which fires through a webhook as soon as something happens, the PDF is produced right after the event.
04What if a PDF Export by PDFCrowd module is missing in Make?
Use Make an API Call. It reaches any endpoint of the PDFCrowd API with the connection you already have, which covers what Convert HTML to PDF leaves out. Keep in mind that Make's documentation for this app is limited, since there is not enough public information about it, so check the endpoint in PDFCrowd's own API documentation and test the call with Run once before relying on it in a live scenario.
05Should you use Make or n8n for PDF Export by PDFCrowd?
It depends on your criteria rather than on the app. In Make, you get 2 modules: a ready conversion step and an API call for everything else, both on one connection, usable from the Free plan. The same app often has an n8n node too, so check that side before deciding. The comparison page linked earlier in this guide sets out, point by point, the criteria that separate the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations