Two automation workflows, running

Both were built before the proposal was written. Every number and every message on these pages comes from a real run against the live sources today — the pages are generated from the run output.

Govt Exam Notification Alert Bot →

Scrapes exam sites and aggregators, filters what was already seen, AI extracts eligibility and dates, alerts only what the candidate can actually apply to.

UPSC Daily Current Affairs Digest →

Eleven RSS sources, 24-hour window, deduplication, AI summary and syllabus tagging, Google Sheet, Telegram digest split across messages.

How both are built

One file each, nothing to install. Node 18+ and the standard library. No npm dependencies at all — including the Google Sheets integration, which signs its own JWT.
Google Sheets and Telegram are wired and optional. With credentials they deliver; without them the exact output that would have been sent is written to disk, so it can be inspected before anything goes live.
A dry-run mode that touches nothing external.
Failures are isolated. One dead source does not stop a run.

Why the write-ups mention what went wrong

Each page lists the bugs the first runs exposed — eligibility fields that came back empty and made the filtering meaningless, a duplicate that only appeared after translation, an alert for a vacancy that had closed ten months earlier. They are there because the difference between “I built it” and “I ran it” is exactly that list, and because a workflow you cannot audit is one you have to trust blindly.

Built by Dilan Del Valle · automation & data integration.
Every number and every message on this page comes from a real run against the live sources — the page is generated from the run output, not written by hand.