Back to all workRunning system

Automated job search and alert pipeline

A scheduled workflow that pulls remote job listings from three sources, normalises fields that none of them format the same way, filters against my criteria, removes duplicates it has already seen, and sends what is left to Telegram.

n8n · REST APIs · Telegram

Telegram alert arriving on a phone, one message per job listing with the role title, company and a link — One alert as it arrives on the phone. One message per listing that survived the filters.

What one recorded run did

124 listings collected across three sources. Boolean and exclusion filters cut them to seven. Deduplication against previous runs left five. Five alerts arrived in Telegram.

Collected from 3 sources124
After filters7
After removing duplicates5
Sent to Telegram5

One recorded run. The workflow canvas below shows the same counts.

n8n workflow canvas for the job pipeline, with item counts printed along the connectors between the fetch, normalise, filter, deduplicate and Telegram nodes — The same run inside n8n. The numbers printed along the connectors are the counts passing between each step.

What is not proven

It runs from my own computer on a schedule, which means it stops when the machine sleeps. It has not been tested across weeks of unattended running, API outages, or source websites changing their response format.

What I would do next

Move it to hosting that does not depend on my laptop, then measure failure rate, duplicate handling and cost across repeated scheduled runs.