Automation library · Alerts and monitoring

Automated hotel price drop alerts

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

Medium

14 stepsMedium: a working afternoon
1Branch: 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. 1Schedule - Every 6 HoursSchedule triggerStarts it
  2. 2Load Hotel ListCodeLogic
  3. 3Fetch Current Price from APIHttp RequestService
  4. 4Parse Price DataCodeLogic
  5. 5Get Previous Price from DBHttp RequestService
  6. 6Compare PricesCodeLogic
  7. 7Check if Price ReducedIfLogic
  8. 8Format Alert EmailCodeLogic
  9. 9Log No Alert NeededCodeLogic
  10. 10Send Email to Travel AgentEmail SendService
  11. 11Merge All LogsMergeLogic
  12. 12Log Alert SentCodeLogic
  13. 13Update Price in DatabaseHttp RequestService
  14. 14Create Execution SummaryCodeLogic

How it's built

Starts on
A clock
Steps
14, with 1 branch
Size
Medium: a working afternoon
Connects to
Email
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Email 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.