Agent skill · operations · n8n-io
n8n-cli
Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.
Why this skill is useful
Adds specific commands and workflows for managing n8n instances that the AI wouldn't reliably generate on its own.
What it needs
Requires n8n-cli installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
n8n CLI The n8n-cli command-line tool manages an n8n instance via its REST API. It auto-detects piped output and switches to JSON, making it composable for scripts and LLM tool use. Setup Global Flags Every command supports these flags: Flag Short Description ------ ------- ------------- --url -u Instance URL (overrides config/env) --apiKey -k API key (overrides config/env) --format -f Output format: table, json, id-only --json Shorthand for --format=json --jq jq-style filter (implies --json), e.g. '.[0].id', '.[].name' --quiet -q Suppress output --no-header Hide table headers (for awk/cut parsing) --debug Print HTTP details to stderr Auto-JSON: When stdout is piped (not a TTY), output defaults to JSON automatically. Workflows Executions Credentials Tip: Use credential schema <type> to discover required fields before creating. Projects Tags Variables Data Tables Users Other Composability Patterns The CLI is designed to be piped and composed: Workflow JSON Structure When creating or updating workflows, the JSON follows this structure: Key points: nodes[].type follows the pattern n8n-nodes-base.<nodeName> for built-in nodes connections is keyed by source node name, with main output arrays Each connection specifies target node, type (usually main), and output index Use workflow get <id> --json to see real examples from the instance
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/n8n-cli