The flow
Starts it 1Logic 5Service 8
The steps in the order they run, from what starts it.
- 1When clicking 'Test workflow'Manual triggerStarts it
- 2⚙️ ConfigSetLogic
- 3Get Public KeyHttp RequestService
- 4Get ChallengeHttp RequestService
- 5Encrypt TokenCodeLogic
- 6Init AuthHttp RequestService
- 7Wait 2sCodeLogic
- 8Check Auth StatusHttp RequestService
- 9Redeem TokenHttp RequestService
- 10Query InvoicesHttp RequestService
- 11Extract InvoicesCodeLogic
- 12Format for SpreadsheetCodeLogic
- 13Write XLSXSpreadsheet FileService
- 14Close SessionHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 14
- 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. 14 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 14 steps before you point it at anything that matters.