Automation library · E-commerce

Monitor OKX spot DCA orders and send trade alerts to Telegram

Started by a clock, and works across Telegram. 14 steps: a working afternoon to understand properly.

Medium

14 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 9Service 4

The steps in the order they run, from what starts it.

  1. 1Trigger Every MinuteSchedule triggerStarts it
  2. 2Authenticate OKX DCACodeLogic
  3. 3Get Ongoing DCA ListHttp RequestService
  4. 4Cycle List AuthenticationCodeLogic
  5. 5Fetch DCA Cycle ListHttp RequestService
  6. 6Compute DCA Cycle ProfitCodeLogic
  7. 7Assemble Current DCA CyclesCodeLogic
  8. 8Orders AuthenticationCodeLogic
  9. 9Fetch DCA OrdersHttp RequestService
  10. 10Reformat DCA OrdersCodeLogic
  11. 11Verify DCA Order AbsentCodeLogic
  12. 12Compose Telegram TextCodeLogic
  13. 13Send Telegram MessageTelegramService
  14. 14Log DCA Processed OrderCodeLogic

How it's built

Starts on
A clock
Steps
14
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. 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.

Before you run it

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.