Skip to content

Fix Telegram isConnected to require webhook_secret #6259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
noanflaherty merged 1 commit into from
Feb 21, 2026
Merged

Fix Telegram isConnected to require webhook_secret #6259

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion assistant/src/messaging/providers/telegram-bot/adapter.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,13 @@ export const telegramBotMessagingProvider: MessagingProvider = {
* credential:telegram:access_token, but the Telegram bot token is
* stored as credential:telegram:bot_token. This method lets the
* registry detect that Telegram credentials exist.
*
* Both bot_token and webhook_secret are required — the gateway's
* /deliver/telegram endpoint rejects requests without the webhook
* secret, so partial credentials would cause every send to fail.
*/
isConnected(): boolean {
return getBotToken() !== undefined;
return getBotToken() !== undefined && !!getSecureKey('credential:telegram:webhook_secret');
},

async testConnection(_token: string): Promise<ConnectionInfo> {
Expand Down
Loading