Automation library · Alerts and monitoring

Student Housing Availability Monitor with Telegram and AWS S3

Started by a clock, and works across S3 and Telegram. 11 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 7Service 3

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

  1. 1Daily CheckSchedule triggerStarts it
  2. 2Define Source URLsCodeLogic
  3. 3Split URLs in BatchesSplit In BatchesLogic
  4. 4Scrape Housing ListingsScrapegraph AiService
  5. 5Merge ListingsMergeLogic
  6. 6Clean and Tag DataCodeLogic
  7. 7Price & Availability FilterIfLogic
  8. 8Aggregate For StorageCodeLogic
  9. 9Build Telegram MessageCodeLogic
  10. 10Upload JSON to S3Aws S3Service
  11. 11Send Telegram AlertTelegramService

How it's built

Starts on
A clock
Steps
11, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
S3, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own S3 and Telegram accounts. 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. 11 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 11 steps before you point it at anything that matters.