Automatic PDF compression with iLovePDF for Google Drive files
Ready for 3.0What this workflow does
This workflow has 10 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Google Drive. It also calls api.ilovepdf.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Send your iLoveAPI public key to their server (HTTP Request): calls api.ilovepdf.com (POST)
- Download file (Google Drive): download
- Get task from iLoveAPI server (HTTP Request): calls api.ilovepdf.com
- Group public key, task and downloaded file data (Merge): merges the data from its input branches
- Upload PDF to iLoveAPI server (HTTP Request): calls an HTTP API (POST)
- Compress your file (HTTP Request): calls an HTTP API (POST)
- Download compressed file (HTTP Request): calls an HTTP API
- Move compressed file to new Google Drive folder (Google Drive): move
Services it uses
HTTP calls to: api.ilovepdf.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- Manual Trigger
n8n-nodes-base.manualTrigger - Google Drive
n8n-nodes-base.googleDrive - Google Drive Trigger
n8n-nodes-base.googleDriveTrigger - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest
From the author
Watch Google Drive folder and use iLovePDF Compress Tool to save it in another Google Drive folder This n8n template shows how to upload a file in your Google Drive desired folder, compress it with the iLovePDF tool and move the compressed file to another…