How can I run two Telegram-trigger workflows concurrently in n8n using different bot tokens?

Below is an explanation and a couple of workarounds that can help you use both workflows concurrently.

What’s Happening

Each Telegram trigger node registers a webhook using the Telegram Bot API. Because Telegram only allows one registered webhook per bot, when both workflows are active, the most recently activated one “wins” the registration. Although you’re using different bot tokens (and thus different bots), if your instance isn’t properly reachable via a secure, public URL, Telegram may not be able to register each webhook correctly. This usually happens when the instance isn’t served over HTTPS or when the reverse proxy isn’t set up to handle websocket connections, which both can cause issues with Telegram’s webhook configuration.

How to Solve It

1. Configure HTTPS via Your Reverse Proxy:

   When self-hosting with Docker Compose, you need to make sure your n8n instance is accessible via a public HTTPS address. To achieve this:

   • TLS/SSL Termination:
     Set up TLS/SSL termination in your reverse proxy (e.g. Nginx, Traefik, Apache).

   • Set the WEBHOOK_URL:
     Update the WEBHOOK_URL environment variable in your Docker Compose configuration so that it points to your public HTTPS URL. For example:

     YAMLCopied
     environment:
       - WEBHOOK_URL=https://your-public-domain.com/

   This ensures that n8n passes a proper HTTPS URL to Telegram when registering each webhook, allowing both bots to work correctly.

2. Ensure Reverse Proxy Websocket Support:

   Telegram’s webhook mechanism benefits from proper websocket proxying. Verify your reverse proxy configuration includes support for websockets. For example, if you are using Nginx, your configuration should include:

   NGINXCopied
   location / {
       proxy_pass         http://n8n:5678;
       proxy_http_version 1.1;
       proxy_set_header   Upgrade $http_upgrade;
       proxy_set_header   Connection "upgrade";
       proxy_set_header   Host $host;
   }

Additional Considerations

• Different Bots:
  Since you’re using two different bot tokens (and thus two separate bots), Telegram will accept one webhook per bot provided the webhook URL is reachable (i.e. HTTPS is properly set up). Once your instance is correctly accessible, both bots should be able to register and trigger their respective workflows at the same time.

• Testing vs. Production:
  Some documentation for trigger nodes notes that switching between testing and production endpoints can cause the webhook registration to update. For concurrent usage, ensure that both workflows are configured to use production (or both to use test) so that Telegram doesn’t override one webhook with the other.

Final Steps

1. Update your reverse proxy configuration to support websockets and TLS/SSL.
2. Set the WEBHOOK_URL environment variable in your Docker Compose file to a valid HTTPS URL.
3. Restart your n8n instance so that both Telegram bots can register their webhooks correctly.
4. Verify that each workflow’s trigger is working by sending a message to each respective Telegram bot.

With these adjustments, your two workflows using different Telegram bots should be able to be active and trigger concurrently.