2 active telegram workflows

I have 2 workflows. Each workflow starts with a telegram trigger on message received. Each trigger is connected to a different bot (different token).

If one workflow is active, it works as it should.

When activate the second workflow, it doesn’t trigger, until I disable the first one. So only one works in the same time.

I think this is because I haven’t set a webhook in telegram.

How should I solve this, to activate and use both in the same time?

Additional info: I’m selfhosted on digital cloud, using docker compose. n8n version 1.78.0

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

hello @Rabih_Badr

You should set the webhook during the bot registering process via botfather. If you have 2 bots, then you’ll need two different webhooks. Their address you can see in the trigger nodes

Hi,

How do I set the webhook?

It will be set automatically within the trigger node. However, you can check if it was set correctly with the HTTP Request node and your bot token. Change the url part <your_bot_token> with actual token

Thank you for the instruction.

I checked both my telegram bots. One has a webhook url, the second doesn’t.


On my n8n side, the telegram trigger has a test webhook (it’s greyed out, and can’t be changed)

what should I do?

post a webhook request to assign that webhook to the agent without it?
or
switch to production and assign it to both?

Edit: Can 2 telegram agents in 2 separate workflows simultaneously use the same webhook.

You can see the production url by clicking on the Production URL button

What is the output of the HTTP node for both bots if you enable both workflows with the Telegram triggers?

I’ve tested on my self-hosted instance and there were no issues.

Both workflows are active now.

Both requests are returning the same webhook above.

However, now my agent 1 workflow is not triggering. Agent 2 (the one that I just activated) is triggering.

That should not happen.

Does the Production URL link for both of the telegram trigger nodes is the same?

Remove one trigger node and replace it with the new one from the nodes panel (not via copying the old trigger)

2 Likes

Yeah that was it!

I copied the node to my other workflow, yeah, and it retained the webhook.

I made a new trigger, and it got a new hook.

Thank you for your guidance barn4k

cheers,

1 Like

If the issue was resolved, please mark my post as a solution by clicking on the little checkbox below the post so others can see the solution as well.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.