n8n Hub

**Quick judgment** Solid, focused skill for teams already committed to n8n who want both good workflow design practices and operational control via the n8n REST API. Best suited to technical users comfortable with API keys, HTTP, and n8n concepts. **Strengths and scenarios where it works well** - When you need **well-architected n8n workflows**: idempotency, retries, logging, failure routing, and review queues are explicitly called out and supported. - When you want **importable artifacts**: it can produce `workflow.json` plus a runbook-style `workflow-lab.md` for documentation and handoff. - When you need **operational control** over an existing n8n instance: listing workflows, activating/deactivating, and managing executions (list, retry) via the public API. - Good fit for **production-ish environments** where observability and guardrails matter (run IDs, logs, status rows, and non-silent failures). **Key risks / limitations** - **Requires a working n8n API**: free trial plans with API disabled will not work; you need a self-hosted or upgraded cloud instance and a valid API key. - **Operational risk if misused**: activating/deactivating workflows and retrying executions can affect production behavior; careful environment selection and access control are important. - **Security responsibilities remain with you**: the skill expects you to manage API keys securely and respect n8n’s existing audit/security controls (it explicitly should not be used to bypass them). **Recommended use** Use this skill when you: - Already run or plan to run an n8n instance and want to **standardize how workflows are designed and operated**. - Need **structured planning plus concrete JSON output** that can be imported into n8n. - Want a repeatable way to **operate workflows via the REST API** (list, publish, deactivate, debug) in a controlled, documented manner. Avoid it if you don’t use n8n, need pure code-only automation, or cannot enable the n8n public API in your environment.