# Webhook executing the workflow many times on 1 request

**URL:** <https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322>\
**Category:** Questions\
**Tags:** data-transformation, node\
**Created:** [2023年十二月18日 16:43 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322 "2023-12-18T16:43:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nazih\_Saba](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/nazih_saba/32/27606_2.png) [@Nazih\_Saba](https://community.n8n.io/u/Nazih_Saba)\
**Post date:** [2023年十二月18日 16:43 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/1 "2023-12-18T16:43:09Z")

</div>

## Describe the problem/error/question

Hello guys,  
Im using a webhook node. When I send the request to it (Production or test) it receives the body twice or 3 times on 1 click.  
How can I fix it so that It receives the data only once?

## What is the error message (if any)?

## Please share your workflow

```auto
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

```

## Share the output returned by the last node

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/f/b/fbf2e2ca4341610507ef63ed862ef60774c902ec.png)

## Information on your n8n setup

- **n8n version:** 1.21.0
- **Database (default: SQLite):** SQLite
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** Docker
- **Operating system:**

---

<div class="post-metadata">

**Author:** ![ihortom](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ihortom/32/11473_2.png) [@ihortom](https://community.n8n.io/u/ihortom)\
**Post date:** [2023年十二月19日 01:51 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/2 "2023-12-19T01:51:38Z")

</div>

@Nazih_Saba , I wonder if the service that sends the request to your webhook expects some specific response. As it does not get it, it might be re-sending the request assuming the webhook did not receive it.

---

<div class="post-metadata">

**Author:** ![netroy](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/netroy/32/22154_2.png) [@netroy](https://community.n8n.io/u/netroy)\
**Post date:** [2023年十二月19日 12:39 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/3 "2023-12-19T12:39:06Z")

</div>

@Nazih_Saba If you refresh the frontend, can you still reproduce the issue?  
I’m wondering if this is an issue of the frontend listening to backend messages multiple times.

---

<div class="post-metadata">

**Author:** ![Nazih\_Saba](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/nazih_saba/32/27606_2.png) [@Nazih\_Saba](https://community.n8n.io/u/Nazih_Saba)\
**Post date:** [2023年十二月19日 12:52 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/4 "2023-12-19T12:52:46Z")

</div>

I think that was the issue. I modified the webhook to send response immediately, and so far the problem did not appear.

---

<div class="post-metadata">

**Author:** ![Nazih\_Saba](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/nazih_saba/32/27606_2.png) [@Nazih\_Saba](https://community.n8n.io/u/Nazih_Saba)\
**Post date:** [2023年十二月19日 12:53 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/5 "2023-12-19T12:53:43Z")

</div>

I thought the issue was with the frontend. But My worfklow posts data at specific places, and It was posting them multiple times on 1 click.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [2024年三月18日 12:54 UTC](https://community.n8n.io/t/webhook-executing-the-workflow-many-times-on-1-request/34322/6 "2024-03-18T12:54:40Z")

</div>

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