The flow
Starts it 2Logic 1Service 7
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Upload your file to Google DriveGoogle Drive triggerStarts it
- 3Send your iLoveAPI public key to their serverHttp RequestService
- 4Download fileGoogle DriveService
- 5Get task from iLoveAPI serverHttp RequestService
- 6Group public key, task and downloaded file dataMergeLogic
- 7Upload PDF to iLoveAPI serverHttp RequestService
- 8Compress your fileHttp RequestService
- 9Download compressed fileHttp RequestService
- 10Move compressed file to new Google Drive folderGoogle DriveService
How it's built
- Starts on
- An event in a connected app
- Steps
- 10
- Size
- Medium: a working afternoon
- Connects to
- Google Drive
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 10 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.