Generate merged onboarding PDF packets with PDFops and Google Drive
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 12 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Google Drive and Pdfops (community).
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Payload Valid? (If): checks a condition and branches into true / false
- Fetch Blank Form A (HTTP Request): calls an HTTP API
- Fetch Blank Form B (HTTP Request): calls an HTTP API
- Respond With Error (Respond to Webhook): sends the response back to the webhook caller
- Pdfops: fill
- Pdfops: fill
- Combine Filled Forms (Merge): merges the data from its input branches
- Both Forms Filled? (If): checks a condition and branches into true / false
- Pdfops: merge
- Upload Packet to Drive (Google Drive): upload (file)
…plus 1 more step. See the full node list below.
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-pdfops is verified or supports 3.0 (used in PDFops Fill Form A, PDFops Fill Form B, PDFops Merge Packet).
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - HTTP Request
n8n-nodes-base.httpRequest - Pdfops
n8n-nodes-pdfops.pdfops - Merge
n8n-nodes-base.merge - Google Drive
n8n-nodes-base.googleDrive - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Quick overview This workflow receives a webhook request with two fillable PDF form URLs and field values, fills and merges the PDFs using PDFops, uploads the combined onboarding packet to Google Drive, and returns a JSON success or error response to the…