ettix

Ettix guides · Workflow testing

How to test n8n webhook retries before launch

If a webhook arrives twice, will your workflow create two CRM records? If an older update arrives late, can it overwrite a newer status?

Download sample events (JSON)

Set up a safe test

Clone your workflow in a test n8n instance and point it at a test CRM or database. Activate the test copy and use its webhook URL so it can accept repeated and concurrent requests. Use synthetic data and reset the test records before each scenario.

The file contains individual payloads under events. Send the named payload for each step as a JSON request body to your staging webhook. Use the same payload, including its event ID, when repeating an event.

Run the five scenarios

  1. Sequential duplicate. Send orderCreated twice, waiting for the first run to finish. Expect one CRM record.
  2. Concurrent duplicate. Send two copies of orderCreated at the same time. Expect one CRM record.
  3. Out-of-order delivery. Send orderCreated, orderPaid, then olderUpdate. The last event has a different ID and an older version. Expect the status to stay paid.
  4. Temporary destination failure. Send orderCreated and have the test destination return HTTP 503 before saving the first create. Let the workflow retry. Expect one saved record.
  5. Distinct events. Send orderCreated and anotherOrder. Expect two CRM records.

Check what actually got saved

Check the saved records and their final values after each run. A successful webhook response only confirms what the endpoint returned.

Ettix counts guide requests and sample-file downloads on its server. This guide uses no tracking cookies.

Run the checks with RetryLab

Try the demo or run the sequential duplicate check from your computer. Unlock all five scenarios and shareable reports for $39 per project.

Open RetryLab