Automatically sign PDFs from a watched Google Drive folder with PDF API Hub
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 Pdf Api Hub (community).
How it runs
Trigger: On Google Drive events (file created).
- Download file (Google Drive): download
- Config (Edit Fields (Set)): sets or maps fields
- Is PDF? (If): checks a condition and branches into true / false
- Sign a PDF with a signature image (Pdf Split Merge): work with watermark
- Upload file (Google Drive): uses Google Drive
- Log (Edit Fields (Set)): sets or maps fields
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-pdf-api-hub is verified or supports 3.0 (used in Sign a PDF with a signature image).
Nodes used (5)
- Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Google Drive
n8n-nodes-base.googleDrive - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Pdf Split Merge
n8n-nodes-pdf-api-hub.pdfSplitMerge
From the author
Auto E-Sign PDF — Google Drive Watcher Automatically signs PDF documents the moment they land in a Google Drive folder — no manual steps needed. The signed output is routed to a Drive folder. --- How it works 1. Google Drive Trigger watches a folder every…