Individual skill
n8n
Use when operating a live n8n instance programmatically — its REST API (`{host}/api/v1`, `X-N8N-API-KEY`) or the n8n-mcp server — to create, validate, test, activate, update, delete workflows and read executions on self-host or n8n.cloud. NOT designing the flow or its importable JSON (that is `automation-flows`), NOT another platform (`make`, `zapier`).
skills/n8n/SKILL.md
Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 564
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- cline Repository topic
- codex Repository topic
- coding-assistant Repository topic
- cursor Repository topic
- n8n Declared skill tag
- automation Declared skill tag
- workflows Declared skill tag
- mcp Declared skill tag
- rest-api Declared skill tag
- no-code Declared skill tag
- integrations Declared skill tag
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesSKILL.mdcore · 10,329 bytesevals/README.mddoc · 1,088 bytesevals/cases.yamlasset · 3,963 bytesreferences/auth-and-selfhost.mddoc · 2,857 bytesreferences/n8n-mcp-tools.mddoc · 4,526 bytesreferences/rest-api-cheatsheet.mddoc · 4,438 bytes
Read excerpt
# n8n — operate a live instance over its REST API and MCP
You already have a workflow *design* — the trigger→steps→error shape and the importable JSON, which is
`automation-flows`' job and this skill does not re-teach it. This skill is the **operate** half: push
that JSON into a running n8n, validate it, test it, flip it live, watch its executions, and tear it
down safely — all without touching the UI. n8n has the richest programmatic story of the no-code
platforms: a first-party REST API **plus** a mature MCP server, both hitting the same instance.
## Connect first — REST API vs MCP
Two ways to drive the same instance. Pick by who is at the wheel.
| | **Public REST API** | **n8n-mcp** (czlonkowski, de-facto standard) |
|---|---|---|