Real-time Vtiger support tickets to Telegram with auto status updates
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (every minute). Along the way it connects Telegram and Vtiger Crm (community).
How it runs
Trigger: On a schedule (every minute).
- VtigerCRM get Tickets (Vtiger Node): uses Vtiger Node
- If: checks a condition and branches into true / false
- Send a Ticket detail to Telegram (Telegram): uses Telegram
- VtigerCRM Update Ticket Status (Vtiger Node): update
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-vtiger-crm is verified or supports 3.0 (used in VtigerCRM get Tickets, VtigerCRM Update Ticket Status).
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Vtiger Node
n8n-nodes-vtiger-crm.vtigerNode - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - No Operation, do nothing
n8n-nodes-base.noOp
From the author
⚠️ This Workflow Requires a Community Node and a Self-Hosted n8n Instance > This workflow uses the Vtiger CRM community node. To use it, you must be running a self-hosted version of n8n with Community Nodes enabled. 🔧 How to Install the Node 1. Go to…