In production

n8n automation workflows

32 live automation workflows across HR, QA, R&D, production, marketing and IT that turn data from company systems into Telegram and email alerts.

Period: 2025 – 2026
Role: Sole developer
Used by: Office and IT

n8n email listing expired and expiring raw-material test reports

Telegram bot confirming each fingerprint check-in and check-out

Attendance workflow: webhook in, chat ID lookup, then a message in the employee’s language

Screens from the live system. Names, IDs, figures and document codes have been replaced with sample values.

The problem

Many follow-ups depended on someone remembering to check: expiring raw-material documents, certificates and trademarks, trips missing paperwork, or attendance scans. Things slipped and were noticed late.

What I built

Made n8n the company’s automation hub: it pulls from SQL Server, Google Sheets and agency websites on a schedule, or receives webhooks from my own systems (TimeStamp, X-ray Sentinel, the production dashboard), then formats the message and sends it to the right people.

Key features

An attendance alert on Telegram for every fingerprint scan, in the employee’s language (Thai, Myanmar, Khmer, Lao, English)
A Telegram sign-up bot that checks the employee ID, links the chat ID automatically and sends a welcome in the right language
Missing-scan alerts before each payroll cut-off, and a monthly Excel summary of new and leaving staff
Email alerts for expired or expiring Test Report and HALAL documents with a summary table and file links, plus customer-complaint follow-up every two hours
FoodLexAI: 16 workflows that scan food-law agencies in 16 countries and bodies (e.g. Thai FDA, Department of Fisheries, ACFS, WTO SPS), de-duplicate, and feed FoodLex
Alerts when a production line reaches its plan, packaging idle for 180+ days, trademarks nearing expiry, and trips missing documents

Under the hood

My systems post webhooks to a single n8n entry point, so channels and wording change without touching the source code
Separate “Test” and “Production” send nodes in each workflow, so messages are checked before they reach real users
Send results are written back to SQL Server (e.g. a trip-reminder log, a complaint “sent” flag) to avoid duplicates and share cooldowns with the source systems
Each FoodLexAI workflow has 30–40 nodes: it pulls several sources per country, parses them in Code nodes, checks what it has seen before, and stores only new items

All live workflows

32 published workflows in n8n. Canvas images are from the live system, with internal IPs and URLs blurred.

FoodLexAI | Food Regulation Alert v2.5 (16 workflows)

Schedule, Daily FoodLex + Email 22–45 nodes

Scans food, export and fisheries law agencies in 16 countries and bodies, has AI write Thai summaries and rate relevance, stores new items in FoodLex and emails each new law.

StepsSchedule → fetch sources in parallel (HTTP, or WebFetcher for JavaScript-rendered sites) → parse (Code) → merge → seen before? → OpenRouter summary → de-duplicate → insert into FoodLex’s SQL Server → email alert

Email seen

Countries and bodies tracked

HR

TimeAttendanceLog ZKdriver - Webhook

Webhook from another system Telegram 11 nodes

Tells employees on Telegram every time they scan in or out, in their own language.

Steps Webhook from TimeStamp → look up chat ID → has Telegram? → switch by nationality → format in 5 languages → send on Telegram

Telegram message seen

Cutoff Payroll Ready (HR)

Schedule , Before daily and monthly pay cut-offs Telegram 20 nodes

Before each pay cut-off, tells each employee on Telegram which days are missing a scan.

Steps Cut-off schedules → employees with Telegram → work out the period → fetch work times → find missing days → group → switch language → send on Telegram

Automation Insert TelegramChatID Employee (IT)

Telegram bot message Telegram + SQL Server 25 nodes

Sign-up bot: an employee sends their ID, it is checked against HR data, the chat ID is linked automatically and a welcome goes out in their language.

Steps Telegram trigger → new user? → de-duplicate → check employee record → insert or update chat ID → switch by nationality → welcome in 5 languages

Certificate Expiry Monitoring System

Schedule , 1st of each month, 09:00 Email 10 nodes

Finds certificates and documents that are expiring or overdue and emails a summary with an Excel file.

Steps Monthly schedule → documents from SQL Server → keep those with an expiry → compute days left/overdue → sort → Excel → HTML email

Employee Lifecycle Monitor (HR)

Schedule , Monthly Email 12 nodes

Monthly summary of new and leaving staff, with Excel attachments for the teams that need it.

Steps Monthly schedule → new and leaving staff → split by type → two Excel files → email

QA

Agreement Spec - Expiration Alert (HALAL & Test Report)

Schedule , Daily, 09:00 Email 7 nodes

Emails a summary table of raw-material HALAL certificates and test reports that have expired, expire today or are about to, with file links.

Steps Schedule → HALAL and test-report records from SQL Server → build an HTML email for each → send (with a separate test node)

Email seenSuccessful runs in n8n

Complaint Automation System

Schedule , Twice a day Email + SQL Server 7 nodes

Gathers new customer complaints into a summary email, then flags them as sent so none go out twice.

Steps Schedule → unsent complaints → HTML table → send email → mark as sent

Email seen

R&D

PFP FollowUp Sample Product Bot

Schedule , Daily, 09:00 Email 10 nodes

Follows up open product-sample requests between R&D and requesters, grouped by owner, with a reminder email to each.

Steps Schedule → sample requests → switch by role → group per person → merge → loop and send HTML emails

Email seen

Marketing and sales

Customer Visiting – AI Overdue Trip Document Reminder

Schedule , Daily, 09:00 Email + SQL Server 7 nodes

Reminds trip owners back for 7+ days without documents or budget, and logs each send alongside Customer Visiting so it never repeats.

Steps 9 am schedule → trips missing documents → loop → build email → send → write reminder log

Email seen

TradeMark Lifecycle Management

Schedule , 1st of each month Email 15 nodes

Checks trademarks due for verification or nearing expiry and emails a summary with two Excel files.

Steps Monthly schedule → trademarks → two branches (verification / expiry) → compute and sort → Excel → merge → email

Customer Expiry Pilot (MK)

Schedule Email 11 nodes

Checks customer permits and certificates in Google Sheets, emails when they near expiry, and writes the status back to the sheet.

Steps Schedule → read Google Sheets → check expiry → group by recipient → send email → update the sheet row

SaleTracking Customer (Ari Ari)

Schedule Email 6 nodes

Finds customers with no order for 60+ days and emails the sales team a follow-up list.

Steps Schedule → customer sales → days since last order → keep 60+ days → email

Production planning

180-Day Packaging Mobility Monitor Service

Schedule , 1st of each month Email 9 nodes

Finds packaging with no movement for 180+ days in the ERP, totals its value and emails it with an Excel file.

Steps Monthly schedule → stock via API → split items → keep 180+ idle days → sort by idle days → Excel → HTML email

IT and data

Real-time Production Notification System

Webhook from another system SQL Server 12 nodes

Receives real-time production-line events, formats the notification, and writes it into the production dashboard’s notification feed (previously sent to Telegram).

Steps Webhook → factory and line lookup → shape data → message template → production summary → insert into the dashboard notification table

XRayDriveSentinel Alert

Webhook from another system Email 3 nodes

Receives a webhook from XRay Drive Sentinel when an X-ray folder is missing or a disk is filling up, and sends the alert email.

Steps Webhook (POST) → send the HTML email built by the Python service

Send Content Image To Telegram Automation

Schedule Telegram 10 nodes

Sends the Think with AI infographics to staff on Telegram from a Google Sheets schedule, then marks them as sent.

Steps Schedule → content plan (Google Sheets) → download image from Google Drive → chat IDs → send photo on Telegram → update the sheet