agentleFS
Sign inStart free
tmolavitmolavi/n8n-agent-skills/skills/n8n-node-configuration/SKILL.md

n8n-node-configuration

Skill1 starsChanged 3 months agoMITView on GitHub

Use when configuring any n8n node parameters — HTTP Request, Webhook, triggers, Merge, Switch/IF, databases, spreadsheets, AI sub-nodes. Never guess typeVersion or property dependencies; load live schema first.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use n8n-binary-and-data, n8n-code-tool and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • czlonkowskiSkill

    n8n-binary-and-data

    Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send the image", Merge losing binary, or a CDN for chat images. Covers the $binary vs $json split, reading/writing binary, keeping binary alive across transforms with Merge, the agent-tool binary boundary, and the CDN/URL requirement for chat surfaces.

    Also in 4 projects that use this

  • czlonkowskiSkill

    n8n-code-tool

    Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the `query` input, returning a string result, defining an input schema for structured arguments (specifyInputSchema, jsonSchemaExample, DynamicStructuredTool), or troubleshooting errors like \"Wrong output type returned\", \"No execution data available\", \"The response property should be a string, but it is an object\", \"Cannot assign to read only property 'name'\", or an AI agent that refuses to call the tool. Covers the critical differences between Code node and Code Tool: return format (string vs `[{json:{...}}]`), unavailability of `$fromAI`/`$input`/`$helpers` in the Code Tool sandbox, naming rules for AI invocation, and when to use `toolWorkflow`/HTTP Request Tool instead.

    Also in 3 projects that use this

  • AnthropicSkill

    pptx

    Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

    Also in 3 projects that use this

  • NVIDIASkill

    deep-research

    Queue deep, multi-step research and analysis tasks to the DeepAgents worker. Supports execution depth presets, request-specific rubrics, SubAgent delegation, and RubricMiddleware cross-validation.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

  • +3 more from czlonkowski

The file

Create a free account to mount
Files
SKILL.md

n8n Node Configuration

Author: Taghi Molavi

Protocol

  1. Identify node type + required typeVersion for the target n8n version.
  2. Fetch live schema (get_node_types / docs / corpus MCP) — do not invent property names.
  3. Set operation first (many UIs are operation-dependent).
  4. Wire credentials via credential system.
  5. Configure error handling (onError, continue, error output).
  6. Lint the node/workflow.

High-churn gotchas

AreaGotcha
WebhookPath vs production URL; webhookId stability; response mode (last node vs response node); auth
IF v1 vs newerCondition schema changed — lint flags this
MergeDefault 2 inputs; set numberOfInputs for 3+; mode (append/combine/…) changes item shape
SwitchAlways define fallback/default route
HTTP RequestPagination helpers; full response vs body; timeout; binary
Schedule TriggerTimezone + DST
Manual Trigger in active WFSmell — usually wrong for prod
AI Agent clusterSub-nodes connect with ai_* connection types up into the agent, not main only — see n8n-agents
Spreadsheet nodesDeprecated spreadsheetFile → modern file convert nodes

References

  • references/HTTP_AND_WEBHOOK.md
  • references/FLOW_CONTROL.md
  • references/AI_TOPOLOGY.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free