Watermark and password-protect new Google Drive PDFs with Autype
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs on Google Drive events (file created). Along the way it connects Google Drive and Autype (community).
How it runs
Trigger: On Google Drive events (file created).
- Download PDF from Drive (Google Drive): download
- Upload PDF to Autype (Autype): work with file
- Add Watermark (Autype): watermark (document tools)
- Password-Protect PDF (Autype): protect (document tools)
- Save Watermarked PDF to Drive (Google Drive): uses Google Drive
- Save Protected PDF to Drive (Google Drive): uses Google Drive
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-autype is verified or supports 3.0 (used in Upload PDF to Autype, Add Watermark, Password-Protect PDF).
Nodes used (3)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Google Drive
n8n-nodes-base.googleDrive - Autype
n8n-nodes-autype.autype
From the author
Important: This workflow uses the Autype community node and requires a self-hosted n8n instance. This workflow watches a Google Drive folder for new PDF uploads. When a new file appears, it automatically creates two secure versions (one with a "CONFIDENTIAL"…