Use this agent for any n8n development task - frontend (Vue 3), backend (Node.js/TypeScript), workflow engine, node creation, or full-stack features. The agent automatically applies n8n conventions and best practices. Examples: user: 'Add a new button to the workflow editor' assistant: 'I'll use the developer agent to…
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment…
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Use this agent when you need to conduct in-depth technical research on complex topics, technologies, or architectural decisions. This includes investigating new frameworks, analyzing security vulnerabilities, evaluating third-party APIs, researching performance optimization strategies, or generating technical…
Expert n8n workflow architect and builder. Use after onboarding is complete. Knows the full project context from CLAUDE.md, all workflow specs from PRD.md, architecture from DESIGN.md, and all 7 n8n skills. TRIGGERS — invoke when: building a new workflow, debugging a broken node, writing Code node JS/Python, designing…
Project setup wizard. Runs automatically when CLAUDE.md contains [NOT SET] fields — triggered by any greeting (hey, hello, start, let's go, etc.). Asks 6 questions, fills CLAUDE.md and PRD.md, creates workflow stubs, then hands off to n8n-workflow-builder. Do NOT invoke manually — it triggers automatically on first…
Decomposes a PRP-style end-to-end use case into a stack of sub-workflows along known decomposition rules, fixes the handover contracts between them, and (in EXTEND mode) plans the delta against an already-comprehended stack. Read-only — emits the stack plan / delta, never writes files or touches the instance. Used as…
Reconstructs the real call-graph (DAG) of an existing workflow stack from executeWorkflow references in the local mirror, reconciles it against the central architecture doc (or reverse-engineers one if absent), and reports the current stack shape so the architect can plan a delta. Read-only — assumes the local repo…
Code review and error diagnosis for n8nac Decorator-TS workflow files. Use after writing or modifying .workflow.ts files to catch issues before pushing. Run in background for non-blocking reviews.
Use this agent to design the LangGraph architecture for converting analyzed n8n workflows. Produces a detailed conversion plan with state schemas, tool specs, and implementation order.
Use this agent to review an n8n-to-LangGraph conversion for fidelity, test coverage, and code quality. Compares implementation against original workflows.
Use this agent to deeply analyze n8n workflow JSON files for LangGraph conversion. Extracts system prompts verbatim, traces execution paths, identifies integrations and credentials needed.
A provider type is an AI CLI: claude, codex, gemini (provider.go:36-40). A provider instance is a configured copy of one. Multiple instances per type are supported — same claude binary, different env vars (e.g. two PATs).
A sub-agent is another agent that your agent hands one self-contained task to, waits for, and gets an answer back from. Use it when a piece of work wants a different role — research, code review, image generation — or when the intermediate steps would flood the main conversation.
Optimizes n8n workflows for performance and reliability. Analyzes structure, reduces complexity, improves error handling. Use for workflow review and optimization.
Plans n8n workflow automation. Analyzes requirements, searches templates, designs node structure. Use PROACTIVELY when users need new workflows or automation.