n8n stress testing

CrashLabs

Catch double emails and double charges before production. No signup to see a live FAIL.

See a live FAIL reportStress your workflow

Demo is free · your own run needs a free credit after signup

What a FAIL looks like

Sample invoice webhook · preview of the before/after live demo

Before / after live demo

Deploy gate

Fail

Not production-ready yet

No duplicate guard. A retried webhook would invoice and email the same customer again — Crash Labs proved it in a fake company.

Risk

88/100

Blast radius · Northwind Ops (simulated)

If production retried this 50×, Northwind Ops would spam the same customer 43 times.

50 trigger fires into one fake company. No real Stripe. No real Gmail.

43

emails out

Emails
43
Invoices
43
Stripe
43
Messages
43
Customers
3

Run storyboard

  1. Run #1: 1 invoice + 1 email + 1 message
  2. Run #2: 1 invoice + 1 email + 1 message
  3. Run #3: 1 invoice + 1 email + 1 message
  4. ···
  5. Run #14: 1 invoice + 1 email + 1 message
  6. ···
  7. Run #50: 1 invoice + 1 email + 1 message

Fake inbox

  • Your invoice

    to ada@example.com · after run #50

  • Your invoice

    to ada@example.com · after run #49

  • Your invoice

    to ada@example.com · after run #48

What to fix

  • Criticalblast radius

    Fake-company ledger: 43× identical customer emails

    Add an idempotency key (order id / delivery id) before Gmail and Stripe. Retries must no-op.

  • Highapproval

    Payment path can fire without a human gate

    Move Stripe after wait/approve, or require confirmation before charge.

This is a preview. The live demo runs the real engine — no signup.

See the full report →

Workflows look fine in the editor.Production is where they spam, double-charge, or go quiet.

If you ship n8n for clients, this is a second opinion before go-live. Replay the same webhook twice and see what still fires.

How it works

Four steps from export to gate

Upload, simulate, stress, decide. Same path every time.

  1. 01

    Export from n8n

    Download your workflow JSON. Leave credentials out. Crash Labs only needs the graph.

  2. 02

    Spin up a fake company

    Mock Stripe, Gmail, Slack, SMS, Sheets, CRM. Nothing real leaves the building.

  3. 03

    Replay until it breaks

    Same event twice, spam bursts, 50-run stress — then read the ledger.

  4. 04

    Get the blast radius

    Emails, SMS, invoices, CRM writes that survive retry. PASS / WARN / FAIL.

What you get

A report you can act on

Blast radius ledger

Exactly what would leave the company after retries: emails, SMS, invoices, commerce, CRM.

Retry survival

Delivery #1 vs #2. Idempotency and reversibility scores per side effect.

Deploy gate

PASS, WARN, or FAIL with fixes you can ship before the client turns it on.

Next

Run it on your workflow

Paste n8n JSON. Confirmed accounts get a free credit to try. After that, pay per run.

Open the labWatch the demo again