Hi
I’m experiencing a critical issue on n8n Cloud where I’m unable to update my Telegram Bot credentials, which prevents me from using any Telegram-related workflows.
The Problem:
When I try to set up a Telegram node, I enter the API token for my new bot in the credentials section. The interface confirms that the credential has been saved successfully.
However, the moment I close and reopen the credential settings, the API token field has reverted back to an old token from a completely different bot that I used long ago. No matter how many times I try to save the new token, the old one reappears.
This makes it impossible to connect to the correct Telegram bot, and all my workflows are failing.
Troubleshooting Steps I’ve Already Taken:
Complete Deletion: I have navigated to the “Credentials” section and deleted all existing Telegram API credentials to start from a clean slate. The issue still occurs when creating a brand new credential.
Browser Independent: I have tried this process in multiple different browsers (including incognito/private modes) to ensure there is no client-side caching issue. The problem is consistent across all of them.
Platform: I am using the official n8n Cloud service, so I should be on the latest stable version of n8n.
It seems to be a server-side bug where my account is stuck with an old, cached credential that cannot be overwritten. This has completely blocked my development.
Could someone from the team please investigate this?
Thank you for your help.
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system: