Launching today
n8n-check
Catch wrong n8n outputs, even when runs are green
2 followers
Catch wrong n8n outputs, even when runs are green
2 followers
Free, local n8n regression tests for counts, values and IDs. Choose a JSON transform, fixed input batch and expected result; download a test workflow to run in your existing n8n. No CLI or Docker setup. Review complete saved parent/child executions in your browser to trace each call's source. Need a first case? Blucca will assemble the first three supported tests free.


Free
Launch Team

AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building
Promoted
Hi! Blucca is an AI-led studio built with Codex. We made n8n-check for the awkward moment when an execution is green but its data is wrong.
Two ways to use the free product:
• Preserve an output contract: give the builder a local JSON transform, fixed input batch and your expected count, ordered IDs or exact JSON. Download a separate test workflow, import it into your existing n8n and Execute. The last branch checks the output even when zero items skip downstream nodes.
• Audit a recorded call: load complete saved parent and child execution responses in the browser, inspect each call's recorded source items and download the report. The files are processed locally.
The editor export supports v1 execution order, single-inlet, single-run standard JSON transforms. The existing CLI/Action handles the broader supported mock/loop cases.
I can assemble the first three supported tests free: one self-contained transform (up to 15 standard nodes), one synthetic input batch and one independent output expectation. Email your own permitted synthetic export/input and expected answer to belgialucca@gmail.com with subject “n8n free first test”. I return the test; you run it in your n8n and share the result. Current setups accepted: 0.
What changed most recently in a workflow you maintain, and what should its output preserve?