Exercises 11 · AI Job Scout

Start from workflow/starter.json (triggers, settings, both fetches) or your finished lesson workflow.

Exercise 1: Telegram alerts

Task: Replace Send Alert (Exercise 1) with a Telegram message containing the report, but only when count > 0.

Done when: a scheduled run with good fits pings your phone; runs without fits stay silent.

Hint

Create a bot with @BotFather, get your chat ID (message the bot, then open https://api.telegram.org/bot<token>/getUpdates), add an IF on count, then Telegram Send Message with {{ $json.message }}.

Exercise 2: Never see the same job twice

Task: On the scheduled path, skip jobs that previous runs already scored.

Done when: two scheduled runs in a row don't score the same URL twice.

Hint

Remove Duplicates → Remove Items Processed in Previous Executions, value to dedupe on {{ $json.url }}, placed before Score Job. It stores seen values in n8n itself.

Exercise 3: Add a third source

Task: Add another board with an API or RSS feed (e.g. Remotive's public API https://remotive.com/api/remote-jobs?category=software-dev) into the merge.

Done when: dry-run output contains jobs from three sources.

Hint

Fetch → a new Normalize Code node → set Merge's Number of Inputs to 3.