Action

Password protect

Encrypt a PDF (AES-256)

Locks a PDF with a password using strong AES-256 encryption, so only someone who knows the passphrase can open it. Handy when the document holds private information and travels over email.

How it works

This node seals the file behind a password. Once it is encrypted, the PDF cannot be opened, read, or printed without the passphrase, even if the file lands in the wrong inbox.

The AES-256 part is the industry-standard strength banks and hospitals use, so this is real protection, not a token warning that a savvy person can click past.

The usual pattern is to encrypt the finished document and then share the password through a separate channel, for example texting it rather than putting it in the same email as the attachment.

Common use cases

Real situations where this node earns its place in a flow.

Lock a financial report

Password-protect a document that contains account details before it goes out.

Encrypt sensitive files

Add a passphrase to files that carry personal or medical information for compliance.

Share securely

Protect a packet so only the intended recipient, holding the password, can open it.

Password protect in a workflow

A simple example of where this node sits in a flow.

Render document Merge data + template → document Password protect Encrypt a PDF (AES-256) Email outbound Send report link

What you set up

  • Add it after the document is finished but before it is delivered.
  • Set the password the recipient will need to open the file.
  • Confirm the passphrase reaches the recipient through a separate, secure channel.

Common questions

What happens if the recipient loses the password?

The file cannot be opened without it, and it cannot be recovered from the file itself. Keep a record of the password and re-run the job if you need a fresh copy.

Should I email the password with the file?

No. Send the document one way and the password another (a text message, for example), so a single intercepted email does not expose both.