My Telegram trigger does not fire in test mode. After enabling the workflow I see the executions coming in, but while listening to test events it does not fire the trigger.
@Martin_Neumann, this is happening due to you only being able to register 1 webhook onto your telegram bot. Due to you registering only the production webhook it only triggers, whenever you run your workflow in production not in testing.
So should the trigger run in test mode if I am switching off the execution of the workflow? Then there would be no other trigger registered. Also, there is a warning that only one trigger will work, but not about those details in testing the trigger.
The warning can be confusing, but since only one webhook can be active at a time, you could try temporarily disabling the production webhook while testing, or use a different bot for testing. This way, both the production and test environments can run without any issues.
I just tried and even disabling the workflow did not get the test step to work. Would be nice if there was a way to run a trigger test for development. And I think the warning message should also include some note reflecting the situation about trigger testing.
@Martin_Neumann, you must also register the testing webhook. Because Telegram only allows there to be 1 webhook registered at the time. Meaning when you want to test your workflow, you should first register the testing webhook before running the test. And when you want the workflow to run continuously, you register the production webhook. Here’s a small tutorial on how to register a webhook for a Telegram bot. Setting your Telegram Bot WebHook the easy way | by Paolo Montalto | Medium
Well I tried to look up the webhooks that are getting set by calling the /getWebhookInfo endpoint. When activating the webhook, the link is being set correctly and working. When I activate the webhook test, it actually changes to the /webhook-test path, but the DNS name is not changing from the trigger URL to the editor URL. I tried to fix that manually, but still no success in receiving any data. Seems there is something buggy in the Telegram trigger node that does not allow to run it in test mode. Do you have a recent n8n version to run a quick test on that and see if this error persists?