139 modules, one app
Convert, merge, split, OCR, e-sign, watermark, compress, barcode and generate documents from a single app. 139 modules across 17 categories cover most document work without stitching several services together.
PDF automation in Make: 139 PDF4me modules.
Add PDF4me modules to any Make scenario to convert, merge, OCR, e-sign, stamp and generate documents. One connection, one API key, no code.
- No credit card required
- Works with your existing plan
- Set up in minutes
How it works
Set up PDF4me in Make.
01
Get your PDF4me API key
Make connects to PDF4me with an API key, so get yours ready first. Sign in to the PDF4me dashboard, open API Calls & Key, and copy the complete key without extra spaces. No account yet? Create one free to generate your first key.
Get your free API key
02
Create a Make account and start a scenario
If you do not already use Make, sign up for a free account. Log in, open your dashboard, and click Create a new scenario. That gives you a blank canvas where you add PDF4me alongside the other apps you automate.
Create a free Make account
03
Add the PDF4me module
On the scenario canvas, click the plus icon to add a module, search for PDF4me, and select the app. Then pick the action you want to run, from convert and merge to barcodes, editing and extraction.
See PDF4me on Make
04
Add your PDF4me connection
After you choose an action, Make asks you to set up a connection. In the pop-up, click Add to create a new PDF4me connection. The same connection is reused across every PDF4me module in your scenario.
Browse all 139 modules
05
Enter your API key to authenticate
In the Create a connection window, paste your PDF4me key and save. Make stores it securely so you can reuse the same connection everywhere, and your PDF4me modules are ready to run.
Read the full walkthroughEverything it does
Every action, grouped by what it does.
The full module catalogue, grouped by domain. Every module opens its own Make documentation.
139 of 139
AI document parsing13
Convert12
Edit PDF8
Extract7
Word18
Barcode & QR6
PDF operations11
Document generation8
Merge & split9
Excel19
Image15
More & utilities13
Why teams pick it
Why teams run PDF4me in Make.
One API key, one connection
Connect PDF4me once with your API key and reuse it in every scenario. No per-module setup and no OAuth juggling.
Runs after any trigger
PDF4me is an action app, so it slots into scenarios started by SharePoint, Google Drive, Dropbox, webhooks, email or a schedule. It fits the automations you already run.
No code required
Build document steps by dropping modules and mapping fields. Your team ships PDF automation without writing or hosting anything.
AI document parsing
Pull structured data from invoices, receipts, bank statements, contracts, payslips and tax forms, then feed the fields straight into the next module in your scenario.
Barcodes and e-invoicing built in
Generate Code128 and QR codes, Swiss QR bills, EPC and SEPA payment QR, and ZUGFeRD e-invoices inside a scenario. Handle these formats without adding a separate tool.
Ready-made templates
Start from a prebuilt automation
Clone a template and swap in your files, no build from scratch.
Convert HTML to PDF in Make
Turn an HTML template or a live URL into a polished PDF inside a scenario, then save it wherever your flow ends.
Parse invoices with AI in Make
Read line items and totals from incoming invoices with the AI parser, then map the fields straight into your next module.
Merge PDFs from a folder in Make
Watch a folder for new files and merge them into one PDF automatically, with no manual combining.
Split a scan by barcode in Make
Split one scanned batch into separate PDFs by barcode, then route each file to the right destination.
FAQ
Answers before you install.
Is PDF4me a trigger or an action in Make?
PDF4me is an action app. Its modules run inside a scenario that another app starts, so you pair them with a trigger such as a new file in SharePoint, Google Drive or Dropbox, an incoming webhook, an email, or a schedule. See the PDF4me app on Make.
Do I need a paid Make plan or a premium purchase?
You buy nothing extra from PDF4me beyond your usage. You connect it with a PDF4me API key, and each module run consumes one operation on whatever Make plan you already have.
How is PDF4me billed?
PDF4me is billed by API usage, separate from Make. You start free with no credit card and pay only as your volume grows, while Make counts its own operations per run on your existing plan.
How do I get an API key?
Create a free PDF4me account, open the dashboard and copy your key from API Keys, then paste it once when you add the PDF4me connection in Make. The getting-started guide walks through it.
Which apps and triggers can start a PDF4me scenario?
Any trigger in Make. Common ones are a new or updated file in SharePoint, Google Drive, OneDrive or Dropbox, an incoming webhook, a new email, a form submission, or a scheduled run. PDF4me modules run after the trigger fires.
Is there a free tier or usage limits?
Yes. You can start free with no credit card and test the modules before you commit. Higher volume moves you onto a paid tier, metered by PDF4me for API usage and by Make for operations per run.
Get your documents done.
Build it into your product with the API, automate it with no code, or use the free tools in your browser. No credit card to begin.
Start with a single call
curl -X POST https://api.pdf4me.com/v2/ConvertToPdfFree tier · No credit card required