Multiple Triggers as Inputs: does not work

Hi there,

I have a simple issue: I want multiple inputs for my RAG chatbot. Specifically: one via the N8N chat module, one automated once a week (to keep the database active), and one via WhatsApp when a message arrives.

The problem is that it doesn’t work as intended. When I click on “Chat” within the workflow, it should only respond within the chat and not return a message to WhatsApp. If I remove the WhatsApp path entirely, the chat works perfectly fine. However, once the WhatsApp path is added, I receive the error: “This WhatsApp number already has a webhook subscription.”

I don’t think the issue is the webhook subscription itself, as this workflow is the actual subscription. What I want is to have these inputs working in parallel.

1 Like

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:
  • n8n version: 1.69.2
  • Database (default: SQLite): QLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): self-hosted in google cloud
  • Operating system: Windows10

Hey @Kiremit

Try using a “Switch” instead of the “If” node.

In a Chat execution, the output data of the last node in the “branch” is returned to the user - it doesn’t necessarily have to be the agent node! A switch node is perfect for both redirecting for whatsapp and acting as the “last node” for n8n chat.

1 Like

Hi @Jim_Le ,

thanks. It still throws me a bunch of errors.

When I click on WhatsApp Trigger manually it tells me that my wabasid is already subscribed to a workflow even though this is the only active one with that number.

Clicking on Chat it tells me that the reference node is unexecuted and in general it wont reply on whtsapp - switch node does not seem to work the way its supposed to.

Screenshot 2025-01-19 145432
Screenshot 2025-01-19 145406

Hey @Kiremit

Apologies for the late reply.

Hmm yeah the thing is in “editor mode” the workflow will run a little differently which may be why you’re seeing the “reference node not executed” error. Simplifing here but in this mode, the agent node will check all incoming connections are resolved of which you have 3. In “production mode”, this doesn’t happen - it runs as you expect, when you run chat, only that branch is active and the rest ignored.

To use chat then in “editor mode”, you’ll have to temporarily snip the other 2 connections and reconnect them when you’re done. Not ideal I know. The simple workaround is to just split the incoming triggers into their own templates - there is duplication for sure so it really is just preference.

Regarding your WhatsApp error, I don’t think I can provide much assistance other than to maybe look at what subscription the whatsApp ID is bound to (from the dashboard) and if it matches?

Best of luck!

1 Like

@Jim_Le Yeah I am now only using Whatsapp - does not seem to work with 3 inputs.