The flow
Starts it 2Logic 7Service 3
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Every Month the First Day of the MonthSchedule triggerStarts it
- 3ENV*SetLogic
- 4Clean and Escape ENVSetLogic
- 5Get all Invoices*Http RequestService
- 6List InvoicesSplit OutLogic
- 7We do only Invoice ObjectsIfLogic
- 8Download Invoice PDF from StripeHttp RequestService
- 9It shouldn't be something elseStop And ErrorLogic
- 10Inject s3 SubpathSetLogic
- 11Set-SubpathSetLogic
- 12Upload to S3 Bucket*Aws S3Service
How it's built
- Starts on
- A clock
- Steps
- 12, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- S3
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own S3 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. 12 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 12 steps before you point it at anything that matters.