Secure Document - Protection for Zapier

PDF4me Secure Document is a Zapier action that adds password protection and editing restrictions to Word files. Use it to require a password to open a document, or to restrict editing to read-only, comments-only, form fields, or tracked revisions. Returns a secured Word file for the next Zap step.

What this action does

Takes a Word document from a previous Zap step and applies one or both of two independent protections: an open password (Secure On Open) that must be entered before the file can be viewed at all, and an editing restriction (Protection Type) that limits what a user can do once the file is open, such as read-only, comments-only, form-field-only, or tracked-revisions-only editing. Each protection uses its own separate password. Ideal for confidential distribution, read-only reports, or review workflows where only comments are allowed.

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

To access the PDF4me Web API through Zapier, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Zapier workflows and PDF4me's Word document security services.

Get your API Key

What Counts as "Secure" for This Action?

This action does not sign, watermark, or redact a document. It applies two Microsoft Word-native protections: an encryption password required to open the file at all (Secure On Open), and a document-protection password that restricts what can be edited once the file is open (Protection Type). Both are standard Word protection features, applied programmatically instead of through the Word desktop UI.

Important Facts You Should Not Miss

Two independent protections, two passwords

Secure On Open Password unlocks the file for viewing. Document Protection Password removes the editing restriction inside Word. They can be the same value or different values.

File must provide full content, not a reference

If the File field shows "(Exists but not shown)" and the Zap errors, pick the mapping option that provides the full binary content of the Word file instead of a reference.

Protection Type has five options

ReadOnly, Allow Comments, Allow Form Fields, Allow Revisions, or No Protection. Document Protection Password is required whenever the type is not No Protection.

Map File from previous steps

Use the + button next to File and File Name to map from earlier Zap steps (e.g., Google Drive, Dropbox, or a trigger). The Word file must provide full content, not "Exists but not shown" references.

File: (Exists but not shown)

If you see "File: (Exists but not shown)" in the File field and get errors, select the option that provides the full file content instead. See Zapier & Power Automate Tips for details.

Configure the Secure Document action: map File, set File Name, Secure On Open = Yes with its password, and Protection Type = ReadOnly with Document Protection Password.

What Are the Key Features of Secure Document?

• Password Protection: Add password requirements to open documents
• Document Protection: Restrict editing capabilities with various protection types
• Read-Only Security: Make documents read-only to prevent unauthorized editing
• Comment-Only Access: Allow only comments to be added or modified
• Form Field Editing: Restrict editing to form fields only
• Revision Tracking: Allow only tracked changes and revisions
• Combined Security: Apply both password protection and editing restrictions
• Flexible Access Control: Different security levels for different use cases

Parameters

Complete list of parameters for the Secure Document action. Parameter names match the Zapier configuration UI shown in the screenshot above.

Quick setup checklist

1. Map File and File Name from previous step
2. Set Secure On Open = Yes and Secure On Open Password for encryption
3. Set Protection Type (ReadOnly, Allow Comments, etc.) and Document Protection Password if not "No Protection"

Parameter	Required	What it does	Example
File	Required	Word document to secure. Map from a previous step (Drive, Dropbox, trigger). Must provide full file content.	[2. File from Step 2]
File Name	Conditional	Word filename with .docx or .doc extension for the output file.	abc.docx
Secure On Open	Conditional	Enable password to open. Yes requires a password before the file can be opened at all.	Yes
Secure On Open Password	Conditional	Password to open the document. Required when Secure On Open is Yes.	12345
Protection Type	Conditional	Editing restriction applied once the file is open. ReadOnly, Allow Comments, Allow Form Fields, Allow Revisions, or No Protection.	ReadOnly
Document Protection Password	Conditional	Password to remove the editing restriction inside Word. Required when Protection Type is not No Protection.	1234

Important: Parameters marked Required must always be set. Parameters marked Conditional are required only when their corresponding security option is enabled (Secure On Open Password when Secure On Open = Yes; Document Protection Password when Protection Type is not No Protection).

What Does Secure Document Return?

The PDF4me Secure Document action returns the secured Word file for use in subsequent Zap steps. The output format is common across all PDF4me Word file-returning actions in Zapier.

Key output fields (map these to your next step)

File Url

API endpoint to download the secured Word file. Map this to the next step's file input.

api.pdf4me.com/Zapier/GetDocument?d=...

Alternate File Url

Alternative download URL with filename in path.

api.pdf4me.com/Zapier/GetAltDocument/.../document.docx

Field	Type	What it contains
Job Id	String	Unique identifier for the Zapier job execution.
File Url	URL	API endpoint to download the secured Word file.
Alternate File Url	URL	Alternate download URL with the filename in the path.
File Name	String	Base filename without extension.
Full File Name	String	Complete filename with extension.
File Extension	String	File extension of the returned file, .docx.

JSON

Example JSON output (URLs show format only, not working links):

{
"Job Id": "...",
"File Url": "api.pdf4me.com/Zapier/GetDocument?d=...",
"Alternate File Url": "api.pdf4me.com/Zapier/GetAltDocument/.../document.docx",
"File Name": "document",
"Full File Name": "document.docx",
"File Extension": ".docx"
}

Zap Integration

Use + to map File Url or Alternate File Url to the next step, Drive, Dropbox, Email, or another PDF4me Word action.

Typical Setups

Workflow ExamplesCommon Zapier workflow patterns using Secure Document.

Encrypted distribution of a finalized report

1. A trigger fires when a document is marked finalized in a shared Drive folder.
2. PDF4me Secure Document runs with Secure On Open = Yes and a Secure On Open Password, plus Protection Type = ReadOnly with a separate Document Protection Password.
3. A Gmail step emails the secured file, with the open password sent through a separate channel such as Slack.

Read-only distribution without an open password

1. A scheduled Zap retrieves the latest generated report from a Dropbox folder.
2. PDF4me Secure Document runs with Secure On Open = No and Protection Type = ReadOnly with a Document Protection Password, so anyone can open the file but not edit it.
3. The secured file uploads to a shared team folder for wide distribution.

Comment-only review before final sign-off

1. A draft document lands in a review folder, triggering the Zap.
2. PDF4me Secure Document sets Protection Type = Allow Comments with a Document Protection Password so reviewers can add comments but not change the underlying text.
3. An email step sends the review copy to stakeholders, with the protection password shared separately with the document owner.

Practical Tips

File: (Exists but not shown) causes errors

Select the mapping option that provides the file's full binary content instead of a reference. See Zapier & Power Automate Tips for the exact steps.

Secure On Open and Protection Type are independent

You can set either one alone, or both together with different passwords. Leaving Secure On Open = No still lets Protection Type restrict editing.

Document Protection Password is only required for restrictions

It is required whenever Protection Type is anything other than No Protection. If Protection Type is No Protection, this field can be left blank.

Send passwords through a separate channel

Emailing the secured file and its password in the same message defeats the purpose of the protection. Share the password via a different channel such as Slack or SMS.

File Name needs the correct extension

Include .docx or .doc explicitly in File Name so downstream steps and recipients see the correct file type.

Cheat Sheet

Field	Value
Action	Secure Document
File	[Mapped from previous step]
File Name	abc.docx
Secure On Open	Yes
Secure On Open Password	12345
Protection Type	ReadOnly
Document Protection Password	1234
Connection	PDF4me API key

Common Questions

How do I password protect a Word document in Zapier?+

Add the PDF4me Secure Document action to a Zap, map the Word file from a previous step using the full-content option, set Secure On Open to Yes, and enter a Secure On Open Password. See Microsoft's guide on protecting a Word document with a password for how the resulting file behaves when opened in Word.

How do I make a Word document read-only?+

Set Protection Type to ReadOnly and provide a Document Protection Password. Recipients can open and view the document freely but cannot edit the text without first removing the restriction in Word using that password.

What is the difference between Secure On Open and Protection Type?+

Secure On Open controls whether a password is required just to open the file at all, which is standard Word document encryption. Protection Type controls what a user who has already opened the file is allowed to do, such as read-only or comments-only editing. See Zapier's guidance on setting up actions for general help configuring action fields in a Zap.

How do I remove restricted editing from a Word document?+

Open the protected document in Microsoft Word, go to Review, Restrict Editing, and enter the Document Protection Password to stop protection. PDF4me applies the restriction during the Zap; removing it happens inside Word with the same password.

Can I combine an open password with read-only protection?+

Yes. Set Secure On Open to Yes with its own Secure On Open Password, and separately set Protection Type to ReadOnly (or another restriction) with its own Document Protection Password. The two protections are independent and can use different passwords.

Related Actions

Add Watermark

Stamp a visible watermark such as "Confidential" or "Draft" onto a Word document, a common companion step before or after securing it.

Extract Metadata

Read author, title, and other document properties before distribution, useful for logging what was secured and sent.

Optimize Document

Reduce file size before or after securing a Word document, useful when emailing large secured files.

Same Task on Other Platforms

Secure Document in Make

Same open-password and editing-restriction module, wired into visual Make scenarios with cloud-storage triggers.

Secure Word Document in n8n

The equivalent n8n node for developers who want the security logic inside a self-hosted or code-heavy workflow.

Secure Document in Power Automate

Microsoft 365 flows with SharePoint, Outlook, and Teams for organizations already standardized on Power Automate.

Secure Document REST API

The raw PDF4me API endpoint behind this action, for custom backend code or Postman testing.

Industry Use Cases & Applications

Finance & Accounting

• Financial Report Encryption: Encrypt quarterly financial statements before board distribution
• Salary File Protection: Password-protect compensation analysis documents
• Audit Working Paper Security: Encrypt audit files with firm-specific passwords
• Budget Template Protection: Apply read-only to budget templates preserving formulas
• Board Package Encryption: Secure board materials with encryption and read-only protection

Legal & Professional

• Client Matter Encryption: Password-protect client confidential matter documents
• Privileged Document Security: Encrypt attorney-client privileged communications
• Contract Read-Only Protection: Apply read-only to executed contracts preventing alterations
• Discovery Document Security: Encrypt confidential discovery productions
• Work Product Protection: Secure attorney work product with password encryption

Human Resources

• Personnel File Encryption: Secure employee records with password protection
• Performance Review Security: Encrypt performance review documents
• Compensation Analysis Protection: Password-protect salary and benefits analysis
• Policy Template Read-Only: Apply read-only to policy templates for consistency
• Confidential Memo Encryption: Encrypt sensitive HR communications

Corporate

• Strategic Plan Encryption: Password-protect strategic planning documents
• M&A Document Security: Secure merger/acquisition materials with dual passwords
• Confidential Proposal Protection: Encrypt sensitive business proposals
• Executive Report Security: Protect C-suite reports with password and read-only
• Product Launch Protection: Secure pre-launch documents preventing unauthorized edits

Get Help

Zapier IntegrationGet your API KeyZapier Documentation