Facebook chatbot retriggering

Help me Build my Workflow
1

Hello there!

I’m building a Facebook Messenger chatbot using n8n with a webhook. The issue I’m facing is that the webhook keeps retriggering, which causes my bot to repeatedly send the same message (spamming in production).

Here is what’s happening:

  • The webhook verification with GET works correctly.

  • When I receive a POST event from Facebook, my workflow processes it, but the same event gets triggered again and again.

  • As a result, the bot keeps sending the same message multiple times in an infinite loop.

I suspect something is wrong with how my POST webhook response or filtering is set up, but I’m not sure where the issue is.

I am on version 1.112.4

Képernyőfotó 2025-09-30 - 13.11.19
Képernyőfotó 2025-09-30 - 13.11.19881×565 59.6 KB

Thank you for your help!

2 Me gusta
2

Same here ! Can’t figure out what’s happening!

3

Hello @Levente_Toth ,

I debugged your workflow very carefully and try to identify the issue but because of less details and also i don’t have the execution logs so that i can debug the flow very deeply,so i can give you few reasons that may solve your issue :-

1.Ensure Webhook Acknowledgment :- The Webhook Node must return a proper HTTP response (200 OK) with an acknowledgment after processing the event.

2.Avoid Circular Processing :- Ensure that the AI Agent Node or HTTP Request Node does not trigger the Webhook Node again inadvertently. Implement checks to avoid reprocessing the same data.

3.Use Unique Identifiers :- If the same event is processed multiple times, use a unique identifier (e.g., message ID) to check and prevent duplicates.

4

Hello Kenil!

Thank you for your reply!

I found a fairly easy workaround to the problem!

I simply put a ‘response to webhook’ node after the ‘webhook’ node, so it gets back an instant 200 OK response. I have tried put it after the ‘HTTP Request’ node aswell, but it did not worked that way.

However this way works perfectly!

Képernyőfotó 2025-10-02 - 12.54.37
Képernyőfotó 2025-10-02 - 12.54.37504×217 19.6 KB

1 me gusta
5

I’m glad to hear that your problem has been resolved. Wishing you continued growth and success ahead.

6

i am facing the same issu, can you please tell me how you solve it. What you write in Respond to Webhook1, please help me

7

Hey!

Simply pick the ‘no data’ and optionally a 200 response code.

I hope it helps​:raising_hands:t2:

IMG_5484
IMG_54841179×1457 123 KB

8

This solution worked for you? And @Levente_Toth My workflow still runs infinitely.

Screenshot_14
Screenshot_14585×491 35.6 KB

9

Hey!

yes with this setup, it works for me! What is your set up in the respond to webhook node?

10

Hi There!
I was facing the same issue and here is hte solution here’s what I found and how I fixed it.

The Problem

  • Webhook keeps firing repeatedly

  • Bot sends same message in infinite loop

  • Works in test, breaks in production

Root Causes

  1. No instant 200 OK response → Facebook retries the webhook

  2. Echo messages → Bot receives its own sent messages back

  3. Read/Delivery receipts → Non-message events trigger the workflow

The Solution

Step 1: Add “Respond to Webhook” node immediately after Webhook

  • Respond With: No Data

  • Response Code: 200

  • :warning: Set Webhook node → Response Mode: Using 'Respond to Webhook' Node

Step 2: Add IF node with these conditions (AND):

Condition Expression Operator
Not an echo {{ $json.body.entry[0].messaging[0].sender.id }} is not equal to {{ $json.body.entry[0].messaging[0].recipient.id }}
Message exists {{ $json.body.entry[0].messaging[0].message }} exists
Text exists {{ $json.body.entry[0].messaging[0].message.text }} exists

Why This Works

  • sender.id ≠ recipient.id → Filters out echo messages (works for multiple pages!)

  • message exists → Filters out read receipts, delivery receipts

  • message.text exists → Ensures actual text message is present

:wrench: Final Workflow Structure

Webhook
    ↓
Respond to Webhook (200 OK) ← Immediate!
    ↓
IF Node (3 conditions above)
    ↓
True → Continue processing
False → Stop

Hope this helps someone! :raising_hands:

image
image819×645 36.4 KB

image
image865×863 33.8 KB

11

¡Muchas muchas gracias, tío!!!..No puedo expresar lo frustrado que estaba antes de encontrar esto…construí todo el sistema para mi cliente pero me quedé atrapado en este problema durante 3-4 días. He probado de muchas formas pero fallé…finalmente obtuve tu solución y la probé…¡¿Adivina qué???..¡Funcionó!..No puedo expresar lo agradecido que estoy contigo ahora..gracias tío gracias…

este es mi perfil de LinkedIn: www.linkedin.com/in/md-shajedur-rahman-sadik-08774922a

sería un gran placer para mí si nos conectamos. Por favor, envíame una solicitud de conexión

12

(publicación eliminada por el autor)