Classify FRA track defects, route tag-out approvals, and archive records with OpenAI, Slack, and Google Drive
Ready for 3.0What this workflow does
This AI workflow has 19 nodes and runs on a schedule (every day at 05:00). Along the way it connects OpenAI Chat Model, Slack and Google Drive.
How it runs
Trigger: On a schedule (every day at 05:00).
- Normalize Poll Window (Edit Fields (Set)): sets or maps fields
- Fetch Segments Due & Inspector Notes (HTTP Request): calls an HTTP API (GET)
- Classify Defect Severity (Text Classifier): classifies text into categories with AI, with model: Classifier Model
- Tag No Defect (Edit Fields (Set)): sets or maps fields
- Tag Minor (Edit Fields (Set)): sets or maps fields
- Tag Serious (Edit Fields (Set)): sets or maps fields
- Tag Immediate Halt (Edit Fields (Set)): sets or maps fields
- Compute FRA Speed Restriction & Remedial Timeframe (Code): runs custom JavaScript code
- Requires Immediate Tag-Out? (If): checks a condition and branches into true / false
- Request Supervisor Tag-Out Approval (Slack): send and wait for a reply (message)
…plus 7 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Text Classifier
@n8n/n8n-nodes-langchain.textClassifier - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Switch
n8n-nodes-base.switch - Google Drive
n8n-nodes-base.googleDrive
From the author
Quick overview This workflow automates daily railway track safety management by integrating defect classification, risk calculations, and communication. It uses OpenAI to categorize inspector notes by FRA severity, determines speed restrictions, and…