Split large PDF files into 20-page chunks with Google Drive and PDF.co
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 14 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Google Drive and Pdfco (community). It also calls api.pdf.co over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Search files and folders (Google Drive): work with file folder
- Search Specific Folder (Google Drive): work with file folder
- Download file (Google Drive): download
- PDFco Api: upload file to pdf.co
- Merge: merges the data from its input branches
- Retrieve File Info (HTTP Request): calls api.pdf.co (POST)
- Determine file chunks (Code): runs custom JavaScript code
- Count Pages (Code): runs custom JavaScript code
- PDF.co file split (HTTP Request): calls api.pdf.co (POST)
- Build chunk file name (Code): runs custom JavaScript code
…plus 3 more steps. See the full node list below.
Services it uses
HTTP calls to: api.pdf.co
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-pdfco is verified or supports 3.0 (used in PDF.co API).
Nodes used (6)
- Google Drive
n8n-nodes-base.googleDrive - Code
n8n-nodes-base.code - PDFco Api
n8n-nodes-pdfco.PDFco Api - Merge
n8n-nodes-base.merge - Manual Trigger
n8n-nodes-base.manualTrigger - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick overview This workflow manually pulls PDF files from a Google Drive folder, uses PDF.co to detect page counts and split each PDF into 20-page chunks, then uploads the resulting chunk PDFs to a target Google Drive folder. How it works 1. Starts when you…