Using N8n Skills Official
n8nOfficialPublished by n8n
- Skill
- Meta (authoring, orchestration, planning, memory)
- Automation and integrations
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill serves as the central router and protocol for all n8n-related development. It mandates a strict workflow: identify the task, invoke the relevant specialized skill, and adhere to non-negotiable rules regarding validation, credential management, and tool usage. It acts as the primary interface for the n8n-skills plugin, ensuring that developers prioritize live MCP tools and official documentation over potentially outdated training data. By enforcing these protocols, it prevents common antipatterns and ensures that workflows are built, tested, and published according to current best practices.
What it does
- Routes users to the correct specialized n8n skill based on the task.
- Enforces a mandatory validation-before-publish protocol.
- Provides a centralized index of all available n8n MCP tools and their functions.
- Standardizes the use of n8n credentials and user preferences.
- Prevents common development antipatterns through strict rule enforcement.
- Ensures developers use live MCP tools for accurate node and parameter information.
When to use it
- At the start of every n8n-related session.
- Before performing any n8n action, including SDK coding or node configuration.
- When unsure which specific n8n skill applies to a task.
- When needing a quick reference for n8n MCP tool capabilities.
- Before publishing any workflow or agent to production.
Advantages
- Ensures consistent adherence to evolving n8n best practices.
- Reduces errors caused by relying on outdated model training data.
- Streamlines the development process by providing a clear, structured protocol.
- Promotes the use of reusable components and proper error handling.
- Centralizes configuration and preference management across sessions.
Usage examples
- “I need to build a new workflow to sync data between two services.”
- The agent will invoke this meta-skill to route you to the appropriate lifecycle and node configuration skills, ensuring you follow the correct design and validation steps.
- “How do I find out what a specific n8n node does?”
- The agent will guide you to use the get_node_types MCP tool rather than guessing, ensuring you have the exact parameter definitions.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/n8n-io/using-n8n-skills-official/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip using-n8n-skills-official.zip -d .agents/skills
Documentation by n8n
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.
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.
Validate AND verify before publishing.
validate_workflowbeforepublish_workflow, andget_workflow_detailsafter every create or update to check theconnectionsobject. Validation alone misses many issues documented in the skills that will silently break workflows.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-official.
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_workflow_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-official, n8n-expressions-official, n8n-error-handling-official, and n8n-workflow-lifecycle-official. 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-official.Anything reusable becomes a stateless sub-workflow. Search existing ones via
search_workflows({ tags: ['subworkflow'] })before building. Seen8n-subworkflows-official.n8n preferences belong in n8n, not in harness memory. When the user states a durable n8n preference, save it with
save_user_preferencerather than writing it to CLAUDE.md, AGENTS.md, or your own memory: the n8n store is read by the n8n assistant and every AI tool on the instance, so a preference parked in harness memory is invisible outside this session. Read what's already saved once before you start changing things (get_user_preferences) and apply it across the task. If the user would rather keep their n8n preferences in their own context file, that's their call: follow it. See "User preferences" below.
<!-- TEMPORARY: Gateway credits is n8n Cloud only for now and the coverage may expand; revisit this default and the cloud-only caveat when that changes. -->
Prefer Gateway credits when the user has no credential preference. For nodes it covers (check
list_n8n_gateway_services), n8n supplies the managed credential, so there's no setup step, much easier than the user provisioning their own. n8n Cloud only for now. Seen8n-credentials-and-security-official.
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-official. 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-official. 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-official. 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-official and walk VALIDATION_CHECKLIST.md section 2 (the antipattern scan). Validation passing is necessary, not sufficient. |
| "The user wants an agent, I'll wire a Chat Trigger to an AI Agent node" | Invoke n8n-agents-official. "Agent" or "assistant" means a first-class n8n Agent unless one of its listed limits applies. |
| "The Agent validates, I'll publish it" | Don't. A built Agent is a draft; publish only on the user's explicit OK. Channels go live with it. |
| "I'll map the webhook field straight into the Agent's tool input" | Invoke n8n-agents-official references/TOOLS.md. Agent tool expressions only see the model's arguments; exact mapping stays in a workflow. |
| "The agent is wired up, the tool descriptions look fine" | Invoke n8n-ai-nodes-official references/TOOLS.md (AI Agent node) or n8n-agents-official references/TOOLS.md (first-class Agent). 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-official. 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-official 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. |
| "This section's big, I'll pull it into a sub-workflow" | If it's only to tidy the canvas (not reuse/isolation/testing), a node group is lighter, faster, and simpler: keep it inline and group it. Extract to a sub-workflow only for reuse, isolation, or an agent tool. See n8n-workflow-lifecycle-official references/NODE_GROUPS.md. |
| "I should ask the user what their credential is named" | Don't. The string in newCredential('Label') is cosmetic. See n8n-credentials-and-security-official. |
| "I'll note that preference in CLAUDE.md / AGENTS.md / my memory" | If it's about how they work in n8n, offer save_user_preference instead, where the n8n assistant and their other AI tools can see it too. Harness memory is for your own operating notes. |
| "The user mentioned data analysis, I'll write Python" | Invoke n8n-code-nodes-official. Default is JavaScript. Python only when explicitly asked. |
| "I'll add a Loop Over Items here to process each row" | Invoke n8n-loops-official. Default per-item iteration probably handles it without a Loop Over Items node. |
| "Date math, I'll use a DateTime node" | Invoke n8n-expressions-official. DateTime nodes are almost always wrong. |
| "I'll wrap this in a Merge with 3 sources" | Invoke n8n-node-configuration-official 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-official 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-official and n8n-subworkflows-official (mode: 'each' + waitForSubWorkflow: false). |
| "User said which project, I'll just build it" | Invoke n8n-workflow-lifecycle-official. Project is not folder. Ask about folder placement BEFORE building. create_folder works on a registered instance. If the folder tools are absent, the instance isn't registered, and folders are blocked in the UI too, so the user must register it first (free Community-edition registration in Settings), not create the folder by hand. |
"I'll just run test_workflow to see what happens" | Invoke n8n-workflow-lifecycle-official 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-official | Starting, designing, organizing, or finishing a workflow. Covers sticky-note conventions, descriptions that capture the why, naming, validation checklist, folder management, MCP-access-per-workflow gotcha |
n8n-subworkflows-official | Anything reusable, multi-step builds, or the user mentions reuse. Search before building, stateless patterns, tag-based discovery convention |
n8n-extending-mcp-official | You need capabilities the MCP doesn't natively provide. Wrap n8n APIs as workflow tools, with user permission |
n8n-expressions-official | Writing {{}}, $json, $node, expression errors. Luxon for dates, indented multi-line, prefer expressions over extra nodes |
n8n-node-configuration-official | Configuring any node. Operation-aware, property dependencies, never assume parameters |
n8n-code-nodes-official | User reaches for a Code node, or custom logic is needed. Decision tree, JavaScript patterns when truly required |
n8n-loops-official | Multi-item data, batching, paginated APIs, "for each" or "loop over" mentions. Default per-item iteration, executeOnce, Loop Over Items, HTTP pagination |
n8n-agents-official | The user wants an agent, assistant, or bot, or any Agent MCP tool. Agent vs workflow vs AI Agent node, Agent config, tools, approvals, skills, sub-agents, knowledge, memory and sessions, channels, tasks, Message an Agent, reading sessions |
n8n-ai-nodes-official | AI inside a workflow: AI Agent node, Text Classifier, Information Extractor, chains, RAG, structured output, AI media. Chat bot workflows on Slack / Discord / Teams / Telegram |
n8n-error-handling-official | 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-official | Any auth, API key, or token mention. Credential system, custom credentials, HTTP Request with official creds |
n8n-binary-and-data-official | Files, images, attachments. Binary handling patterns, agent-tool boundary, CDN requirement for chat surfaces |
n8n-data-tables-official | 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-official | 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.
User preferences
Cross-client store of how the user works in n8n, read by the n8n assistant and every AI tool connected to the instance. Scopes: instance (admin-set, everyone), user (the caller, every project), project (one team project). get_user_preferences from n8n 2.41.0, the three write tools from 2.42.0.
<!-- TEMPORARY: preference tools are rolling out behind a PostHog flag. Drop the absent-tool fallback below once they ship to all instances. -->
If these tools aren't in your tool list, either the instance predates them or the rollout flag is off, or the MCP connection wasn't granted the aiPreference:read / aiPreference:write scopes. Either way, ask the user instead, and offer harness memory as the fallback for a preference worth keeping.
| Tool | What it does |
|---|---|
get_user_preferences | Read instance, user, and project preferences (instance first). Read once before you start changing things and apply it across the task; re-read only if the user says they changed something. An error in the result means preferences are unknown, not absent, so don't build as if none were saved. projectId narrows to one project. |
save_user_preference | Save one durable preference (max 2000 chars). Only for a way-of-working preference the user actually stated ("always add an error workflow", "name nodes in English"), never a one-off task instruction ("make this one a POST") and never one you inferred. Read preferences first: an exact duplicate is refused, and a near-duplicate should be an update_user_preference instead. Saves immediately with no confirmation step, so report the exact text saved plus the settings link from the result in the same turn. |
update_user_preference | Change a saved preference's text, its scope, or both. Only move scope when the user asks; project needs a projectId. |
undo_user_preference | Remove a preference saved through a connected AI tool for this user. One written in n8n settings, or scoped to a project or the instance, is refused: the user removes those in settings. |
When a saved preference conflicts with what the user asks for right now, follow the user and say which preference you set aside.
Workflow management
| Tool | What it does |
|---|---|
search_workflows | Search workflows across the instance by query (substring on name/description) and/or tags (exact tag names, AND semantics: must have all). The primary cross-workflow discovery 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 | Resolve a folder name to its ID (full path). Folder tools require a registered instance (free Community registration); the skills assume one. |
create_folder | Create a folder, optionally nested. |
update_folder | Rename or move a folder within its project. |
move_workflows_to_folder | Move workflows into a folder (or to project root). |
search_projects | Resolve a project name to its ID. Read-only. |
list_workflow_tags | List all workflow tags (with usageCount per tag). Check the instance's tag vocabulary before tagging or filtering, so you reuse exact names. Tags are attached/detached via update_workflow addTags/removeTags; there's no tag rename/delete tool. |
archive_workflow / publish_workflow / unpublish_workflow | Soft-delete / activate / deactivate. Validate before publish. publish_workflow takes an optional versionId to re-publish a specific version. |
search_workflow_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_workflow_execution. |
Workflow building
| Tool | What it does |
|---|---|
get_workflow_sdk_reference | Fetch the n8n Workflow SDK reference. Read this before writing workflow code. Sections: patterns, patterns_detailed, expressions, functions, rules, import, guidelines, design, groups (n8n 2.33.0+), all. |
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. |
explore_node_resources | Resolve the real values behind resource-locator (@searchListMethod) and load-options (@loadOptionsMethod) params: Slack channels, Sheets tabs/docs, DB tables/columns, model lists, labels. Needs a credentialId from list_credentials (pass currentNodeParameters for dependent lookups). Call after get_node_types to ground dropdown values instead of inventing IDs. |
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 (max 100): node/connection CRUD, setNodeCredential, setNodeSettings (per-node onError/retry/executeOnce), setWorkflowSettings (errorWorkflow, timezone, callerPolicy, timeouts, save-data policies; n8n 2.29.0+), setNodeGroups/addNodeGroup/removeNodeGroup/updateNodeGroup (canvas grouping), setWorkflowMetadata, addTags/removeTags (auto-create unknown names). All-or-nothing except the four group ops: an invalid one is skipped into skippedOperations and the batch still saves, and unrelated edits can delete an existing group into removedGroups. Read both. 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. |
list_n8n_gateway_services | List node/credential types the platform can supply managed credentials for (Gateway credits coverage), so the user can skip credential setup for them. |
Workflow testing & execution
| Tool | What it does |
|---|---|
prepare_workflow_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-official references/TESTING.md. |
execute_workflow | Production execution with the real trigger. Wire error handling first. Same side-effect rules as test_workflow. executionMode is required — use "manual" for testing or validating the current workflow (including tests against live external services), and "production" only when intentionally running the published workflow as a live execution. Structured inputs for chat/form/webhook triggers. Returns an execution ID immediately without waiting; poll get_workflow_execution for results. |
get_workflow_execution | Fetch an execution by executionId + workflowId (both required). Metadata only by default; set includeData: true (optionally nodeNames, truncateData) for node inputs/outputs. |
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. |
get_data_table_rows | Read rows (optional filter/sort/pagination). |
Version history
| Tool | What it does |
|---|---|
get_workflow_history | List a workflow's saved versions, newest first (n8n 2.29.0+). |
get_workflow_version | Fetch a past version's full content by versionId. |
get_workflow_versions_diff | Diff two saved versions: nodes/connections added, removed, modified. |
restore_workflow_version | Re-apply a past version as the current draft (records a new history entry). |
Building n8n Agents
<!-- TEMPORARY: revisit when the Preview tag is removed from Agents in the UI, and when Agents are declared ready for Enterprise. -->
n8n Agents are generally available. The UI shows a Preview tag because they change often and some features you might expect aren't there yet. They aren't ready for Enterprise yet: an Enterprise instance may have them enabled, but don't assume it. If create_agent isn't in your tool list, Agents aren't enabled on this instance; say so and offer a workflow instead.
A first-class n8n Agent is configured as JSON through these tools, never with Workflow SDK code. Invoke n8n-agents-official before the first call; it decides Agent vs workflow and covers every tool below. The AI Agent node inside a workflow is n8n-ai-nodes-official. Agent conversations aren't workflow executions: get_workflow_execution only sees workflows an Agent called as tools.
| Tool | What it does |
|---|---|
get_agent_builder_reference | Required reference for Agent config and mutate_agent ops. Read before building. |
discover_agent_assets | Find models, chat integrations, attachable workflows, sub-agents, or MCP servers to reference. |
search_agents | Find existing Agents; also discovers sub-agents to attach. |
get_agent | Read a draft's config, resources, runnable state, and configHash. Call before mutate_agent. |
list_agent_versions | List an Agent's publish history, newest first. |
create_agent | Create a draft (optional initial model/credential/instructions). Returns the editor URL. Include memory: { enabled: true, storage: "n8n" } or the Agent is stateless. |
mutate_agent | Apply one config/skill/task/custom-tool change, using the latest configHash. |
verify_agent_mcp_server | Test an MCP server + credential and return its tools. Call before adding an mcpServers entry. |
update_agent_integration | Connect or disconnect a Slack, Telegram, or Linear channel. |
validate_agent | Validate the draft, its references, and credential access. Required before publish. |
call_agent | Test the draft via built-in Preview chat. Uses real tools/credentials; side effects possible. |
publish_agent | Publish a valid draft; activates its tasks and integrations. |
unpublish_agent | Unpublish; stops live tasks and integrations. |
revert_agent | Restore a draft from a published version. |
delete_agent | Permanently delete an Agent and its resources. |
The protocol, in order
For any n8n task:
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.
Invoke the skill via the Skill tool before the first MCP call. Don't call n8n MCP tools blind.
Read saved preferences once before you start changing things (
get_user_preferences, when present) and apply them across the task.Read the SDK reference once per session before writing workflow code (
get_workflow_sdk_reference). The most efficient way to avoid SDK-shape mistakes.Get node types before configuring any node (
get_node_types). Guessing parameter names creates invalid workflows, sometimes silently.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.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: report each skill exactly as the Skill tool names it, keeping the
-officialsuffix:plugin:skill-officialwhen plugin-namespaced, else bareskill-official. The suffix marks these as ours (vs other n8n packs); the plugin prefix marks plugin vs raw-skill usage.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-official 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-officialskill (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/n8nto trace logic, find API docs for missing functions. Then8n-debugging-officialskill 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, or for one instance by saving an n8n preference. A saved preference beats a default here. The plugin is just markdown.
Files
- ATTRIBUTION.mdAdded by AutoGineer856 B
- LICENSELicence file added by AutoGineer11.0 KiB
- SKILL.md27.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for describing the origin of the Work and
reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may accept and charge a
fee for accepting support, warranty, indemnity, or other liability
obligations and/or rights consistent with this License. However, in
accepting such obligations, You may act only on Your own behalf
and on Your sole responsibility, not on behalf of any other
Contributor, and only if You agree to indemnify, defend, and hold
each Contributor harmless for any liability incurred by, or claims
asserted against, such Contributor by reason of your accepting any
such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 n8n GmbH
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the License for the specific language governing
permissions and limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key, Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- n8n
- Publisher
- n8n (Official)
- Source
- n8n-io/skills · skills/using-n8n-skills-official · commit 27b6b9f
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by n8n or n8n.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download using-n8n-skills-official.zip