Resources · Make integration

ComPDFKit PDF Editor Make integrationAutomate ComPDFKit PDF Editor with Make.

Tired of opening every PDF by hand to compress, merge or stamp it? The ComPDFKit PDF Editor Make integration gives you 15 action modules for PDF work. This page shows how to link your API key, build a first scenario and pick the right module.

Try the ComPDFKit PDF Editor integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ComPDFKit PDF Editor Make integration do for you?

The ComPDFKit PDF Editor Make integration lets a Make scenario (the automation you build, a chain of modules) send PDFs to ComPDFKit and have them processed: compressed, merged, split, rotated, watermarked or compared. A module is one brick of that chain. You connect your ComPDFKit developer account once, then drop the modules where you need them.

Lighter files for email. A sales team that sends quotes as heavy PDFs can route each file through Compress - Create a Task before it leaves, so the attachment stays small.

One contract pack instead of five attachments. A legal assistant collecting signed pages can join them with Merge PDF Files - Create a Task, then stamp the result using Add a Watermark - Create a Task.

Spotting what changed between two versions. When a supplier returns an edited agreement, Content Comparison - Create a Task or Overlay Comparison - Create a Task puts the two files side by side for review.

What Make does not do here: the app has no trigger, so ComPDFKit never starts a scenario by itself. Your flow begins in another app or on a schedule. The official Make documentation for this app is AI-generated and flagged as possibly containing mistakes, so test each module with a real file. For anything the listed modules skip, Make an API Call reaches the rest of the ComPDFKit API with the same connection.

The same app often has an n8n node too; the n8n vs Make comparison helps you choose. New to the tool? Our Make review and Make training cover the basics.

Connect

How do you connect ComPDFKit PDF Editor to Make?

  1. 01

    Get your API key and client secret

    You need a ComPDFKit developer account with a project ID and its API key. In your ComPDFKit dashboard, open the API Keys section, then copy the API key and the Client secret shown on screen.

  2. 02

    Open a ComPDFKit module in Make

    In your scenario, add any ComPDFKit PDF Editor module and click Create a connection. A connection is your ComPDFKit account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste your credentials and save

    Paste the API key and client secret you copied, or follow the on-screen instructions, then save. From now on, each ComPDFKit module in any scenario can pick this connection from the list instead of asking again.

First scenario

Your first scenario with ComPDFKit PDF Editor

GoalWhen a PDF lands in another app, Make sends it to ComPDFKit PDF Editor and creates a compression task on it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Start with the app where your PDFs arrive, since ComPDFKit has no trigger of its own.

  2. 02

    Add Upload a File

    Click the + to the right of that first module, search for ComPDFKit PDF Editor and pick Upload a File. Choose your connection, then map the PDF coming from the previous module.

  3. 03

    Add Compress - Create a Task

    Add the next module with the + again and pick Compress - Create a Task. Fill its fields, mapping what the previous modules returned. Each file travels as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open each module's bubble to read the bundles it received and check that ComPDFKit accepted the file. No processed file yet? The name Start a Task suggests it launches the task, so try adding it.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What each ComPDFKit PDF Editor module does

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

ComPDFKit PDF Editor1

Add a Watermark - Create a Task

ActionIn the docs only

Puts a watermark on your PDF so everyone who opens it sees it is a draft, a confidential copy or a company document. It saves you from stamping files one by one in an editor.

When to use it
right before a proposal or report leaves your team for a client.
Watch out
the Make doc for this app is AI-generated, so run a test file first and check where the mark lands.
ComPDFKit PDF Editor2

Compress - Create a Task

ActionIn the docs only

Shrinks a PDF so it travels easily by email or fits upload limits in other tools. Pick it over the other modules when the content stays the same and only the weight is the problem.

When to use it
scanned invoices or photo-heavy brochures that bounce back from inboxes.
Watch out
on the Make Free plan, files handled in a scenario are capped at 5 MB, so very large scans may need a paid plan.
ComPDFKit PDF Editor3

Content Comparison - Create a Task

ActionIn the docs only

Compares the content of two PDFs so you can see what was changed between two versions of the same document. It turns a slow line-by-line reread into a single step inside your scenario.

When to use it
a partner sends back a contract and you need to know what they edited.
Watch out
if you want a visual stack of both pages instead, Overlay Comparison is the better fit.
ComPDFKit PDF Editor4

Delete PDF Pages - Create a Task

ActionIn the docs only

Removes pages you do not want to keep, like a blank back page or an internal cover sheet, before the PDF goes anywhere else. The rest of the document stays untouched.

When to use it
exports from a tool that always adds a page nobody needs.
Watch out
keep the original file somewhere safe, since the removed pages cannot be brought back from the trimmed copy.
ComPDFKit PDF Editor5

Extract PDF Pages - Create a Task

ActionIn the docs only

Pulls a selection of pages out of a PDF into a new file, so you only share the part that matters. Where Delete PDF Pages trims, this module keeps just what you pick.

When to use it
sending the signature page of a long agreement to accounting.
Watch out
test with Run once to confirm the page selection matches what you expect before switching the scenario on.
ComPDFKit PDF Editor6

Get the File Information

ActionIn the docs only

Reads back information about a file handled by ComPDFKit, which gives the next modules something concrete to work with. Think of it as a check step rather than an edit.

When to use it
after a task, when you want to know where the result stands before emailing it or saving it.
Watch out
the documentation lists no fields for it, so open the bundle after Run once to see what it really returns.
ComPDFKit PDF Editor7

Insert PDF Pages - Create a Task

ActionIn the docs only

Adds pages into an existing PDF, for example terms and conditions slipped in after a quote. You get one complete file without rebuilding it from scratch.

When to use it
every outgoing proposal needs the same appendix at a set place.
Watch out
if you simply want to glue whole files end to end, Merge PDF Files does that job with fewer settings to think about.
ComPDFKit PDF Editor8

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the ComPDFKit API from your scenario, reusing the connection you already set up. It is your way out when none of the listed modules covers what you need.

When to use it
a PDF feature exists in ComPDFKit but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the ComPDFKit API reference open while you fill it in.
ComPDFKit PDF Editor9

Merge PDF Files - Create a Task

ActionIn the docs only

Joins several PDFs into one, so a client receives a single file instead of a pile of attachments. It is the module for assembling a pack from separate parts.

When to use it
a quote, a spec sheet and signed terms that must travel together.
Watch out
every module run counts as an operation on your Make plan, so group the files before this step rather than merging them two at a time.
ComPDFKit PDF Editor10

Overlay Comparison - Create a Task

ActionIn the docs only

Lays two versions of a PDF on top of each other, so shifts in layout, drawings or signatures jump out at a glance. It suits documents where the look matters as much as the words.

When to use it
checking a revised floor plan or a redesigned form against the previous one.
Watch out
for pure text edits, Content Comparison usually gives a clearer answer.
ComPDFKit PDF Editor11

Remove Watermark - Create a Task

ActionIn the docs only

Takes a watermark off a PDF, so a document that was marked as a draft can go out clean once it is approved. It is the reverse of Add a Watermark.

When to use it
a manager signs off a report and the final copy needs to lose its draft stamp.
Watch out
use it only on files your team is allowed to change, and test on a copy with Run once first.
ComPDFKit PDF Editor12

Rotate PDF Pages - Create a Task

ActionIn the docs only

Turns pages that came out sideways or upside down, so the PDF reads properly on any screen. Nobody has to open the file and fix it by hand.

When to use it
scans from a phone or a shared copier where some pages end up in landscape.
Watch out
check one output with Run once, because a wrong setting would turn the good pages as well.
ComPDFKit PDF Editor13

Split PDF Files - Create a Task

ActionIn the docs only

Cuts one large PDF into several smaller files, so each part can be filed or sent to the right person. It is the opposite move to Merge PDF Files.

When to use it
a batch scan holds several invoices that each belong in their own folder.
Watch out
the result may come as several bundles, and each one you process further costs operations.
ComPDFKit PDF Editor14

Start a Task

ActionIn the docs only

Starts a task in ComPDFKit PDF Editor, which is the step that sets the processing in motion. Its name pairs it with the modules ending in Create a Task.

When to use it
when a Run once shows your task was created but no processed file came back yet.
Watch out
the documentation gives no exact order between creating, uploading and starting, so confirm it on a test run.
ComPDFKit PDF Editor15

Upload a File

ActionIn the docs only

Sends a PDF from your scenario to ComPDFKit PDF Editor, so the other modules have a file to work on. It is often the first ComPDFKit module in a flow that starts in another app.

When to use it
a document arrives by email or in cloud storage and needs processing.
Watch out
on the Free plan, files over 5 MB exceed the Make limit, and the transfer quota is 512 MB.
Need help

Need help automating ComPDFKit PDF Editor with Make?

A person reads every message.

FAQ

Questions about the ComPDFKit PDF Editor Make integration

01Is the ComPDFKit PDF Editor Make integration free?
On the Make side, yes: ComPDFKit PDF Editor is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval 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 lower the interval to 1 minute and remove the cap on active scenarios. ComPDFKit itself asks you to register as a developer, and its own pricing page covers the subscription.
02What do you need to connect ComPDFKit PDF Editor to Make?
You need a ComPDFKit developer account with a project ID and its API key. In the API Keys section of the ComPDFKit dashboard, copy the API key and the client secret. Then add any ComPDFKit module to a scenario in Make, click Create a connection, optionally name it, and paste both values. That single connection is reused by all 15 modules of the app. If Make rejects the values, check that both come from the same ComPDFKit project.
03Does ComPDFKit PDF Editor trigger Make scenarios in real time?
No. The app has no trigger module at all, scheduled or instant, so ComPDFKit never starts a scenario by itself. You begin the flow somewhere else: with a trigger from the app where your PDFs arrive, or with a schedule set on the first module, every 15 minutes by default. The ComPDFKit modules then act on each file as it passes through the scenario. Remember that each module run on each file counts as one operation on your Make plan.
04What if a ComPDFKit PDF Editor module is missing in Make?
Use Make an API Call. It reaches any endpoint of the ComPDFKit API from your scenario with the connection you already have, so a feature without a dedicated module is still within reach. Keep in mind that the Make documentation for this app is AI-generated and may contain mistakes; test every module with a real file and contact ComPDFKit directly for questions about their own documentation. That way you keep one scenario instead of stitching several tools together.
05Should you use Make or n8n for ComPDFKit PDF Editor?
It depends on the tool your team already runs. In Make, the app offers 15 ready-made action modules plus Make an API Call, with no trigger, so the flow starts in another app. The same app often has an n8n node as well. Compare which PDF operations each side covers for your case, then pick the platform where the rest of your automations already live. The n8n vs Make comparison linked higher on this page lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations