Secure Document - Protection for Zapier

PDF4me Secure Document action enables adding password protection and security restrictions to Word documents within Zapier workflows with comprehensive security controls and editing restrictions. This powerful document security service supports open password protection (password required to open file), document editing restrictions with five protection types (No Protection, Read Only, Allow Comments, Allow Form Fields, Allow Revisions), combined security (both password and editing restrictions), and flexible access control—perfect for confidential documents, collaborative editing with restrictions, document access control, and secure distribution workflows across cloud storage platforms and business applications.

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 powerful Word document security services.

Get your API Key

Key Features

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 action. Configure these parameters to control document security behavior.

Important: Parameters marked with an asterisk (***) are required. Password parameters are required when their corresponding security options are enabled.

Parameter	Type	Description	Example
File Name***	String	Word Document Name • Filename with .docx or .doc extension • Used for processing and output file identification • Supports dynamic naming from Zap variables	`document.docx`
Document***	File	Word File Content • Map from previous step (Drive/Dropbox/HTTP) • Binary Word document to secure • Must be valid Word format (.docx, .doc) • Security settings applied to this document	`[File]`
Secure On Open	Boolean	Enable Password Protection • Yes - Requires password to open document • No - No password required to open (default) • Uses Word's built-in password encryption • Password encrypted and stored in document • Requires Open Password when enabled	`Yes`
Open Password	String	Password to Open Document • Password required to open the document • Required when Secure On Open = Yes • Should be strong password (8+ characters) • Supports alphanumeric and special characters • Case-sensitive password	`SecurePass123!`
Security Options Protection Type	String	Document Protection Type • "No Protection" - No editing restrictions (default) • "Read Only" - Document cannot be edited, only viewed • "Allow Comments" - Only comments can be added/modified • "Allow Form Fields" - Only form fields can be edited • "Allow Revisions" - Only tracked changes/revisions allowed • Controls document editing capabilities • Requires Protection Password when not "No Protection"	`Read Only`
Security Options Protection Password	String	Password for Document Protection • Password to remove document protection • Required when Protection Type is not "No Protection" • Should be different from Open Password • Allows authorized users to remove protection • Case-sensitive password	`EditPass456!`

Output

The PDF4me Secure Document action returns comprehensive output data for seamless Zapier workflow integration:

Table
JSON
Zap Integration

Table View

Parameter	Type	Description
File	URL	Direct URL to access the secured Word
File Name	String	The filename without extension
Full File Name	String	Complete filename with .docx extension
File Extension	String	File extension (.docx)

JSON Response Format

{
  "File": "https://...",
  "File Name": "document",
  "Full File Name": "document.docx",
  "File Extension": ".docx"
}

Scenario Examples

The PDF4me Secure Document action in Zapier provides comprehensive scenario templates:

Confidential Distribution
Read-Only Distribution
Review Workflow

Encrypted Document Distribution Workflow

Complete Scenario Steps:

Trigger: Confidential report finalized
Get Sensitive Document: Retrieve from secure folder
Apply File Encryption: Secure On Open = Yes, Open Password = strong password
Apply Read-Only: Protection Type = "Read Only", Protection Password = separate password
Double Protection: Both encryption and editing restriction
Upload Protected: Save to distribution folder
Email Recipients: Send with password via separate channel
Email Protection Password: Send separately for edit removal if needed
Log Distribution: Record secure distribution event
Archive Original: Store unprotected version securely

Business Benefits:

Secures 100+ confidential documents monthly
Dual-layer protection prevents unauthorized access and editing
Password separation enhances security
Eliminates manual protection application saving 10 minutes per document

Create Zap

Industry Use Cases & Applications

Finance & Accounting
Legal & Professional
Human Resources
Corporate

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

Get Help

Zapier Integration Get your API Key Zapier Documentation

Authenticating Your API Request​

Key Features​

Parameters​

Output​

Scenario Examples​

Industry Use Cases & Applications​

Get Help​