n8n-automation
Skill0 starsChanged 4 months agoMITView on GitHub
Use this skill when the user asks to create, edit, debug, or export n8n workflows/automations ("create an n8n automation", "build a workflow that...", "export the workflows", "why is this workflow failing"). Requires the n8n-mcp Docker MCP server connected (tools like search_nodes, validate_workflow) and, for live-instance actions, an n8n API key configured for the target instance.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- realjaymes/marketingagentskillstheir own version, first seen Oct 21, 2026
- garri333/Skillstheir own version, first seen Oct 11, 2026
- mintorain/mintorain-tmux-ocastratheir own version, first seen Apr 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- realjaymes/marketingagentskills★ 68same name
- mintorain/mintorain-tmux-ocastra★ 8same name
- garri333/Skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- adding-authenticationSkill
- auditing-seoSkill
- automating-git-workflowsSkill
- building-email-sequencesSkill
- building-graphql-apisSkill
- building-wordpress-pluginsSkill
- designing-carouselsSkill
- fine-tuning-ml-modelsSkill
- handling-web-formsSkill
- organizing-spreadsheetsSkill
- reviewing-cloudflare-workers-codeSkill
- reviewing-code-for-securitySkill
- scaffolding-landing-pagesSkill
- setting-up-error-monitoringSkill
- setting-up-firebase-authSkill
- using-nextjs-best-practicesSkill
- working-with-postgres-databasesSkill
- writing-marketing-copySkill
- writing-terraform-codeSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 57
If the n8n_* tools aren't available and the task requires acting on a real instance:
- Distinctive: line 60
Ask the user for: the instance's base URL + an API key (n8n → Settings → n8n API → Create API Key).
- Very specific: line 62
Never paste the key directly into a visible Bash command, and never echo it back.
- Distinctive: line 66
Delete that env file at the end of the task.
- Distinctive: line 75
Always in this order — skipping a step produces a workflow that passes syntactic validation but breaks in production:
- Very specific: line 99
Never write a credential secret into the workflow JSON — n8n already separates this (credentials: { googleSheetsOAuth2Api: { id, name } } …
- Distinctive: line 102
If the workflow needs a credential that doesn't exist on the instance, tell the user — you can't create an OAuth credential via the API, …
- Distinctive: line 108
When the request is "save/export the workflows to GitHub":
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
n8n Automation (via Docker MCP + n8n API)
Prerequisites (one-time setup)
This skill does nothing on its own — it needs the n8n-mcp toolkit actually
connected to Claude Code first. If search_nodes/validate_workflow/etc.
aren't in the tool list, none of the steps below will work. Set up, in order:
- Docker Desktop — installed and running. This is what actually hosts
the
n8n-mcpserver; Claude Code doesn't run it directly. - VS Code + Claude Code — the Claude Code extension (or CLI) installed in VS Code, signed in, in the project you want to automate.
- Connect the MCP server to Claude Code — in Docker Desktop's MCP
Toolkit/Catalog, find and enable
n8n-mcp, then connect it to your Claude Code client (Docker Desktop's MCP Toolkit has a "Clients" section for this). Once connected, its tools surface in Claude Code as a single aggregated connection, usually namedMCP_DOCKER. - Verify the connection — ask Claude to list available tools, or just
try
search_nodes. If it's not available, the MCP server isn't connected yet — fix that before attempting anything below, rather than troubleshooting workflow logic that was never the actual problem. - For live-instance actions only (creating/listing/updating real
workflows, not just looking up node info) — the MCP server additionally
needs
N8N_API_URL(and an API key) configured for the target n8n instance. See "Credential setup" below for how to get and use that key safely.
Exact menu labels in Docker Desktop's MCP Toolkit change between versions — if steps 3-4 don't match what's on screen, check Docker Desktop's own MCP Toolkit docs rather than assuming this skill's wording is current.
What this skill covers
Creating, editing, validating, and deploying n8n workflows using the n8n-mcp
toolkit (running in Docker, exposed as an MCP server — usually shows up as
MCP_DOCKER in the tool list) combined with n8n's public REST API for
specific instances.
These are two separate capabilities — don't conflate them:
- Node knowledge (always available via
MCP_DOCKER): search nodes, inspect properties, validate configuration, look up templates. Requires no credentials at all. - Actions on a real instance (
n8n_list_workflows,n8n_create_workflow,n8n_update_partial_workflow,n8n_trigger_webhook_workflow): only appear onceN8N_API_URLis configured for the MCP server. If they don't show up, the instance isn't connected — don't claim you can create/list workflows without it.
Credential setup (per instance)
If the n8n_* tools aren't available and the task requires acting on a real
instance:
- Ask the user for: the instance's base URL + an API key (n8n → Settings → n8n API → Create API Key).
- Never paste the key directly into a visible Bash command, and never echo
it back. Save it to an env file outside the repo (e.g. in the session
scratchpad) and reference it via
source file && curl -H "X-N8N-API-KEY: $KEY" .... - Delete that env file at the end of the task.
- Known limitation: n8n's public API doesn't expose folders/projects
(
folderId) or project endpoints on instances without an enterprise license — you can only list/filter by workflow. If the user asks for "just the workflows in folder X," flag this limitation before attempting to filter.
Standard creation/editing workflow
Always in this order — skipping a step produces a workflow that passes syntactic validation but breaks in production:
- Find the right node
search_nodes({query})orlist_nodes({category})— never assume a node name from memory, packages change between versions. - Configure with essentials first
get_node_essentials(nodeType)beforeget_node_info(which returns 100KB+ and blows up context for no reason). Only escalate toget_node_infoif essentials doesn't have the field you need. - Validate before deploying
validate_node_minimal→ required fields.validate_node_operation→ full validation with suggested fixes.validate_workflow→ the whole graph (connections, expressions, cycles). - Deploy
n8n_create_workflow(new) orn8n_update_partial_workflow(edit via diff — prefer this over recreating the whole workflow for small tweaks). - Confirm Report back to the user: name, ID, status (active/inactive), and whether any trigger needs to be manually activated (webhook, cron) before it actually starts working.
Credentials inside the workflow (nodes using OAuth/API keys)
- Never write a credential secret into the workflow JSON — n8n already
separates this (
credentials: { googleSheetsOAuth2Api: { id, name } }is just the reference, the actual value lives in n8n's credential vault). - If the workflow needs a credential that doesn't exist on the instance, tell the user — you can't create an OAuth credential via the API, that requires the login flow in the n8n UI.
Exporting / version-controlling workflows (backup to git)
When the request is "save/export the workflows to GitHub":
- Pull the full JSON via
GET /api/v1/workflows(the listing already returns completenodes/connections— no need for one call per workflow). - Export clean, re-importable fields:
id, name, active, nodes, connections, settings, staticData, pinData, tags. Drop runtime metadata (activeVersion,versionCounter,shared, publish history) — that's instance-specific noise, not part of the workflow itself. - Organize into folders by category inferred from the name (simple regex
rules are enough — the user can reorganize later). Generate a
manifest.json(category, file, id, status) to allow programmatic reorganization afterward. - Private repo by default, unless the user asks for public — workflows almost always have client/internal-process names in the text.
Common mistakes to avoid
- Treating
MCP_DOCKERas if it's already connected to an instance — it's generic untilN8N_API_URLis configured. - Skipping
validate_workflowon the assumption that each node's individual config already guarantees the workflow works — broken connections and malformed expressions only surface in full-graph validation. - Generating a workflow with
n8n_create_workflowwithout asking whether it should start active or inactive — workflows with a webhook/cron trigger start running immediately ifactive: true.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

