Looking for 5 n8n developers to test a workflow QA tool — free private beta

Hey everyone,

I’ve been building FlowPrecheck, a QA and production-readiness tool specifically for n8n workflows.

The idea is simple: before putting a workflow into production, FlowPrecheck analyzes it for things like:

  • broken or risky branches
  • missing error handling
  • unsafe retry behavior
  • API failure risks
  • maintainability issues
  • production-readiness problems

It also includes Runtime QA and GitHub PR checks for testing workflows more like software.

I’m at the private beta stage now and I’m looking for around 5 n8n developers/freelancers who already build real workflows.

I’m not looking for compliments — I specifically want to know:

  • Which findings are actually useful?
  • Which findings are false positives?
  • What feels confusing?
  • What breaks?
  • Would this actually help before deploying a client workflow?

Private beta is free.

You can try it here Dm me here : Telegram: Contact @MikeyyFrr

If you’re interested, reply here or DM me. I’d really appreciate feedback from people actually using n8n in production.

I build n8n in production and this is the exact class of problem I spend my time on, so I’ll take one of the five slots if any are still open.

So you know what kind of feedback you’d be getting: the failure I care about isn’t the red execution, it’s the green run that quietly did nothing or did half the job. A run that writes 47 of 50 records and reports success. If FlowPrecheck flags “this branch can complete with zero items and raise no alert”, that’s the finding worth paying for. If it mostly flags missing error branches, it’s a linter, and I’d tell you that plainly.

Things I’d check on day one:

- Does it distinguish a node with no error output from a node whose error output goes somewhere nobody reads? Those look nearly identical in the JSON and are completely different in production.

- Retries: does it catch a retry on a non-idempotent write? Retrying a POST that creates a record is worse than not retrying at all, and it’s the most common unsafe retry I run into.

- Does it tell an IF with a missing else path apart from one where the dead end is deliberate?

- A false positive I’d expect you to have: flows that look like they have no error handling because the handling lives in a separate error workflow wired to the error trigger.

A practical note for anyone else joining the beta: test with synthetic workflows that mirror the shape of your real ones rather than uploading client exports, since those carry credential references, endpoints and internal structure.

Related offer, and it’s the part I think would actually move your tool forward: I can build you a set of deliberately broken workflows, each with one known planted defect, so you can measure detection rate instead of collecting opinions. Five people saying “feels useful” tells you much less than “caught 7 of 12 planted defects, missed these 5”.

One question before I start, because the answer changes what the tool can possibly catch and is worth stating up front in your pitch: does it analyse the workflow JSON statically, or does it need execution history?

1 Like

Hey Alex, absolutely — one of the five slots is yours. This is exactly the kind of feedback I was hoping to get.

To answer your question: the core FlowPrecheck analysis is static analysis of the workflow JSON. It doesn’t require execution history. Runtime QA is a separate layer where we simulate failure scenarios and edge cases deterministically.

Your examples are also exactly where I want the product to go beyond being just a “missing error branch” linter — especially silent-success cases, unsafe retries on non-idempotent writes, deliberate vs accidental dead ends, and external error workflows.

I also really like the planted-defect workflow idea. A controlled set where each workflow has one known failure would be much more useful for measuring detection quality than just collecting subjective feedback.

I’ll DM you access/details. And please be as critical as possible — false positives, missed defects, confusing findings, all of it is useful.

Hey! Quick update — FlowPrecheck is live on Product Hunt today. Given how much your test cases shaped the beta, felt right to let you know first.

Would genuinely appreciate an upvote/comment if you’re on PH: FlowPrecheck: Test your n8n workflows like real software | Product Hunt

Thanks again for the testing — it made a real difference.