The flow
Starts it 1Logic 9Service 3
The steps in the order they run, from what starts it.
- 1Every Monday at 07:00Schedule triggerStarts it
- 2Set the pages to archiveSetLogic
- 3Check the list is usableIfLogic
- 4Check remaining quotaPdf MintService
- 5Enough credits for this run?IfLogic
- 6Name this week's archiveCodeLogic
- 7One item per pageSplit OutLogic
- 8Render each page to PDFPdf MintService
- 9Keep the pages that renderedFilterLogic
- 10More than one page survived?IfLogic
- 11Merge into one archivePdf MintService
- 12The one page is the archiveSetLogic
- 13Say what was archivedSetLogic
How it's built
- Starts on
- A clock
- Steps
- 13, with 3 branches
- 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 a clock.
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. 13 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 13 steps before you point it at anything that matters.