Manage fleet compliance and driver renewals with Sheets, OpenAI and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 28 nodes and runs on a schedule (cron 0 7 * * *) (plus 1 other trigger). Along the way it connects Google Sheets, OpenAI, Slack and ClickUp and 2 more.
How it runs
Trigger: On a schedule (cron 0 7 * * *) (plus 1 other trigger).
- Read Fleet Register (Google Sheets): uses Google Sheets
- Look Up Driver Vehicle (Google Sheets): uses Google Sheets
- Read Alert Log (Google Sheets): uses Google Sheets
- Accept Only Driver Photos (Code): runs custom JavaScript code
- Evaluate Document Expiry & Dedupe (Code): runs custom JavaScript code
- Download Document Photo (Telegram): work with file
- Check Pending e-Challans (HTTP Request): calls an HTTP API (POST)
- AI Read Document Photo (OpenAI): analyze (image)
- Score Risk & Dispatch Gate (Code): runs custom JavaScript code
- Validate Document Details (Code): runs custom JavaScript code
…plus 16 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 - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - OpenAI
@n8n/n8n-nodes-langchain.openAi - Slack
n8n-nodes-base.slack - ClickUp
n8n-nodes-base.clickUp - Gmail
n8n-nodes-base.gmail - Telegram
n8n-nodes-base.telegram - Telegram Trigger
n8n-nodes-base.telegramTrigger
From the author
Quick overview This workflow runs a daily compliance scan from Google Sheets, checks each vehicle’s document expiries and pending e-challans via an HTTP API, then uses OpenAI to message drivers on Telegram, create renewal tasks in ClickUp, notify ops in…