I built a stress tester for n8n workflows so you can see what blows up before it hits real customers

Hey,

I kept seeing the same thing with n8n. People build a workflow, test the happy path once, flip it on, and then something weird happens in production. Duplicate webhook. Missing field. Stripe retry. Suddenly you emailed half your list twice or charged someone wrong.

So I built Crash Labs.

You paste your n8n workflow JSON. It runs it against a fake company (mock email, Stripe, Slack, etc). Then it shows the blast radius. What would have been sent, charged, created. Pass / warn / fail.

It is early. Not every node is covered yet. Coverage and blind spots are in the report so it does not pretend it proved more than it did.

If you build client automations or anything that touches money / customers, try dumping a workflow in and tell me what it gets wrong.

https://crashlabs.app

Happy to take brutal feedback.

6 comments

I built a stress tester for n8n workflows so you can see what blows up before it hits real customers