N8N Workflow Troubleshooter

Debug n8n workflow execution errors fast.

Install
cmdop skills install agensi-n8n-workflow-troubleshooter

N8N Workflow Troubleshooter is a skill designed for developers and automation engineers who maintain n8n workflows in production environments. When a workflow fails or becomes stuck, manual debugging typically involves checking logs, inspecting Docker container states, and toggling workflows on and off to reset internal state. This skill automates that diagnostic process by identifying common workflow execution failures, verifying that Docker dependencies required by n8n are in a healthy state, and applying deactivate/reactivate cycles to workflows that are stuck and unresponsive. The skill targets n8n power users who run workflows in production and need to resolve errors quickly without iterating manually through each possible failure point. It does not require environment variable configuration based on the available facts. Because no individual tools are listed for this skill, its behavior is encapsulated entirely within the skill logic rather than exposed as discrete callable functions. This makes it appropriate for agent workflows where the goal is rapid triage of n8n errors rather than granular programmatic control over specific n8n API endpoints. It is not a general-purpose n8n management interface and does not cover workflow creation, editing, or deployment.

Use cases

  • Diagnose why a production n8n workflow stopped executing
  • Check whether Docker dependencies are healthy when a workflow fails
  • Apply deactivate/reactivate cycles to clear a stuck n8n workflow state
  • Reduce manual trial-and-error when troubleshooting recurring n8n execution errors
  • Triage common n8n failure patterns automatically during an incident

When to use it

  • A production n8n workflow is failing and the root cause is unclear
  • A workflow appears stuck and manual toggling would otherwise be required
  • Docker-backed n8n deployments need dependency health checked as part of error diagnosis
  • An agent pipeline needs automated triage of n8n execution errors

When not to use it

  • The goal is to create, edit, or deploy n8n workflows rather than debug them
  • Fine-grained programmatic control over specific n8n API endpoints is needed
  • The n8n instance is not running on Docker and Docker dependency checks are irrelevant
  • A full n8n administration interface is required