Secure Word Document in n8n

Secure Word Document is a PDF4me node action in n8n that locks a .docx file with a password, an editing restriction, or both. Use it to protect confidential reports before they are sent, keep a signed template from being altered, or let reviewers comment on a contract without changing its text.

What this node does

PDF4me Word: Secure Word Document applies two independent kinds of protection. Secure On Open plus Open Password decides whether the file opens at all. Protection Type plus Protection Password decides what may be changed once it is open, from fully read-only to comments, form fields, or tracked revisions only. Use either, or both together.

Authenticating Your API Request

Every PDF4me node in n8n requires a valid Credential to connect with. Create or select one that holds your PDF4me API key so the workflow can authenticate document security requests.

Get your API Key

Important Facts You Should Not Miss

Two passwords, two different jobs

Open Password gates the file. Protection Password gates editing. Setting them to the same value hands an editor the keys to both, which defeats the point of the restriction.

Never type a password into the node

Anything entered directly lands in the saved workflow JSON, which gets exported and often committed to git. Use an expression that reads a credential or environment variable.

Protection is applied, not recoverable

This action adds protection. If the passwords are lost there is no path back through this node, so store both values before the workflow runs at scale.

The PDF4me Word node in n8n with Operation set to Secure Word Document, Word File Input Method set to From Previous Node, Secure On Open toggled on, Protection Type set to Read Only, and Output File Name set to secured_document.docx — Secure On Open is a toggle, and Protection Type is a separate dropdown set to Read Only here. The two password fields beneath them are independent of each other.

Open Password vs Editing Restriction

Question	Open password	Editing restriction
Which fields set it	Secure On Open and Open Password	Protection Type and Protection Password
What it blocks	Opening the document at all	Changing the document once open
Can the recipient read it	Only with the password	Yes, reading is always allowed
Typical recipient	A named person receiving something confidential	A reviewer or a form filler
Use it when	The content must not be seen by others	The content may be seen but not altered

What Parameters Does Secure Word Document Need?

Parameter	Required	What it does	Example
Credential to connect with	Required	The PDF4me account credential the node authenticates with.	`PDF4ME account`
Operation	Required	The action this node performs. Select Secure Word Document.	`Secure Word Document`
Word File Input Method	Required	How the .docx reaches the node: from the previous node as binary data, as a Base64 string, or from a URL.	`From Previous Node (Binary Data)`
Binary Data Property Name	Conditional	Name of the binary property holding the document. Appears when the file comes from the previous node.	`data`
Document Name	Required	Filename of the input document including the extension. Drives format detection.	`document.docx`
Secure On Open	Optional	Toggle that requires a password before the document will open. Leave off if you only want an editing restriction.	`enabled`
Open Password	Conditional	The password needed to open the file. Required once Secure On Open is enabled. Supply it through an expression, not as literal text.	`{{ $env.DOC_OPEN_PW }}`
Protection Type	Optional	Editing restriction applied to the document: Read Only, Allow Comments, Allow Form Fields, or Allow Revisions.	`Read Only`
Protection Password	Conditional	The password that lifts the editing restriction. Required once a Protection Type is chosen, and should differ from Open Password.	`{{ $env.DOC_EDIT_PW }}`
Output File Name	Optional	Filename of the returned secured document. Keep the .docx extension.	`secured_document.docx`
Output Binary Data Name	Optional	Binary property the secured document is written to. Leave as data unless a later node expects another name.	`data`

Protection Type options

Option	What the recipient can do
`Read Only`	View the document only. No edits of any kind are accepted.
`Allow Comments`	Add and edit comments, but not change the document text itself.
`Allow Form Fields`	Fill in form fields while the surrounding content stays locked.
`Allow Revisions`	Edit, but only with tracked changes recorded so every alteration is visible.

Output

Field	Type	What it contains
fileName	`String`	Name of the returned secured document.
fileSize	`Number`	Size of the secured document in bytes.
success	`Boolean`	Whether protection was applied. Branch on this so failures surface as alerts.
originalFileName	`String`	Name of the input document as supplied in Document Name.
secureOnOpen	`Boolean`	Whether an open password was applied, echoed back for verification.
protectionType	`String`	The editing restriction applied, such as ReadOnly, or empty when none was set.
message	`String`	Human-readable status text describing the result of the operation.

Checking protectionType in the response is the cheapest way to confirm the restriction you intended is the one that actually landed.

How Do I Set Up Secure Word Document in n8n?

Add the PDF4me Word node to your workflow and set Operation to Secure Word Document.
Select your PDF4me credential, or create one and paste your API key.
Pick a Word File Input Method and supply the .docx through the field beneath it.
Set Document Name with the correct extension.
To gate opening, turn on Secure On Open and set Open Password from a credential or environment variable.
To gate editing, set Protection Type and supply a different Protection Password.
Set Output File Name ending in .docx.
Execute the node, confirm secureOnOpen and protectionType in the response, then route the secured file onward.

Typical Setups

Workflow ExamplesCommon n8n workflow patterns using Secure Word Document.

Send a confidential report

A reporting step produces a document with sensitive figures.
Secure On Open applies a password held in an environment variable.
The file is emailed, and the password is shared over a separate channel.

Circulate a contract for comment

Protection Type is set to Allow Comments.
Reviewers annotate without altering any clause text.
Feedback arrives without a diff to reconcile afterwards.

Distribute a fillable form

Allow Form Fields keeps the surrounding wording fixed.
Recipients complete only the fields intended for them.
Returned forms are consistent enough to parse automatically.

Lock an approved template

A template is approved and published to a shared drive.
Read Only protection prevents silent local edits.
Everyone works from the same authoritative wording.

Practical Tips

Keep passwords out of the workflow

An expression reading a credential or environment variable keeps the secret out of exported workflow JSON and out of version control.

Use different values for the two passwords

Reusing one value means anyone who can open the file can also unlock editing, which removes the distinction you set up.

Pick the least restrictive type that works

Allow Comments or Allow Revisions often serves a review better than Read Only, because reviewers can still express changes.

Verify protectionType in the response

The echoed value confirms the restriction landed as intended, which is faster than opening a sample in Word every run.

Secure last in the chain

Watermarking, merging, and header updates all need an editable file. Apply protection after those steps, not before.

Record the passwords before scaling up

This action applies protection and offers no recovery. Store both values in your secret manager before running it across a batch.

Cheat Sheet

Field	Value
Operation	`Secure Word Document`
Word File Input Method	`From Previous Node (Binary Data)`
Binary Data Property Name	`data`
Document Name	`document.docx`
Secure On Open	`enabled`
Open Password	`{{ $env.DOC_OPEN_PW }}`
Protection Type	`Read Only`
Protection Password	`{{ $env.DOC_EDIT_PW }}`
Output File Name	`secured_document.docx`
Output Binary Data Name	`data`

Common Questions

What is the difference between the open password and the protection password?+

The open password gates the file itself: without it the document will not open at all. The protection password gates editing: the document opens for anyone but stays restricted until that second password is entered. They are separate fields and should hold different values, because a recipient who needs to read but not edit should only ever receive the first one.

What do the Protection Type options do?+

Read Only stops edits entirely. Allow Comments permits commenting but no text changes. Allow Form Fields permits filling fields while the rest stays locked. Allow Revisions permits editing only with tracked changes recorded. Microsoft describes the equivalent desktop behaviour under restricting changes in Word.

Where should I store the passwords in n8n?+

Not in the node. A password typed directly into either field is saved inside the workflow JSON, which gets exported, shared, and often committed to version control. Reference an n8n credential or an environment variable through an expression so the secret stays out of the workflow definition.

Can I apply both an open password and an editing restriction at once?+

Yes. Secure On Open and Protection Type are independent, so a document can require a password to open and still be read-only afterwards. That combination suits a confidential document a named recipient may read but nobody may alter.

How do I remove the protection later?+

Editing restrictions are lifted in Word by supplying the protection password, and the open password is entered when the file is opened. Keep both values in your secret store rather than relying on memory, because this action applies protection and there is no recovery path through it if the passwords are lost.

Secure Excel

The same protection idea for spreadsheets arriving in the same workflow.

Protect Document

Apply password protection to a PDF rather than a Word file.

Add Image Watermark To Word Document

Brand or mark the document before you lock it down.

Disable Tracking Changes In Word

Turn revision recording off, a different lever from the Allow Revisions restriction.