Lottery-results verification in n8n
About 10 parallel n8n workflows cross-check API results against crawled pages, score each source on speed and accuracy, and alert via Google Chat.
- Status
- Production
- Period
- Mar 2025 – Feb 2026
- Role
- Data Scientist (AI & Automation), Nam Viet Media
- Code
- Proprietary
- Stack
- n8n
- REST APIs
- Web crawling
- SQL database
- Google Sheets API
- Google Chat
- Workflows running in parallel
- ~10
- Front-end API
- Crawled pages
- Parse + cross-check
- Database
- Source scoring
- Sheets reports + Chat alerts
Problem
Published lottery results have to be right and on time. The company needed to verify them against more than one source, automatically.
Approach
I built a lottery-results verification system entirely in n8n, made of about 10 workflows running in parallel.
- Pull results from the API that feeds the front end.
- Crawl the published pages.
- Parse and cross-check both sources, and store them in a database.
- Score each source on speed and accuracy.
- Push reports to Google Sheets and alerts to Google Chat.
Architecture
Two independent inputs (the API and the crawled pages) run through parsing and a cross-check, land in a database, and feed a scoring step. Reporting (Google Sheets) and alerting (Google Chat) are separate outputs.
Results
The verification runs as about 10 parallel workflows, and every source gets a speed and accuracy score.