N8n Node Configuration Official
n8nOfficialPublished by n8n
- Skill
- Tool integration
- 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 provides the definitive methodology for configuring n8n nodes. It emphasizes using live tool outputs over memory to determine parameter shapes, ensuring that developers avoid cryptic validation errors caused by evolving node definitions. It covers the full lifecycle of node configuration, from initial discovery and discriminator selection to resource grounding and final validation.
What it does
- Defines the standard workflow for discovering and configuring any n8n node.
- Explains how to use discriminators like resource, operation, and mode to fetch correct parameter shapes.
- Provides patterns for resolving dynamic values using load-options and search methods.
- Outlines the use of validation tools to debug configurations mid-build.
- Offers specific guidance for common node categories including HTTP, AI, and communication nodes.
- Lists anti-patterns to avoid, such as hardcoding credentials or relying on stale node configurations.
When to use it
- When you are adding a new node to an n8n workflow.
- When you encounter validation errors or 'field does not exist' messages.
- When you need to configure complex nodes like AI Agents, Slack, or database connectors.
- When you are unsure about the required parameters for a specific operation.
- When you need to resolve dynamic resource IDs like channel names or database tables.
Advantages
- Prevents common configuration errors by relying on live, canonical schema data.
- Reduces development time by providing a clear, step-by-step configuration flow.
- Ensures workflows are robust and less prone to breaking during n8n version updates.
- Promotes secure practices by enforcing the use of credentials over hardcoded tokens.
Usage examples
- “How do I configure a Slack node to send a message?”
- The agent will guide you to first use get_node_types with the correct resource and operation, then use explore_node_resources to find the correct channel ID, and finally build the configuration using the returned schema.
- “I am getting a validation error on my Postgres node, what should I do?”
- The agent will instruct you to re-fetch the node type with your specific operation (e.g., executeQuery) and verify that all required conditional fields are present, rather than guessing based on previous configurations.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/n8n-io/n8n-node-configuration-official/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip n8n-node-configuration-official.zip -d .agents/skills
Documentation by n8n
n8n Node Configuration
Each n8n node has its own parameter shape, often with conditional fields (parameter X only matters when parameter Y has value Z). Shapes evolve between versions. Guessing produces cryptic validation errors.
Don't guess, use the get_node_types tool.
Non-negotiable
Call get_node_types with discriminators (resource, operation, mode) before configuring a node. Without discriminators you get the generic shape, missing operation-specific parameters and required fields. Build against the exact shape. Don't guess from memory.
The live get_node_types output is the canonical parameter shape. The references in this skill cover patterns, gotchas, security rules, and decision-making (when to use which operation, why credentials over text fields, engine retry caps, etc.) not parameter names or field structures. If a reference example conflicts with what get_node_types returns, trust the tool. Markdown drifts; the type def is generated from the live source.
Never guess resource-locator or load-options values. When get_node_types shows a param with @searchListMethod or @loadOptionsMethod (Slack channels, Sheets tabs/docs, DB tables/columns, model lists, labels), resolve the real value with explore_node_resources (pass a credentialId from list_credentials) and use a returned value. If you already know the exact ID, use it; if several match and intent is ambiguous, ask the user. An invented ID validates but points at nothing. Exception: toolWorkflow.workflowId has no search method, resolve it via search_workflows and use mode: 'id'.
Strong defaults
Configure operation-first. Set
resourceandoperationfirst, and conditional parameters become visible. Most "field doesn't exist" errors are really "you haven't set the parent operation yet."Don't carry parameters across operations. When changing
operation, re-derive from the new shape. Stale parameters from the previous operation trip validation.
The flow for any new node
1. search_nodes(['<capability keyword>'])
→ returns matching node IDs + discriminators
2. Pick the right (resource, operation) for the task.
3. get_node_types([{ name: '...', resource: '...', operation: '...' }])
→ returns exact parameter shape including conditional fields
4. For any RLC / load-options param in that shape, ground the real value:
explore_node_resources({ nodeType, version, methodName, methodType, credentialType, credentialId, currentNodeParameters? })
→ use a returned `value`. Don't invent IDs.
5. Build the node config from that shape.
6. validate_workflow → fix errors.
7. get_workflow_details → inspect the saved config; confirm parameters landed.
8. test_workflow with pinned data → confirm runtime behavior.Skipping any step compounds the next. The most common skip is step 3, leading to "Cannot read property X" errors that are really "you didn't pass the discriminators."
validate_node_config as a side-channel
validate_node_config([{ type, typeVersion, parameters, isToolNode? }]) runs the same Zod schema as validate_workflow on isolated node configs. Schema-level only; doesn't replace validate_workflow (still the publish gate). Cleaner signal for:
Iterating on a single node mid-build. Faster than re-running
validate_workflowper tweak.Small edits to an existing workflow. Wiring unchanged? Check the one node you touched; full validate before publish.
Debugging a misconfigured node. Per-parameter errors with no graph noise.
For tool subnodes (wired via ai_tool), set isToolNode: true so the correct displayOptions branch evaluates.
Operation-aware configuration
Most nodes have a top-level shape like:
{
resource: '<thing being operated on>', // 'message', 'spreadsheet', 'user', etc.
operation: '<verb>', // 'send', 'append', 'lookup', etc.
// ...operation-specific parameters
}The (resource, operation) pair determines what other parameters exist (e.g., Slack (message, send) differs from (user, info)).
Pattern:
Set
resourceandoperationfirst.Re-fetch
get_node_typeswith those discriminators if you didn't initially.Configure the rest from the operation-specific shape.
Property dependencies: the subtle trap
Some parameters depend on others in non-obvious ways:
A field is required only when another field has a specific value.
A field accepts different types depending on a mode.
A field's options come from another field's value.
Examples:
HTTP Request
authentication: 'genericCredentialType'requiresgenericAuthTypeandcredentials, but'predefinedCredentialType'requires a different shape.Postgres
operation: 'executeQuery'requiresquery, whileoperation: 'select'requirestableandcolumns.Slack
messageType: 'block'enables block-builder fields absent frommessageType: 'text'.
Always inspect via get_node_types for the specific operation. Don't reuse a config from a different operation and expect it to validate.
Options-from-another-field is a @loadOptionsMethod: resolve the live options with explore_node_resources (methodType: 'loadOptions'), passing prior selections via currentNodeParameters when the method depends on them (e.g. listing a spreadsheet's tabs needs documentId).
Reference files
Per-category gotchas. Read the file for the node type you're configuring:
| File | When to read |
|---|---|
references/HTTP_NODES.md | Configuring HTTP Request: auth, pagination, query/body parameters, retries |
references/WEBHOOK_NODES.md | Configuring Webhook trigger or Respond to Webhook: body parsing, response shape, async patterns |
references/COMMS_NODES.md | Slack, Gmail, Discord, email: credential types, message shapes, attachments |
references/DATABASE_NODES.md | Postgres, MySQL, Mongo, Supabase: query vs operation, parameter binding, error handling |
references/AI_NODES.md | AI Agent node config knobs: streaming, vision, maxIterations, retries on the model sub-node. Defers design (prompts, tools, memory, structured output) to n8n-ai-nodes-official |
references/TRIGGER_NODES.md | Webhook, Schedule, Manual, Execute Workflow Trigger: input schemas, polling vs realtime |
references/SWITCH_FALLBACK.md | Configuring a Switch node: unnamed outputs / missing fallback silently drop unmatched items |
references/MERGE_NODE.md | Configuring a Merge node, or you see useDataOfInput, numberOfInputs, or branches converging |
Anti-patterns
| Anti-pattern | What goes wrong | Fix |
|---|---|---|
| Building node config from memory of how the node looked last year | Parameter shape has drifted, validation fails with cryptic errors | Always get_node_types per session per node |
Skipping discriminators in get_node_types | Get generic shape, miss operation-specific required fields | Always pass resource + operation (and mode where present) |
| Copying a node config from one operation to another and tweaking | Stale parameters trip validation, and conditional fields don't apply | Re-derive from the new operation's shape |
| Hardcoding tokens / credentials in node text fields | Leaks on export. See n8n-credentials-and-security-official | Always credentials |
Not testing the node with test_workflow after configuring | Runtime errors only surface on real data | Always test with pinned data before publish |
Files
- ATTRIBUTION.mdAdded by AutoGineer868 B
- LICENSELicence file added by AutoGineer11.0 KiB
- SKILL.md7.8 KiB
- references/AI_NODES.md3.2 KiB
- references/COMMS_NODES.md6.1 KiB
- references/DATABASE_NODES.md7.4 KiB
- references/HTTP_NODES.md3.0 KiB
- references/MERGE_NODE.md4.1 KiB
- references/SWITCH_FALLBACK.md904 B
- references/TRIGGER_NODES.md1.8 KiB
- references/WEBHOOK_NODES.md3.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 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/n8n-node-configuration-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 n8n-node-configuration-official.zip