Telegram Callback Query is not working with Restrict to Chat IDs field

I’m experimenting with Telegram workflow where a bot sends the user an message with 2 buttons each month, and the user can decide which flow to trigger this month.

I have a problem with the Telegram Trigger node. When it gets a message I can restrict the node to a specific Chat ID, but when I want the flow to trigger on a Callback Query, the restrict to Chat IDs field prevents the node from catching anything. When I remove the restriction, the trigger works, and when I set the trigger to catch messages, the restrict to Chat IDs filter also works. They just don’t work combined as far as I can tell.

Yep… self-hosted version 1.113 same behavior.

Therefoore, it is posible that this is is either a limitation or a bug in the implemenntation…

Handling the chat ID restriction within workflow logic after the trigger fires, as a workaround… An IF or FILTER node to harcode mi id s