<Got it 
Massimo.
Here’s a clean, professional problem report in English you can copy-paste directly into the n8n community forum:
⸻
Issue Description
We are experiencing persistent issues with our n8n workflow that involves Telegram Trigger and Send Message nodes.
• The workflow is active and saved correctly.
• The Telegram bot is connected with a valid token.
• When we type commands/messages into the Telegram bot (e.g., /start), no response is sent back and no execution appears in the n8n editor.
• The Send Message node works only when tested manually, but it doesn’t get triggered automatically when a message is received on Telegram.
Steps Already Taken
1. Verified that the Telegram credentials are valid (tested via getMe API call).
2. Checked the Chat ID and Text fields in the Send Message node (set via expressions).
3. Ensured the workflow is active (green status in the editor).
4. Restarted the workspace several times and even changed the timezone setting.
5. Updated n8n from 1.108.2 to 1.109.2 (Latest Stable), but the problem persists.
6. Tried disabling Simple Memory node (we saw related errors before), but issue remains.
Error Behavior
• No error is displayed in the execution log.
• The Telegram Trigger node does not fire when messages are sent to the bot.
• Only direct manual execution of Send Message works.
Environment
• n8n version: 1.109.2 (Latest Stable)
• Deployment: C
blob:WhatsApp Web (Starter plan)
• Nodes involved: Telegram Trigger, AI Agent, Send Message
Question
blob:WhatsApp Web
What could prevent the Telegram Trigger node from firing, even though the bot is valid and workflow is active?
Is there a known issue with Telegram triggers in v1.109.2, or could this be related to webhook configuration / n8n Cloud setup
