Automation library · Alerts and monitoring

Sap Business One update TRM Colombia with Telegram

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

Medium

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

The flow

Starts it 1Logic 8Service 8

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Login SL SAPHttp RequestService
  3. 3IfIfLogic
  4. 4Fecha ActualCodeLogic
  5. 5Mensaje a TelegramTelegramService
  6. 6Consultar la TRM en SAPHttp RequestService
  7. 7FinalizaNo OpLogic
  8. 8If1IfLogic
  9. 9SuperfinancieraHttp RequestService
  10. 10Logout SL SAPHttp RequestService
  11. 11XMLXmlLogic
  12. 12Finaliza2No OpLogic
  13. 13Actualizar TRM en SAP1Http RequestService
  14. 14If2IfLogic
  15. 15Mensaje a Telegram1TelegramService
  16. 16Logout SL SAP1Http RequestService
  17. 17Finaliza1No OpLogic

How it's built

Starts on
A clock
Steps
17, with 3 branches
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. 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.

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 17 steps before you point it at anything that matters.