Triage elevator callbacks and compliance alerts with OpenAI, Telegram, and Gmail
Ready for 3.0What this workflow does
This AI workflow has 15 nodes and runs on a schedule (every day). Along the way it connects OpenAI Chat Model, Telegram and Gmail.
How it runs
Trigger: On a schedule (every day).
- Fetch Current Elevator Status (HTTP Request): calls an HTTP API
- Read Prior Elevator State (Data table): uses Data table
- Tag Current Snapshot (Edit Fields (Set)): sets or maps fields
- Tag Prior Snapshot (Edit Fields (Set)): sets or maps fields
- Combine Current & Prior Snapshots (Merge): merges the data from its input branches
- Diff Elevator State & Detect New Events (Code): runs custom JavaScript code
- Extract Callback Fault Details (Information Extractor): extracts structured fields from text with AI, with model: OpenAI Chat Model
- Shape Watchdog Event Record (Edit Fields (Set)): sets or maps fields
- Entrapment - Urgent? (If): checks a condition and branches into true / false
- Certificate Expiring Soon? (If): checks a condition and branches into true / false
…plus 3 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 (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Data table
n8n-nodes-base.dataTable - Code
n8n-nodes-base.code - Information Extractor
@n8n/n8n-nodes-langchain.informationExtractor - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow polls an elevator monitoring API every 30 minutes, compares the latest unit status to a saved prior snapshot in an n8n Data Table, uses OpenAI to extract structured fault details from technician notes, and sends Telegram and Gmail…