Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

PDF4me Make Integration

What this integration does

PDF4me for Make delivers 80+ document operations — PDF conversion, merging, splitting, watermarking, OCR, Excel manipulation, and Word processing — inside Make's visual scenario builder. Connect PDF4me to Dropbox, Google Drive, Gmail, Slack, Airtable, Salesforce, and 1000+ other Make apps without writing a single line of code.

Get your API KeyOpen Make
PDF4me Make scenario example showing modules connected in a visual workflow

Important Facts You Should Not Miss​

One connection, all modules

Create a PDF4me connection once using your API key and reuse it across every PDF4me module in your Make account — no re-authentication required when you build new scenarios.

Chain modules — no intermediate uploads

The Document Data output of any PDF4me module maps directly into the File input of the next. Convert, compress, watermark, and sign in a single scenario run — no file storage step between each action.

Works with any Make file source

Supply documents from Dropbox, Google Drive, OneDrive, Gmail, Outlook, Box, a public URL via HTTP module, or any Make trigger that outputs a binary file — PDF4me accepts them all.

Authentication​

To use PDF4me in Make, authenticate using an API key. You can register at either dev.pdf4me.com (Developer Portal, recommended) or pdf4me.com (Consumer Portal).

Developer Portal — dev.pdf4me.com (Recommended)​

The developer portal is best for automation workflows: monthly subscription plans, automatic credit renewal, a usage dashboard, and free trial credits to get started immediately.

Get your key:

  1. Register at dev.pdf4me.com
  2. Navigate to Dashboard → API Keys
  3. Copy your API key
PDF4me developer portal showing the API Keys section with a key ready to copy
Get Developer API Key

Consumer Portal — pdf4me.com​

The consumer portal uses a one-time purchase model. After purchasing a plan, find your API key under Account Settings.

PDF4me consumer portal showing the API key location in Account Settings

Setting Up PDF4me in Make​

Step 1 — Register and get your API key​

Go to dev.pdf4me.com, create a free account, and copy your API key from Dashboard → API Keys. Free trial credits are included — no credit card required.

Step 2 — Open Make and create a scenario​

Log in to make.com, navigate to Scenarios, and click Create a new scenario to open the visual builder.

Step 3 — Add a PDF4me module​

Click + to add a module, search for PDF4me, and select the action you need — for example Convert to PDF, Merge Multiple PDFs, Add Text Watermark, Generate Document Single, or any of the 80+ modules listed below.

Step 4 — Create the connection​

When prompted, click Add in the Connection dialog and paste your PDF4me API key. Save the connection — it is reusable across all PDF4me modules in your account.

Make PDF4me connection dialog showing the API key field

Step 5 — Configure, save, and run​

Map the File input from a prior module (Dropbox download, Google Drive download, email attachment), set any required parameters, click Save, and run the scenario once to verify the output.

Scenario Architecture​

A typical PDF4me Make scenario follows this pattern:

Typical Scenario FlowStandard pattern for a PDF4me Make automation — trigger, file retrieval, processing, and output.
File upload → Convert → Store
  1. Dropbox watch folder detects a new Word file upload.
  2. Dropbox – Download a File retrieves the binary content.
  3. PDF4me – Convert to PDF converts it to PDF format.
  4. PDF4me – Compress PDF reduces the file size.
  5. Dropbox – Upload a File saves the final PDF to the output folder.
Schedule → Generate → Email
  1. A scheduled trigger fires on the first day of each month.
  2. Google Sheets fetches the latest report data.
  3. PDF4me – Generate Document Single merges data into a Word template and converts to PDF.
  4. PDF4me – Add Text Watermark stamps "Confidential" on every page.
  5. Gmail sends the watermarked PDF to the distribution list.
Email attachment → OCR → Database
  1. Gmail watch trigger fires when a new email with a PDF attachment arrives.
  2. Gmail – Get Attachment retrieves the PDF binary.
  3. PDF4me – PDF OCR extracts all text from the scanned PDF.
  4. Extract Text by Expression pulls key fields (invoice number, date, total) using regex patterns.
  5. Airtable – Create a Record saves the extracted data to the invoices base.

Available Module Categories​

PDF Operations
Excel Automation
Word Processing
Document Generation
Image Processing
Barcode & Hyperlinks

Frequently Asked Questions​

Do I need separate accounts for Make and PDF4me?+
Yes. Make is the visual workflow platform and PDF4me is the document processing service — both require their own accounts. Make offers a free plan with limited monthly operations; PDF4me provides free trial credits so you can test any module before committing to a paid plan. Once you have both accounts, you link them inside Make using your PDF4me API key in the Connection dialog. The two accounts are independent and billing is managed separately on each platform.
Which API key should I use — developer portal or consumer portal?+
The developer portal at dev.pdf4me.com is recommended for automation use cases. It offers monthly subscription plans, automatic credit renewal, and a usage dashboard with per-call tracking. The consumer portal at pdf4me.com is a one-time purchase model better suited to lower-volume or infrequent needs. The API key format is identical in both cases — paste it into the Make connection dialog the same way regardless of which portal issued it.
Can I chain multiple PDF4me modules in one Make scenario?+
Yes, and this is the recommended pattern for multi-step document workflows. The Document Data output of one PDF4me module is a binary buffer that maps directly into the File input of the next — no intermediate upload step is needed. For example, you can Convert to PDF, then Compress PDF, then Add Text Watermark, all in a single scenario run. Each module consumes separate PDF4me credits, so factor that into your monthly usage estimate when planning complex scenarios.
What file sources can I use to supply documents to PDF4me modules?+
Any Make module that outputs a binary file works as a file source: Dropbox – Download a File, Google Drive – Download a File, Microsoft OneDrive – Download a File, Gmail – Get Attachment, Outlook – Get Attachment, HTTP – Get a File for public URLs, and Box – Download a File are all common sources. You can also use Make's Map toggle to wire filename and binary data directly from a webhook payload or any prior module. To read metadata like page count before processing, run Get Document Information first. For structured data extraction from existing PDFs, use Parse Document with a custom template before routing to downstream modules.
How do I handle errors when a PDF4me module fails in Make?+
Right-click the PDF4me module in the scenario builder and select Add error handler. The Resume route lets the scenario continue with a fallback; the Rollback route stops and reverts reversible operations. For transient failures such as temporary API unavailability, a Retry error handler with back-off is effective. Inspect the error bundle for the HTTP status code — 401 means the API key is invalid or expired, 429 means the rate limit was hit (wait and retry), and 400 typically indicates a missing or incorrectly formatted parameter. To pre-validate a file before a complex multi-step chain, add Get Document Information at the start — if it returns an error, the file is not a valid PDF and you can skip the rest of the scenario.

Get Help​

Make IntegrationGet your API KeyMake Documentation