n8n EV Charger Fault Diagnosis Workflow (OpenAI + Telegram)

Detect new EV charger faults and notify technicians—with optional automatic refunds

This n8n EV Charger Fault Diagnosis Workflow polls your charging network every 15 minutes, detects newly faulted stations by comparing live status against a stored baseline, uses OpenAI to generate a manufacturer-style fault diagnosis, and sends Telegram alerts. If a fault occurs during an active charging session, it can also trigger an automatic refund via your payment processor API.

What this workflow does

• Runs on a schedule every 15 minutes using a scheduled trigger.
• Fetches current charging station status from your charging network HTTP API.
• Reads the previous baseline from an n8n Data Table (matched by stationId).
• Detects only new faults by comparing the latest fault code to the stored baseline.
• Diagnoses the fault using an OpenAI-powered agent that references a manufacturer fault-code reference API to produce a brief diagnosis and recommended technician action.
• Routes alerts to technicians via Telegram, including the generated diagnosis.
• Triggers a refund when appropriate: if the station has one or more active charging sessions, the workflow sends a refund request to the payment processor API; if there’s no active session, it skips the refund.
• Updates the baseline by upserting each station’s latest status, fault code, and session count into the n8n Data Table for the next poll.

Use cases

• EV charging operators who want faster response to newly reported charger failures.
• SaaS teams managing fleet health dashboards and needing automated incident triage.
• Automation engineers building reliable maintenance workflows with audit-friendly state tracking in n8n.

Technical details

• n8n Data Table for baseline storage and upsert logic (configurable Data Table ID).
• HTTP API polling for charging station status.
• OpenAI agent using a manufacturer fault-code reference API.
• Telegram node for technician alerts.
• Refund routing via payment processor API when active sessions exist.
• Core workflow nodes: if, set, code, merge, telegram, data table.