The flow
Starts it 1Logic 5Service 11
The steps in the order they run, from what starts it.
- 1Get accounts id from MaybeHttp RequestService
- 2Step 2 - Get institution idHttp RequestService
- 3Step 5 - Get account idHttp RequestService
- 4Schedule TriggerSchedule triggerStarts it
- 5Step 4 - Building link with RevolutHttp RequestService
- 6Step 3a - User agreement with first Revolut AccountHttp RequestService
- 7Step 3a - User agreement with second Revolut AccountHttp RequestService
- 8Get access tokenHttp RequestService
- 9Get Revolut Personal transactionsHttp RequestService
- 10Get Revolut Pro transactionsHttp RequestService
- 11Extract booked - Revolut PersonalItem ListsLogic
- 12Extract booked - Revolut ProItem ListsLogic
- 13Set transactions for Revolut PersonalSetLogic
- 14Set transactions for Revolut ProSetLogic
- 15Merge all transactions in one arrayMergeLogic
- 16Create transactions to MaybeHttp RequestService
- 17ResendResendService
How it's built
- Starts on
- A clock
- Steps
- 17
- 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. 17 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 17 steps before you point it at anything that matters.