The flow
Starts it 1Logic 10Service 8
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2GET example PDF filesHttp RequestService
- 3Extract PDF linksHtmlLogic
- 4Split links into itemsSplit OutLogic
- 5Use two relevant PDF examplesLimitLogic
- 6Download example PDF FilesHttp RequestService
- 7Pass through binarySetLogic
- 8Get Presigned Upload URL (PDF.co)Http RequestService
- 9Combine binary and json dataMergeLogic
- 10Upload PDF to Presigned URLHttp RequestService
- 11Strip binary dataSetLogic
- 12Combine dataMergeLogic
- 13Split multipage PDF filesHttp RequestService
- 14Loop over pdf filesSplit In BatchesLogic
- 15Compress into zip fileCompressionService
- 16Split out urlsSplit OutLogic
- 17Convert PDF to PNG (PDF.co)Http RequestService
- 18Download PNG from PDF.coHttp RequestService
- 19Combine binariesAggregateLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 19, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n 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. 19 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.
Before you run itNothing 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 19 steps before you point it at anything that matters.