- Home
- Skills
- Workflow Automation
- n8n failure test kit
More screenshots
Works with the AI Agents you already use
n8n failure test kit
Generate structured failure-test packs for n8n workflows to audit error handling, rate limits, and idempotency risks.
$5
n8n failure test kit
Example session with this skill installed
I have a Shopify to Slack n8n workflow. I need a failure test kit to see what happens if the Shopify API is down or if we get a duplicate order webhook. Here is my workflow.json.
- Read your context and instructions
- Compiled the n8n failure test
I have analyzed the Shopify-to-Slack workflow. I have prepared the five-file failure test kit, including 4 targeted scenarios for service outages and 1 scenario for duplicate delivery.
Failure Test Pack: Shopify Integration
The following files have been generated to your local directory:
workflow-review.json: Identified 12 nodes, includingShopify TriggerandSlack Send.test-cases.json: 5 scenarios defined (SHP-01 to SHP-05).test-plan.md: Step-by-step injection guide for your test environment.run-results-template.json: Empty results schema for your execution phase.repair-plan.md: Critical observations regarding missing retry logic on the Slack node.
repair-plan.md Extract
| Node Name | Observation | Case ID | Proposed Change |
|---|---|---|---|
| Slack Send | "Continue On Fail" is False | SHP-01 | Enable Error Trigger to log failures to a persistent store. |
| Shopify Trigger | No deduplication logic found | DUP-01 | Implement an external state check (Redis/DB) using order_id. |
| HTTP Request | Retry on 429/503 not enabled | SHP-02 | Toggle 'Retry on Failure' and set max attempts to 3. |
Next steps
- Run
python scripts/build_failure_pack.py --workflow workflow.json --contract contract.jsonto generate the full JSON artifacts. - Import the workflow into an isolated n8n test instance and point the Shopify webhook to a mock service.
- Execute the
DUP-01test case by sending the sameorder_idtwice and checking the Slack channel for duplicate posts.
Connects securely to your tools. The creator never sees your data.
About this skill
Deploying n8n workflows without testing edge cases is a recipe for silent production failures. This skill generates a comprehensive failure-test pack to validate how your automation handles rate limits, outages, and duplicate deliveries before you hand it off to a client.
What it does
- Sanitizes workflows by auditing exports for sensitive headers and credentials before generating test fixtures.
- Generates test cases for specific failure modes including missing input fields, 503 service outages, and 429 rate limiting.
- Creates synthetic fixtures based on your node output structures to simulate real-world data without using production payloads.
- Identifies structural risks like ambiguous write operations, missing error triggers, or lack of idempotency logic.
- Produces repair plans that map observed configuration weaknesses to specific behavioral risks and verification steps.
How it works
- Supply your workflow export in JSON format along with a basic contract defining expected service effects and input boundaries.
- Execute the builder script using the provided Python 3.10 utility to materialize a structured test directory locally.
- Review the generated pack including
test-cases.jsonandworkflow-review.jsonto identify blocked scenarios or required manual injections. - Follow the repair plan to implement suggested node-level improvements or idempotency strategies in your n8n environment.
Frameworks & tools
Built for n8n workflow developers. Requires Python 3.10+ for local test pack generation. Works with standard n8n JSON exports and requires a separately authorized n8n instance for actual execution.
Why this beats prompting it yourself
Generic prompts often miss n8n-specific quirks like the difference between a node's internal version and the instance version. This skill uses a structured approach to generate precise JSON pointers for node outputs, ensuring your test fixtures actually match the way n8n handles data items.
Use cases
- Pre-handoff auditing to verify that a freelancer's workflow won't crash on the first API timeout.
- Idempotency verification to ensure duplicate webhook triggers don't result in double-billing or duplicate database entries.
- Rate limit hardening by simulating 429 responses to see if your retry logic actually respects backoff requirements.
- Boundary testing for complex JSON payloads to confirm that missing optional keys don't break downstream JavaScript code nodes.
Known limitations
Does not execute workflows or verify n8n expression logic. Requires a separate n8n environment for live testing. Cannot simulate concurrent race conditions or third-party queue persistence.
Requires Python 3.10+ for generation. Does not execute workflows, prove import compatibility, or validate n8n expressions. Manual n8n environment required for execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 18 days ago
Requires