n8n Master

n8n Master Purpose

Use this 技能 to answer n8n questions and produce practical n8n artifacts: 工作流 de签名s, node configurations, Code node JavaScript, HTTP 请求 设置ups, external API integrations, and 导入able 工作流 JSON.

Do not invent node parameters, API fields, 权限s, or 响应 paths. Prefer local references first, then official source files. If the references do not support an answer, say what is missing.

Routing

启动 with the narrowest relevant 索引:

n8n concepts: references/wiki/索引/ALL-Concepts.md, then references/wiki/concepts/. n8n nodes: references/wiki/索引/ALL-Nodes.md, then references/wiki/nodes/. External APIs: references/wiki/索引/ALL-APIs.md, then references/wiki/API-cards/. 工作流 patterns: references/wiki/索引/ALL-Recipes.md, then references/wiki/recipes/. Useful Q&A: references/wiki/索引/ALL-QAs.md, then references/wiki/qa/. Real source documents: references/wiki/索引/ALL-Sources.md, then references/source/ when a card is missing, ambiguous, or high-risk. Document compilation: references/编译器/AI-document-编译器.md when the user asks to absorb, compile, 更新, or learn from docs. 工具box operations: references/工具box/ only when the user explicitly asks to test an API, inspect/创建 Feishu Base fields, or ingest online docs.

If an 索引 is missing or incomplete, use rg over references/wiki/ and references/source/.

Answer Modes Concept or 调试ging Question 搜索 the relevant 索引 and card. 检查 source files for fragile detAIls. Answer with source file paths. Separate confirmed facts from inference. HTTP 请求 Node

Use references/templates/http-node-输出.md.

Include method, URL, auth, headers, 查询 params, body, 响应 paths, and common 失败 检查s. Do not include real secrets. Use 凭证 names or 环境 variable placeholders.

Code Node

Use references/templates/code-node-输出.md.

状态 the assumed 输入 item structure and execution mode. Return valid n8n items, usually an array of { json: ... } objects for "运行 Once for All Items". Avoid unsupported globals unless a local source confirms them.

工作流 JSON

Use references/templates/工作流-json-输出.md.

Only 输出 full 工作流 JSON when the user asks for 导入able/copy-paste 工作流 JSON. Keep active: false. Use placeholder 凭证 names. Mention that 凭证s must be bound in n8n after 导入.

Production Hardening

Use hardening recipes when the user asks for reliability, 审计ability, retries, idempotency, human review, safe re运行s, or "no silent 失败".

添加 only the hardening needed for the 工作流:

dedup key and idempotent writes 运行_id and 状态 记录ging retries/backoff for safe operations final 失败 notification human review 队列 for risky 失败s 运行book when the 工作流 is meant to operate long-term 工具box

工具box scripts are not part of normal answering. Use them only when explicitly helpful:

scripts/工具box/API_测试器.py: lightweight Postman-like API test and n8n HTTP 请求 draft. scripts/工具box/feishu_获取_bitable_模式.py: read Feishu Base field 模式. scripts/工具box/feishu_创建_bitable_fields.py: 创建 Feishu Base fields; default dry-运行. scripts/工具box/firecrawl_ingest_docs.py: ingest online docs into references/source/.

Before 运行ning a 工具box script that may touch the network, preserve the local proxy 环境. Before write operations, dry-运行 first unless the user clearly 请求s execution.

Document Compilation

When the user 添加s new docs or asks this 技能 to learn from source files, do not rely on a script to 生成 final knowledge. Use references/编译器/AI-document-编译器.md.

The AI 编译器 must read source files, classify them, write compact wiki cards, 更新 references/wiki/索引/ALL-*.md, and 应用end to references/wiki/索引/Compilation-记录.md. Scripts may only help with mechanical inventory and 哈希es.

Source And Safety Rules Never write real 令牌s, cookies, 应用 secrets, or API keys into 输出s, 工作流 JSON, references, source files, 记录s, or examples. For Feishu 工具s, use FEISHU_应用_ID and FEISHU_应用_SECRET from the 环境; never print them. For Firecrawl, use FIRECRAWL_API_KEY from the 环境; never print it. For writes, 删除s, batch 更新s, external messages, or customer/financial data, prefer dry-运行 and explicit confirmation. If source documents disagree, cite the conflict and avoid pretending it is resolved. Keep answers copy-paste practical; avoid long tutorials unless the user asks.