- Home
- Skills
- Workflow Automation
- n8n Reliability Debugger
Works with the AI Agents you already use
n8n Reliability Debugger
Diagnoses n8n workflow failures and turns noisy execution errors into safe, actionable repair plans.
$6.99
n8n Reliability Debugger
Example session with this skill installed
I have a workflow failing at an HTTP Request node. It says '403 Forbidden' but my credentials work in Postman. Here is the redacted JSON export and the node input/output samples.
- Read your context and instructions
- Compiled the n8n reliability debugger
The diagnosis indicates an authorization scope mismatch. While the credential object is valid, the specific endpoint requires a scope not mapped in the n8n credential configuration.
Diagnostic Report
| Component | Detail |
|---|---|
| Failed Node | HTTP Request: Sync CRM |
| Error Type | 403 Forbidden (Authorization/Scope) |
| Evidence | Resolved parameters show the bearer token is sent, but the provider response body indicates insufficient_scope. |
| High Impact | Yes (Writes to Production CRM) |
| Confidence | 90% |
Minimal Repair Plan
// Suggested change for the 'Sync CRM' node parameters
{
"parameters": {
"authentication": "oAuth2",
"node": "n8n-nodes-base.httpRequest",
"nodeVersion": 4.1,
"options": {
"scope": "crm.objects.contacts.write crm.schemas.contacts.read"
}
}
}
Verification Matrix
Test 1: Scope Validation: Update the OAuth2 credential in n8n to include crm.objects.contacts.write. Re-authorize and re-run.
- Test 2: Item Shape: Pass a single contact object with valid email to ensure 201 Created.
- Test 3: Rate Limit: Simulate 10 rapid executions to verify retry-on-429 logic is active.
Next steps
- Update your n8n Credential object with the missing write scopes.
- Run a manual execution on a single test record in your staging environment.
- Verify the
Sync CRMnode no longer returns a 403.
Connects securely to your tools. The creator never sees your data.
About this skill
Workflows fail for reasons that aren't always obvious in the n8n execution log. This skill provides a structured path from an execution error to a verified repair plan without requiring production access or sensitive credentials.
What it does
- Analyze exports by mapping triggers, node versions, and branch logic from redacted JSON files.
- Trace expressions to find where references break or item shapes change unexpectedly.
- Isolate side effects by identifying high-impact nodes like CRM writes or payment gateways before proposing changes.
- Rank root causes using evidence-based confidence scoring for auth, data-shape, or logic failures.
- Generate repair plans focused on minimal patches, such as corrected pagination cursors or idempotency guards.
- Create test matrices that cover happy paths, rate limits, and 5xx provider errors for safe verification.
How it works
- Provide a redacted workflow export and the specific error message or execution ID.
- The skill inventories the graph, identifies high-impact nodes, and flags disconnected paths.
- It correlates the failing boundary against resolved parameters and input item counts.
- You receive a ranked list of hypotheses and a targeted diff for the specific node settings needing repair.
Frameworks & tools
Built for n8n workflow automation. Uses local Python scripts inspect_workflow.py and validate_workflow.py for structural inventory and safety linting without external network calls.
Why this beats prompting it yourself
Generic prompts often miss n8n-specific quirks, like the inability of Code nodes to read credentials directly. This skill follows a strict diagnostic contract that prioritizes minimal repairs over risky, full-workflow rewrites.
Use cases
- Debugging production failures in inherited workflows with missing documentation.
- Validating a repair plan in a staging environment before pushing to a client instance.
- Identifying missing scopes or auth errors in complex HTTP Request nodes.
- Generating a regression test plan for high-stakes automation involving financial or CRM data.
Known limitations
Does not act as a remote administrator. Cannot verify fixes that require active external API calls or secret values. Structural analysis is limited to the provided JSON export.
Cannot access live n8n instances or read secret values. Diagnosis is limited to provided exports and logs. Requires manual implementation of suggested patches.
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 today