using-n8n-skills

Using n8n Skills

The official n8n MCP evolves over time, so tool names, parameters, and default behaviors can drift between versions. When you spot drift (a tool a skill names doesn't exist, a parameter shape doesn't match what get_node_types returns, or behavior differs from what the skill describes), suggest updating the skill and n8n instance to the latest stable.

Non-negotiables

Three rules with no exceptions. Violating any produces workflows that look right but break in production.

1. Invoke the relevant skill before any n8n action. Not just MCP tool calls. Before writing SDK code, configuring a node, designing a workflow, wiring a connection, building an agent, or handling errors: invoke the matching skill via the Skill tool. This document is a router. The skill body has the actual rules. The PreToolUse hooks remind you on the highest-impact MCP calls if a plugin is installed. The responsibility is yours on everything else. Err on the side of reading extra documents.
2. Validate AND verify before publishing. validate_workflow before publish_workflow, and get_workflow_details after every create or update to check the connections object. Validation alone misses many issues documented in the skills that will silently break workflows.
3. Tokens/secrets never go in text fields. Always use the n8n credential system. If no native node exists, configure HTTP Request with the official credential type. See n8n-credentials-and-security.

Lean on skills, not training data

n8n evolves faster than any model's training cutoff. Parameter names drift, new MCP tools land, defaults change, patterns get deprecated. Anything you "remember" is likely wrong, often silently.

Trust the skills + live MCP tools (get_node_types, get_sdk_reference, get_workflow_best_practices) over recollection. If a skill contradicts what you "know", trust the skill. If get_node_types contradicts a skill, trust the tool. Without this discipline you will ship workflows that look right and silently fail: parameter names that don't exist, renamed nodes, deprecated patterns.

Unless a user preference overrides it, err on the side of loading too many skills rather than too few. Even a 3-node webhook flow typically needs n8n-node-configuration, n8n-expressions, n8n-error-handling, and n8n-workflow-lifecycle. Nothing in n8n is too small for skills.

Strong defaults (each skill owns its exceptions)

• The Code node is a last resort. Expression first, then arrow function inside Edit Fields, then Code. Code earns its place for multi-source aggregation, libraries, and stateful work. See n8n-code-nodes.
• Anything reusable becomes a stateless sub-workflow. Search existing ones via search_workflows({ query: 'Subworkflow' }) before building. See n8n-subworkflows.

Red flags: thoughts that mean STOP and invoke

These rationalizations cause skills to be skipped. If you catch yourself thinking any of them, invoke the relevant skill via the Skill tool, even if you "already read it" earlier in the session.

Thought	Action
"This workflow is simple, I'll just build it"	Invoke n8n-workflow-lifecycle. Most "simple" workflows are 10+ nodes by the time they ship.
"I'll add a Set node here to map these fields"	Invoke n8n-expressions. Set nodes feeding only 0 or 1 downstream consumer are the most common antipattern in this entire pack.
"I'll just use a Code node, it's easier"	Invoke n8n-code-nodes. The bar is high. Most reaches for Code can be expressions or Edit Fields with arrow functions.
"Validation passed, I'm ready to publish"	Invoke n8n-workflow-lifecycle and walk VALIDATION_CHECKLIST.md section 2 (the antipattern scan). Validation passing is necessary, not sufficient.
"The agent is wired up, the tool descriptions look fine"	Invoke n8n-agents references/TOOLS.md. Tool names and descriptions ARE part of the prompt, and "looks fine" usually means generic.
"I'll set this sub-workflow trigger to passthrough"	Invoke n8n-subworkflows. Passthrough is only correct for binary-receiving sub-workflows that won't be agent tools, or for sub-workflows that genuinely take no inputs (Define Below requires at least one field).
"I'll use passthrough so binary works, then branch internally on which input shape arrived"	Invoke n8n-subworkflows references/SUBWORKFLOW_PATTERNS.md "Splitting by input shape". This is the signal to SPLIT into two outer sub-workflows (one Define Below, one passthrough) sharing a common downstream sub-workflow. Don't fight passthrough vs Define Below in one trigger.
"I should ask the user what their credential is named"	Don't. The string in newCredential('Label') is cosmetic. See n8n-credentials-and-security.
"The user mentioned data analysis, I'll write Python"	Invoke n8n-code-nodes. Default is JavaScript. Python only when explicitly asked.
"I'll add a Loop Over Items here to process each row"	Invoke n8n-loops. Default per-item iteration probably handles it without a Loop Over Items node.
"Date math, I'll use a DateTime node"	Invoke n8n-expressions. DateTime nodes are almost always wrong.
"I'll wrap this in a Merge with 3 sources"	Invoke n8n-node-configuration references/MERGE_NODE.md. Merge defaults to 2 inputs, and 3+ sources need numberOfInputs set explicitly.
"I'll fan out these three slow steps to run in parallel"	Invoke n8n-workflow-lifecycle and read the Execution model section. n8n executes fan-out branches sequentially (top-to-bottom by Y-position), not concurrently. For real concurrency, see n8n-loops and n8n-subworkflows (mode: 'each' + waitForSubWorkflow: false).
"User said which project, I'll just build it"	Invoke n8n-workflow-lifecycle. Project is not folder. Ask about folder placement BEFORE building. The MCP can't create folders, so if the requested folder doesn't exist, the user must create it in the UI first.
"I'll just run test_workflow to see what happens"	Invoke n8n-workflow-lifecycle references/TESTING.md. test_workflow mocks the trigger only. Slack sends, DB writes, payments all fire for real. Ask the user first when downstreams have side effects.

The meta-skill (this document) tells you WHICH skill applies. The Skill tool loads the actual rules. Reading the meta-skill once at session start is not a substitute for invoking the skill at the moment of decision.

Skill index

Invoke via the Skill tool. Trigger column = when to invoke.

Skill	Trigger
n8n-workflow-lifecycle	Starting, designing, organizing, or finishing a workflow. Covers sticky-note conventions, descriptions that capture the why, naming, validation checklist, folder limitations, MCP-access-per-workflow gotcha
n8n-subworkflows	Anything reusable, multi-step builds, or the user mentions reuse. Search before building, stateless patterns, naming-prefix convention for discovery
n8n-extending-mcp	You need capabilities the MCP doesn't natively provide. Wrap n8n APIs as workflow tools, with user permission
n8n-expressions	Writing {{}}, $json, $node, expression errors. Luxon for dates, indented multi-line, prefer expressions over extra nodes
n8n-node-configuration	Configuring any node. Operation-aware, property dependencies, never assume parameters
n8n-code-nodes	User reaches for a Code node, or custom logic is needed. Decision tree, JavaScript patterns when truly required
n8n-loops	Multi-item data, batching, paginated APIs, "for each" or "loop over" mentions. Default per-item iteration, executeOnce, Loop Over Items, HTTP pagination
n8n-agents	LangChain Agent node, tool calling, system prompts, structured output, memory, RAG. Tool names/descriptions as part of the prompt, sub-workflow as tool, modular prompt design
n8n-error-handling	Webhook-triggered or production-bound workflows. Error branch on every fallible node, 4xx for caller errors and 5xx for execution errors
n8n-credentials-and-security	Any auth, API key, or token mention. Credential system, custom credentials, HTTP Request with official creds
n8n-binary-and-data	Files, images, attachments. Binary handling patterns, agent-tool boundary, CDN requirement for chat surfaces
n8n-data-tables	Data Tables: schemas, default columns (id/createdAt/updatedAt), no-FK relational design, dedup, the no-JSON-only-primitives rule, the SDK-vs-UI manual-mapping quirk
n8n-debugging	Errors, unexpected behavior, "this isn't working". Believe the user, check parameters, fetch n8n source from GitHub

n8n MCP tools (compact reference)

The MCP defers tool descriptions to save tokens. Below is the short-form list so you have working knowledge of every tool from turn one.

Tool names are shown without the MCP prefix. The qualified name is mcp__<server>__<tool> where <server> depends on the user's MCP config.

Workflow management

Tool	What it does
search_workflows	Search workflows across the instance by query (matches name and description, but tags are not filterable via MCP). The only cross-workflow tool. Use it to discover what already exists.
get_workflow_details	Fetch a workflow's full JSON by ID. Use after every create/update to verify connections.
search_folders	List folders. You cannot create or move folders. You can only place workflows into folders that already exist.
search_projects	List projects.
archive_workflow / publish_workflow / unpublish_workflow	Soft-delete / activate / deactivate. Validate before publish.
search_executions	Search executions across the instance (filter by status, workflow, time range). Use for "list recent runs" / "failures in the last hour". Single executions: get_execution.

Workflow building

Tool	What it does
get_sdk_reference	Fetch the n8n Workflow SDK reference. Read this before writing workflow code. Sections include guidelines and design.
get_workflow_best_practices	Fetch best-practices for a workflow technique. Call once per technique before searching nodes. technique: "list" discovers what's available.
search_nodes	Discover nodes by capability (e.g. "gmail", "slack", "schedule trigger"). Returns IDs plus discriminators (resource/operation/mode).
get_node_types	Fetch exact TypeScript parameter definitions for node IDs. Required before configuring any node. Don't guess parameter names.
create_workflow_from_code	Save a workflow from SDK code. Always include a 1-2 sentence description. Pass skillsUsed (below).
update_workflow	Apply atomic ops to an existing workflow (max 100, all-or-nothing): node/connection CRUD, credential binding, settings, metadata. Saves a draft; needs publish_workflow to go live. Pass skillsUsed (below).
validate_node_config	Schema-only validation of node configs (1-50 per call). Per-parameter errors, no graph noise. Side-channel for iteration/debug; validate_workflow still gates publish. For ai_tool subnodes set isToolNode: true.
validate_workflow	Validate full SDK code before create/update. Necessary but not sufficient: doesn't catch all wiring traps (.to(), merge index).
list_credentials	List accessible credentials (filter by type/project/etc). Returns metadata only, never secret values. Discover IDs before binding via setNodeCredential.

Workflow testing & execution

Tool	What it does
prepare_test_pin_data	Returns JSON Schemas (not data) for nodes that need pinning: triggers, credentialed nodes, and HTTP Request. You generate sample values.
test_workflow	Run with the pin data you supply. Auto-pins triggers, credentialed nodes, and HTTP Request. Code, Edit Fields, If, Data Tables, Execute Command, file ops, and sub-workflow calls run for real. Ask before running if any not-auto-pinned node has side effects. Pin data is per-execution only with no visual indicator in the execution viewer, so tell the user which nodes were pinned after the call. See n8n-workflow-lifecycle references/TESTING.md.
execute_workflow	Production execution with the real trigger. Wire error handling first. Same side-effect rules as test_workflow.
get_execution	Fetch a previous execution by ID.

Data tables

n8n's built-in tabular storage. Not an external service. Prefer over external DBs for workflow-local persistent state. Full surface:

Tool	What it does
create_data_table	Create a new Data Table.
search_data_tables	Find existing Data Tables.
rename_data_table / rename_data_table_column	Rename.
add_data_table_column / delete_data_table_column	Schema changes.
add_data_table_rows	Append rows.

The protocol, in order

For any n8n task:

1. Recognize the matching skill from the index above. If the task spans skills, recognize the primary one first and pick up others as their triggers come up.
2. Invoke the skill via the Skill tool before the first MCP call. Don't call n8n MCP tools blind.
3. Read the SDK reference once per session before writing workflow code (get_sdk_reference). The most efficient way to avoid SDK-shape mistakes.
4. Get node types before configuring any node (get_node_types). Guessing parameter names creates invalid workflows, sometimes silently.
5. Validate before publish, verify after create/update. Validation catches schema errors. Verification (pulling the workflow back via get_workflow_details) catches connection bugs validation misses.
6. Surface drift when you spot it. If a tool or parameter doesn't match what a skill says, tell the user. Updates may be needed.

Reporting skills used

create_workflow_from_code and update_workflow take an optional skillsUsed: string[]. Pass it every time so the n8n team can measure plugin impact on MCP output.

• Contents: skills invoked while preparing this workflow change. Use the qualified Skill-tool name (e.g. n8n-skills:using-n8n-skills, n8n-skills:n8n-workflow-lifecycle).
• Window: skills invoked since the last successful create/update call. Resets after each.
• Limits: max 50 entries, each max 128 chars.

Reviewing existing workflows or projects

For audits, code-review, or any task framed as "review this workflow" / "what's wrong with this" / "audit this project," walk the review checklist: n8n-workflow-lifecycle references/REVIEW_CHECKLIST.md. Severity-tiered (MUST FIX / SHOULD FIX / NICE TO HAVE), with each item linking to the canonical skill ref for the fix. Distinct from VALIDATION_CHECKLIST.md (pre-publish gates for in-progress builds): REVIEW_CHECKLIST is for any workflow, including ones built by anyone, any age.

A review agent should call get_workflow_details first, walk the checklist top to bottom, and report findings grouped by severity. MUST FIX items shouldn't be auto-fixed without user confirmation.

When in doubt

• Can't find a workflow the user is referring to? If the user built it in the n8n UI, the most common reason is MCP access isn't enabled on that specific workflow: UI-created workflows can default to MCP-disabled and stay invisible until the per-workflow toggle is flipped. Ask the user: "Open the workflow in n8n, Settings, toggle MCP access on." (MCP-created workflows default on, so this only applies to UI-built ones.) See the n8n-workflow-lifecycle skill (references/MCP_ACCESS_PER_WORKFLOW.md).
• The user is right. If they say something's broken, believe them, even if you "know" the workflow is correct. Re-check parameters, fetch the n8n source from github.com/n8n-io/n8n to trace logic, find API docs for missing functions. The n8n-debugging skill walks through this.
• If no skill fits and the task is non-trivial, ask before guessing.
• These skills are opinionated, but considered best practice by the n8n team. The user can override any opinion by editing the SKILL.md. The plugin is just markdown.