Triggered twice with old data on webhok

[Frederik_Nielsen]

Describe the problem/error/question

We’re seeing the same webhook event being triggered twice. Here’s an example execution:

Our n8n workflow has executed two times, and it was triggered again on Saturday, Feb 15, but with the same test payload that was originally sent earlier in the week. In the payload timestamp, it explicitly shows:

created: 2026-02-10T12:29:13Z

Has anyone experienced something like this before, or knows why this could happen?

I’ve spoken with Ortto (the system sending the event to our webhook), and they claim they only sent it once—on the original created date Feb 10. So it seems like the cause is somewhere in n8n (or in our setup around it).

What should I look for from here?

Sincerely
Frederik

[barn4k]

hello @Frederik_Nielsen

Are you sure that your workflow sends a correct answer to the webhook event?

Usually, the source system resends the webhook event when it doesn’t have a proper response to the collected webhook event.

You can remove duplicates with the Remove Duplicates node or by storing the webhook payload in the Data Table and comparing the next webhook event with the one in the data table.

[Frederik_Nielsen]

hmm. I’m not sure.

This is my workflow.

So I have a webhook coming from a standard formular on our page.
In the end of our workflow it creates and sent an email.

That email keeps on being sent, again and again. like it keeps being executed, ones every day at the same time.

I’m sorry for not being a developer, som im a bit lost

[barn4k]

how the Webhook node configured to respond? On the last node or immediately?

Can you also show how it looks with an execution (e.g., the last one from the executions tab)?

[Frederik_Nielsen]

This is my first webhook:

If true it goes to finish execution and if fails it goes to this:

When the execution is done it looks like this in the last node:

So this execution we didnt do ourself. It’s something that keeps being triggered every day somehow.

[barn4k]

As far as I see, you have configured the webhook to send a response with the “Using Respond to Webhook Node” option; however, your workflow design doesn’t contain that node for the True branch of the Secret key IF node. Moreover, both branches might output two results sequentially, as you are splitting the execution into two in the ending section:

Use the Merge node on the ending part (numbers 1 and 2 on the screen), with the option Choose Branch >> A single empty item, to merge the branches, then add a response to the webhook node with something like code 200.