US facilities-services company
Work-order automation
delivered · running unattended
A facilities-services company received work orders from a client platform by email, and re-typed every one of them into their field-service system. The pipeline that replaced this is small, boring, and exactly the point: it has one job and it does it every time.
The starting point
- Every work order manually re-entered: slow, error-prone, and entirely dependent on someone being at a desk.
- The target system accepts only a strict 28-column, semicolon-delimited, ISO-8859-1-encoded CSV via FTPS: a format built for machines, filled in by humans.
- Work-order emailsIMAP watch on the inbox
- Parseplatform email → structured order
- Format28-col · semicolon · ISO-8859-1
- DeliverFTPS upload
- Verifypoll success/error folders
- Field-service systemorders arrive machine-perfect
- Audit logevery order in a sheet
- Dashboardtechnician performance (Next.js)
What got built
Ingestion pipeline
An email trigger watches the work-order inbox, parses each platform email, generates the exact 28-column CSV the field-service system requires, uploads via FTPS, polls the success/error folders to confirm processing, and logs every order to a sheet the team can audit.
Technician performance dashboard
A Next.js dashboard on top of their operations: technician metrics, incidents, attendance, with an admin panel for the office team.
Run, not just shipped
This is the client behind the testimonial on the homepage: the engagement that ends with “I will be hiring Tim again.”
Stack
- n8n (self-hosted)
- IMAP email parsing
- FTPS integration
- Google Sheets logging
- Next.js dashboard
Got a system like this waiting to exist?
Start with the free teardown: I’ll map your three biggest automation leaks and what they cost you monthly. In your inbox within 72 hours.
Get your free systems teardown