Telegram Trigger not working in Test Execution
tanvir
HOBBYOP

8 months ago

I’m running n8n on Railway using the N8N (w/ webhook processors) template. Everything is deployed properly and running.

The Issue

Active mode → Telegram Trigger works fine. Bot messages reach n8n and trigger executions.

Test Execution mode → Workflow just stays in “Listening…” and never receives Telegram messages.

In the UI I see:

Test URL points to the Primary (custom domain):

  • https://<custom-domain>/webhook-test/<workflowId>/webhook

Production URL points to the Webhook Processor (Railway domain):

This mismatch means Active works (through processor) but Test never fires (because it’s pointed at Primary).

What I’ve Tried

  • Added these env vars to both Primary and Webhook Processor:

    • N8N_WEBHOOK_URL=https://<custom-domain>

    • N8N_WEBHOOK_TUNNEL_URL=https://<custom-domain>

  • Cleared Telegram webhook with deleteWebhook and re-registered.

  • Verified with getWebhookInfo: in Active mode it shows the /webhook/... URL. In Test mode, even though /webhook-test/... appears in n8n, Telegram never sends messages there.

  • Hitting the test URL directly in a browser returns:

    • {"code":404,"message":"This webhook is not registered for GET requests. Did you mean to make a POST request?"}

How can I fix this issue?

$10 Bounty

2 Replies

Railway
BOT

8 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


Anonymous
FREE

3 months ago

hi tanvir, have you figured this out? if so, can you post back with the fix? I'm having similar issues with the sample template. Thank you!


Welcome!

Sign in to your Railway account to join the conversation.

Loading...