Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Remove Password from PDF in Make

What this module does

PDF4me — Remove Password from PDF permanently decrypts and unlocks password-protected PDFs inside your Make scenario. Provide the PDF buffer and the correct password — the module returns an unrestricted PDF ready for editing, merging, splitting, or content extraction in the next modules of your scenario. Works with both user passwords (open protection) and owner passwords (permission restrictions) so a single module clears all access barriers in one step.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog →

Authenticating Your API Request​

Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate PDF unlocking requests securely.

Get your API Key

Important Facts You Should Not Miss​

The password must match exactly — the module does not guess
The module requires the correct password supplied in the Password field. If the password is wrong, the module returns an error and the scenario stops. Store passwords securely in Make's Data Stores, environment variables, or a connected secrets manager — never hardcode them in the scenario configuration where they are visible in plain text.
Output is a plain unlocked PDF buffer — no extra step needed
The module returns Doc Data (unlocked PDF buffer) and Name (filename). Map the Doc Data output directly into downstream PDF4me modules — Convert to Word, Add Watermark, Merge PDFs, Extract Pages — without any additional conversion step. The output PDF has all restrictions permanently removed and is immediately usable.
Use an Iterator to batch-unlock multiple PDFs
To unlock multiple password-protected PDFs in one scenario run, use a Repeater or Iterator before this module. Each iteration passes one PDF and its password. The unlocked output can then be routed to cloud storage (Dropbox, Google Drive, SharePoint) or another processing module in the same scenario, making bulk unlocking fully automated.
Make PDF4me Remove Password from PDF module showing Connection set to My PDF4me connection, File set to Map with File Name and Document mapped from the prior download step, and Password field with the document password entered

Set File to Map, wire File Name and Document from the prior download step, then enter the Password. The Doc Data output is the fully unlocked PDF ready for any downstream module.

Parameters​

Required: Connection, File Name, Document, and Password must all be provided. The module cannot decrypt a PDF without the correct password.

ParameterRequiredWhat it doesExample
ConnectionYesPDF4me API connection. Click Add and paste your API key if connecting for the first time. Reused automatically across all PDF4me modules in your scenarios.My PDF4me connection
FileYesHow the protected PDF is supplied. Choose Map to wire File Name and Document from a prior module. Choose Dropbox – Download a File to pull directly from Dropbox without a separate download step.Map
File NameYesFilename of the password-protected PDF including .pdf extension. Map from the filename output of your source module — e.g. the Name field of a Dropbox or Google Drive download step.protected_document.pdf
DocumentYesBinary content of the password-protected PDF. Must be raw file bytes from a download or upload module — the Data field in Dropbox, Google Drive, or OneDrive. Do not pass a URL string or filename here.1. Data
PasswordYesThe exact password needed to unlock the PDF. Accepts both user passwords (open protection) and owner passwords (permission lock). Retrieve from a Make Data Store or environment variable rather than hardcoding.SecurePass2024

Output Fields​

FieldTypeWhat it contains
NameStringOutput filename with password removed. Map into an upload module as the destination filename.
Doc DataBufferUnlocked PDF document as a binary buffer with all password restrictions permanently removed. Map directly into any downstream PDF4me module or cloud storage upload step.

Quick Setup​

  1. Add PDF4me → Remove Password from PDF to your Make scenario.
  2. Select Connection (or click Add to create one with your PDF4me API key).
  3. Under File, choose Map to reveal the File Name and Document fields.
  4. Map File Name to the filename output of your source step (include .pdf extension).
  5. Map Document to the binary data field of the same step — typically named Data in Dropbox, Google Drive, or OneDrive modules.
  6. Enter the Password. For security, retrieve it from a Make Data Store lookup step rather than hardcoding it here.
  7. Click Save and run the scenario. Map the Doc Data output to the next module — upload, merge, convert, or archive the unlocked PDF.

Workflow Examples​

Workflow ExamplesCommon Make scenario patterns using Remove Password from PDF.
Protected archive batch → unlock → convert to PDF/A → store
  1. A watch folder trigger fires when new protected PDFs land in a Dropbox archive inbox.
  2. A Data Store Search step retrieves the correct password for the document based on its filename.
  3. Remove Password from PDF decrypts the locked file using the retrieved password.
  4. A PDF4me Create PDF/A module converts the unlocked PDF to the archival PDF/A format required by the records system.
  5. The compliant PDF/A uploads to the long-term archive folder in SharePoint. An index record is appended to Google Sheets with the filename and processing date.
Protected invoice email → unlock → extract data → post to accounting
  1. Gmail triggers when a new email arrives from a known vendor address with a PDF invoice attachment.
  2. A Data Store lookup retrieves the vendor's invoice password by sender email address.
  3. Remove Password from PDF unlocks the encrypted invoice.
  4. A PDF4me Extract Text or AI-Invoice Parser module reads the invoice number, amount, and due date from the unlocked PDF.
  5. An HTTP module creates the invoice record in the accounting system. The unlocked PDF uploads to the "Processed Invoices" folder in Dropbox for audit reference.
Mixed document package → unlock each → merge → number pages → deliver
  1. A webhook fires when a document package assembly is requested via a form submission.
  2. Google Drive lists all PDF files in the project folder — some protected, some not.
  3. An Iterator loops over each file. A Router checks if the file is protected; if so, Remove Password from PDF unlocks it using the project password from a Data Store.
  4. PDF4me Merge PDFs combines all unlocked files into a single package document.
  5. Add Page Numbers stamps the merged document. Gmail delivers the final package to the requester with a confirmation message.

Frequently Asked Questions​

What types of PDF password does this module remove?+
The module removes both user passwords (open protection — the password you must enter just to open the file) and owner passwords (permission restrictions — locks that prevent editing, printing, or copying content). Supply whichever password type protects your document in the Password field and the module decrypts that restriction layer permanently.
What happens if I enter the wrong password?+
The module returns an error and the scenario stops at that step. There is no partial unlock — the operation is all-or-nothing for security reasons. If you process multiple PDFs with different passwords, use a Make Data Store keyed by filename or document ID to look up the correct password for each file automatically before passing it to this module.
How do I pass the password securely without hardcoding it in the scenario?+
Store the password in Make's Data Store and retrieve it with a Data Store Search step placed before this module. Alternatively, pull it from a secure external service via an HTTP module, or use a Make environment variable. Never type the password directly into the Password field in the module configuration — it will be visible in plain text to anyone who can view your scenario setup.
Can I unlock multiple protected PDFs in a single scenario run?+
Yes. Add a Repeater or an Iterator before this module and wire each file and its corresponding password into the module inputs per iteration. The unlocked Doc Data from each iteration can then be routed to cloud storage, a merge step, or any other downstream module. This pattern handles batch processing of any number of protected PDFs in a single automated run without manual intervention.
Does the original protected file in cloud storage get modified?+
No. PDF4me processes a copy and returns the unlocked PDF in the Doc Data output field. Your source file in Dropbox, Google Drive, SharePoint, or any other storage remains completely untouched and still password-protected. You control where the unlocked output is saved by wiring the Doc Data output to a subsequent upload or save module.

Get Help​

Make IntegrationGet your API KeyMake Documentation