The flow
Starts it 1Logic 12Service 6
The steps in the order they run, from what starts it.
- 1Run Every 5 MinutesSchedule triggerStarts it
- 2Time FilterCodeLogic
- 3Set InputsSetLogic
- 4Set Inputs2SetLogic
- 5Set Inputs3SetLogic
- 6Fetch Candles (Strategy1)Http RequestService
- 7Fetch Candles (Strategy2)Http RequestService
- 8Fetch Candles (Strategy3)Http RequestService
- 9Strategy1: Momentum EMACodeLogic
- 10Strategy2: RSI BreakoutCodeLogic
- 11Strategy3: MACD CrossoverCodeLogic
- 12Combine Strategy SignalsMergeLogic
- 13Filter Active SignalsCodeLogic
- 14Has Valid SignalIfLogic
- 15Combine Signal With BalanceMergeLogic
- 16Get Account BalanceHttp RequestService
- 17Calculate Position SizeCodeLogic
- 18Send Telegram MessageTelegramService
- 19Place OANDA OrderHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 19, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Telegram 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. 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.
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 19 steps before you point it at anything that matters.