Resources · Make integration

iLovePDF Make integrationAutomate iLovePDF with Make.

Tired of opening iLovePDF by hand for every file? The iLovePDF Make integration gives you 16 actions to compress, convert, merge, stamp and lock PDFs inside an automation. This page shows you how to link your account and build a first working flow.

Try the iLovePDF integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the iLovePDF Make integration do for you?

The iLovePDF Make integration lets a Make scenario (the automation you build, a chain of modules) hand your files to iLovePDF and get the processed PDF back. Each module is one brick of that chain: here, 16 actions such as Compress a PDF, Merge a PDF or Protect a PDF, all driven by one connection to your iLovePDF developer project.

Proposals that leave clean. A sales team drops a Word proposal into shared storage. Office to PDF turns it into a PDF, Watermark stamps a draft mention, and Protect a PDF adds a password before anything leaves the building.

Searchable archives. An accounting office scans paper invoices. OCR PDF makes the text selectable, Extract PDF Text pulls it out for a spreadsheet, and PDF to PDF/A produces the copy meant for long-term storage.

Tidy client packs. A property manager needs one file per tenant. Merge a PDF joins the lease and its appendices, Add Page Numbers numbers the result, and Compress a PDF keeps it light enough to email.

What the integration does not do: iLovePDF has no trigger in Make, so it never starts a scenario on its own. Another app, or the schedule you set on the first module, has to kick things off. On the Free plan, Make also caps files at 5 MB. The same app may have an n8n node too; our n8n vs Make comparison helps you pick a tool, and the Make pricing guide explains how plans count usage. Stuck on a failing run? Open Make troubleshooting.

Connect

How do you connect iLovePDF to Make?

  1. 01

    Get your developer keys

    Register as an iLovePDF developer, then log in and open your administration console. Go to the section that lists your projects, select the project you want, and copy the API key and the Client secret shown on screen.

  2. 02

    Add an iLovePDF module

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

  3. 03

    Paste the credentials

    Give the connection a label in Connection name if you like (it is optional), then paste the credentials you copied from iLovePDF, or follow the on-screen instructions. Save, and Make can now call iLovePDF for you.

First scenario

Your first scenario: turn a Word file into a protected PDF

GoalWhen a Word document reaches your file storage app, Make turns it into a PDF with iLovePDF and locks it with a password.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since iLovePDF has no trigger, the first module comes from the app where your Word files live.

  2. 02

    Add Office to PDF

    Click the + on the right of that first module, search iLovePDF, pick Office to PDF and select your connection. Map the file from the previous module so each document is converted.

  3. 03

    Chain Protect a PDF

    Add Protect a PDF after it and map the PDF that Office to PDF returned. Set the password in the module fields, then share it with recipients through another channel than the file.

  4. 04

    Test with Run once

    Click Run once with one test document in place. Open each module's bubble to read the bundles it received: a bundle is one item passed along, here one file.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, never below that on the Free plan) and switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

Every iLovePDF module in Make, explained

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

iLovePDF1

Add Page Numbers

Action

In Make“Add's page numbers into PDF's with ease.”

Your PDF comes back with numbered pages, so a reader can point to page 7 of a report instead of counting sheets by hand.

When to use it
right after Merge a PDF has joined several documents into a single dossier that people will discuss in a meeting.
Watch out
number the pages after the merge, not before, otherwise each part keeps its own separate count.
iLovePDF2

Compress a PDF

Action

In Make“Reduces file size while optimizing for maximal PDF quality.”

A lighter copy of the same PDF is what you get here, with iLovePDF keeping the quality as high as it can while shrinking the file.

When to use it
before emailing a heavy scan or storing it in a folder where space is tight.
Watch out
on the Make Free plan files are capped at 5 MB, so a very large PDF may need a paid plan before it even reaches this module.
iLovePDF3

HTML to PDF

Action

In Make“Convert webpages in HTML to PDF. Copy and paste the URL of the page you want and convert it to PDF with a click.”

Hand it the URL of a web page and a PDF snapshot of that page comes back, ready to file or attach.

When to use it
to keep a dated copy of your published terms of sale on the day a customer signs, or to archive a public notice.
Watch out
the module starts from the page address, so check that the link opens in a normal browser before mapping it in.
iLovePDF4

Image to PDF

Action

In Make“Converts JPG, PNG and TIFF images to PDF in second. Easily adjust orientation and margins.”

Photos and scans become a proper PDF: JPG, PNG and TIFF images go in, and you can adjust orientation and margins on the way.

When to use it
field staff snap receipts or delivery slips with their phone, and accounting wants PDFs only.
Watch out
the directory names those three formats; if your files use another one, test a sample with Run once before relying on it.
iLovePDF5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the 15 other modules leave out stays reachable: this module calls any endpoint of the iLovePDF API, using the same connection.

When to use it
an iLovePDF tool you rely on has no dedicated module in Make, and you still want it inside the scenario.
Watch out
you build the request yourself, so keep the iLovePDF API documentation open next to the editor while you set it up.
iLovePDF6

Merge a PDF

Action

In Make“Merges multiple PDF files into one PDF.”

Several PDF files leave this module as one single PDF, so a pile of attachments becomes one file.

When to use it
a quote, the signed terms and the first invoice should reach a client as one attachment rather than three.
Watch out
Make passes each file as its own bundle, so click Run once and check that the module really receives every file you expect in the same run.
iLovePDF7

OCR PDF

Action

In Make“Easily convert scanned PDF into searchable and selectable documents.”

Scanned pages turn into a document you can search and select text in, instead of a flat picture of paper.

When to use it
paper contracts or delivery notes get scanned, and someone later needs to find a name or a reference inside them.
Watch out
place it before Extract PDF Text in the chain, since a raw scan holds images rather than characters to pull out.
iLovePDF8

Office to PDF

Action

In Make“Makes DOC and DOCX files easy to read by converting them to PDF.”

Word documents come out as PDFs that anyone can open and read the same way, whatever software they use.

When to use it
a proposal or a contract is drafted in Word and must go out in a format the client cannot edit by mistake.
Watch out
despite the Office name, the directory only mentions DOC and DOCX files, so test other formats with Run once first.
iLovePDF9

PDF to JPG

Action

In Make“Converts each PDF page into a JPG or extract all images contained in a PDF.”

Images come out of your PDF in one of two ways: each page saved as a JPG, or every picture already inside the file extracted on its own.

When to use it
you need page previews for a web page, or the product photos buried in a supplier catalog.
Watch out
pick the right mode before running, because the two give very different results from the same document.
iLovePDF10

PDF to PDF/A

Action

In Make“Transforms your PDF to PDF/A, the ISO-standardized version of PDF for long-term archiving.”

This one hands you a PDF/A copy, the ISO-standardized version of PDF designed for keeping documents readable over the long term.

When to use it
signed contracts, board minutes or HR records that must stay readable in your archive.
Watch out
convert the final version only; PDF/A is the copy you store, not the draft people keep editing.
iLovePDF11

Protect a PDF

Action

In Make“Protects PDF file with a password.”

Only people who know the password can open the file once this module has locked it.

When to use it
payslips, medical forms or pricing grids travel by email and should not be readable if forwarded to the wrong inbox.
Watch out
run it last, after any watermark or merge, and send the password through a channel other than the email carrying the PDF.
iLovePDF12

Split a PDF

Action

In Make“Splits given pages or page ranges into multiple PDF files.”

One long PDF becomes several smaller ones, cut along the pages or page ranges you choose.

When to use it
a scanner produced a single file holding a whole stack of invoices, and each one belongs in its own client folder.
Watch out
Run once shows how many bundles come out, and every module placed after it uses one operation per bundle.
iLovePDF13

Watermark

Action

In Make“Stamps an image or text over your PDF in seconds.”

Text or an image gets stamped over your PDF, so every page carries a visible mark such as your logo or a status.

When to use it
a proposal goes out marked as a draft, or documents shared with partners must show where they came from.
Watch out
place it before Protect a PDF, so the locked copy already carries the stamp when it leaves.
iLovePDF14

Create Signature Request

ActionIn the docs only

As its name says, this module starts an iLovePDF signature request straight from your scenario, so a document can move toward signing without a manual upload.

When to use it
a contract has just been converted by Office to PDF and is ready for the client to sign.
Watch out
Make publishes no official description for it, so open the module and read its fields before building a flow around it.
iLovePDF15

Extract PDF Text

ActionIn the docs only

Judging by its name, the words inside a PDF come out as plain text that the next modules can read, sort or store.

When to use it
you want the content of incoming documents in a spreadsheet row or passed to another tool for review.
Watch out
no official description exists for this module; if the text comes back empty on a scan, add OCR PDF in front of it and test again.
iLovePDF16

Unlock PDF

ActionIn the docs only

Going by its name, this module gives you back a PDF without its lock, so the rest of the scenario can work on the content.

When to use it
a supplier sends protected files that you then need to merge, compress or number.
Watch out
Make lists it without any official description, so check which fields it asks for and test with Run once on a sample file.
Need help

Need help automating iLovePDF with Make?

A person reads every message.

FAQ

iLovePDF and Make: common questions

01Is the iLovePDF Make integration free?
Yes, on the Make side. iLovePDF is a standard app, available from the Free plan, which 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 (Core, Pro, Teams and Enterprise) lift those limits and count usage in operations per month. On the iLovePDF side, the doc points you to the iLovePDF pricing page for subscriptions, so check it there.
02What do you need to connect iLovePDF to Make?
You need an iLovePDF account registered as a developer, because Make asks for a project's credentials. In the iLovePDF administration console, open your projects, select one and copy its API key and Client secret. Then add any iLovePDF module in a Make scenario, click Create a connection, name it if you wish and paste those two values. Every iLovePDF module then reuses this one connection, so you set it up a single time.
03Does the iLovePDF Make integration react in real time?
No, because iLovePDF has no trigger in Make: its 16 modules are all actions. A scenario therefore starts elsewhere. Either another app's trigger fires it (instantly if that trigger is an instant one, called by a webhook) or you set a schedule on the first module, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. Either way, the iLovePDF modules run right after the module that starts the flow.
04What if an iLovePDF module is missing in Make?
Use Make an API Call. It calls any endpoint of the iLovePDF API with the connection you already set up, which covers tools the 15 dedicated modules do not. You write the request yourself, so keep the iLovePDF API documentation at hand. If the file size is what blocks you, remember that the Make Free plan caps files at 5 MB, while paid plans raise execution time to 40 minutes.
05Should you use Make or n8n for iLovePDF?
It depends on the tool your team already runs. In Make, iLovePDF offers 16 ready modules, including Make an API Call for the rest, and works from the Free plan. Many apps also exist as an n8n node, so check whether iLovePDF has one and what it covers before choosing. Compare the modules you actually need on both sides; that list, not a general ranking, should decide for your team.
Same platform

Other docs you might need on this stack.

Browse all integrations