Telegram Trigger — “Provided secret is not valid” error (WebApp / webhook mode only)

Questions
, , ,
1

:puzzle_piece: Title:
Telegram Trigger — “Provided secret is not valid” even after resetting webhook and secret
Describe the problem/error/question
I’m getting a
{“message”:“Provided secret is not valid”}
error whenever testing the Telegram Trigger node.
Even after deleting the webhook, resetting N8N_TELEGRAM_SECRET, and recreating the webhook, n8n keeps rejecting it.
I’ve tried both:
Letting n8n register the webhook automatically via “Listen for Test Event”.
Manually setting the webhook using Telegram API with a secret_token.
Both return the same result.
What is the error message (if any)?
{“message”:“Provided secret is not valid”}
Please share your workflow
(Just a single Telegram Trigger node — standard setup.)
Information on your n8n setup
n8n version: 1.114.4
Database: SQLite (default)
n8n EXECUTIONS_PROCESS: own
Running via: PM2 + Cloudflare Tunnel (local Mac setup)
Operating system: macOS
Environment variables:
N8N_ENCRYPTION_KEY=***********
WEBHOOK_URL=https://n8n.example-domain.nl
N8N_TELEGRAM_SECRET=***********
:white_check_mark: Additional notes:
Cleared both settings and webhook_entity tables in the SQLite DB.
Restarted n8n with --update-env.
Tried generating multiple new secrets — no effect.
It seems n8n still expects a different internal secret than the one defined in environment variables.
No option exists in the Telegram Trigger node to remove or reset the stored secret.
This issue only happens when using the Telegram WebApp / webhook mode —
regular message-based triggers (e.g., text messages, commands) work fine without errors.
Would really appreciate any insights or confirmed fixes from anyone who faced this.
Tagging @n8n-team and @MutedJam — maybe you’ve seen this behavior with the Telegram WebApp integration?

2

@HamidJavaheri19Sometimes when you copy provided secret then copy the extra space gets added maybe that’s what’s causing the issue. Please check it.

3

@Ahmad_Hassam thanks but the credential is in normal status (green) and text message and inline callbacks work through this api. the problem is related to receive webapp message in mini app