Developer's own acceptance tests caught two bugs in n8n workflow pack before launch
A developer selling an n8n automation workflow pack discovered two critical bugs by running acceptance tests on a clean n8n instance before listing the product. The first bug involved Node.js's built-in 'crypto' module being blocked by n8n's Code node sandbox on standard installs, breaking deduplication logic that worked fine in a custom dev environment. The second bug caused a safety gate — designed to block message delivery until a specific environment variable was set — to crash instead of failing gracefully, because default n8n installs block environment variable access in code nodes. Both issues were invisible during local development and only surfaced when the workflows ran on a stock installation. The developer fixed both bugs and now ships every workflow with acceptance criteria and a buyer-facing checklist, arguing that running tests on a clean instance is the only reliable way to catch environment-specific failures.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in