What makes n8n Master notable?

3.4K downloads. Trust evidence available

How should n8n Master be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

n8n Master

Answers n8n questions and builds n8n workflows, node configurations, Code node JavaScript, HTTP Request setups, API integrations, toolbox-assisted API tests,... Skill: n8n Master Owner: billzhuang6569 Summary: Answers n8n questions and builds n8n workflows, node configurations, Code node JavaScript, HTTP Request setups, API integrations, toolbox-assisted API tests,... Tags: api:1.0.2, automation:1.0.2, feishu:1.0.2, lark:1.0.2, latest:1.0.2, n8n:1.0.2, workflow:1.0.2 Version history: v1.0.2 | 2026-05-17T09:58:36.901Z | user Wiki-only release: remove raw source corpora while

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

3.4k

Updated

Oct 9, 2026

Version

1.0.2

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 3.4K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 3.4K downloadsadoption · observed Oct 9, 2026
Latest release: 1.0.2release · observed May 17, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: medium.

clawhub skill install s17d7mdp9nn22faex2cbvcrzy183wr4c:n8n-master

Setup complexity is MEDIUM. Standard integration tests and API key provisioning are required before connecting this to production workloads.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-billzhuang6569-n8n-master/snapshot"

Documentation

CLAWHUB

79,904 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

references/compiler/ai-document-compiler.md

# AI Document Compiler

Use this prompt when the user asks to add, absorb, compile, update, or reorganize documentation for `n8n-master`.

The compiler is an AI workflow. Scripts may create inventories and hashes, but they must not decide what a document means or silently generate final wiki knowledge.

## When To Use

- The user adds new docs under `references/source/`.
- The user asks to ingest online API docs with Firecrawl and then compile them.
- The user asks why a card is missing and wants the Skill to learn from source docs.
- Official docs were refreshed and the wiki layer needs updating.
- A real Q&A revealed a reusable node pattern, API detail, or workflow recipe.

## Source First

Before writing any wiki file:

1. Identify the exact source files.
2. Read enough of the source to understand the object model, limits, parameters, and examples.
3. Record the source path in the compiled card.
4. If source material is unclear, mark the compiled card `status: draft` and name the uncertainty.
5. Never invent node parameters, API fields, credentials, permissions, response paths, or limits.

## Classification

Classify each source into one primary output type:

| Source kind | Compile to | Examples |
|---|---|---|
| n8n node docs | `references/wiki/nodes/` | HTTP Request, Webhook, Google Sheets, Slack Trigger |
| n8n concept docs | `references/wiki/concepts/` | expressions, item linking, binary data, queue mode |
| external API docs | `references/wiki/api-cards/` | Feishu Base add record, Stripe create payment link |
| reusable workflow | `references/wiki/recipes/` | webhook to Base, API pagination, human review queue |
| useful Q&A | `references/wiki/qa/` | real solved issue, verified troubleshooting answer |
| raw-only material | keep in `references/source/` | release notes, large archive, docs not yet understood |

If a document covers multiple concerns, write one primary card and link to follow-up cards instead of stuffing everything into one long file.

## Card Rules

Every compiled wiki card should include:

Body order:

1. `# Title`
2. `## 何时读取`
3. `## 核心要点`
4. Task-specific sections:
- Node card: parameters, operations, credentials, input/output, common issues.
- API card: endpoint, auth, params, body, n8n HTTP Request config, response paths, permissions/pitfalls.
- Concept card: definition, decision rules, examples, common mistakes.
- Recipe: node chain, data contract, key expressions, error handling, source cards.
5. `## 来源`

Keep cards compact. Link back to source files for full detail.

## Index Updates

After writing or changing cards, update the relevant index:

- `references/wiki/index/ALL-Nodes.md`
- `references/wiki/index/ALL-Concepts.md`
- `references/wiki/index/ALL-APIs.md`
- `references/wiki/index/ALL-Recip

references/compiler/card-templates.md

# Compiler Card Templates

## Node Card

```markdown
---
title: Node name
type: node-card
status: draft
updated: YYYY-MM-DD
source: official-doc
tags: [n8n, node]
---

# Node name

## 何时读取

...

## 核心要点

- ...

## 关键参数 / 操作

- ...

## n8n 使用建议

- ...

## 常见坑

- ...

## 来源

- Local: `references/source/...`
```

## API Card

````markdown
---
title: Platform API name
type: api-card
status: draft
updated: YYYY-MM-DD
source: source-doc
tags: [api, platform, n8n]
---

# Platform API name

## Endpoint

- Method:
- URL:

## Auth / Headers

- ...

## Params

- Path:
- Query:

## Body

```json
{}
```

## n8n HTTP Request

- Method:
- URL expression:
- Headers:
- Body Content Type:
- Body:

## Read Response

- ...

## Permissions / Pitfalls

- ...

## Source

- Local: `references/source/...`
````

## Concept Card

```markdown
---
title: Concept
type: concept-card
status: draft
updated: YYYY-MM-DD
source: official-doc
tags: [n8n, concept]
---

# Concept

## 何时读取

...

## 定义

...

## 决策规则

- ...

## 示例

...

## 常见坑

- ...

## 来源

- Local: `references/source/...`
```

## Recipe

````markdown
---
title: Recipe
type: recipe
status: draft
updated: YYYY-MM-DD
source: compiled
tags: [n8n, workflow]
---

# Recipe

## 何时读取

...

## 节点链路

```text
Trigger -> ...
```

## 数据契约

- Input:
- Output:

## 关键配置

- ...

## 错误处理

- ...

## 来源

- Local: `references/wiki/...`
- Local: `references/source/...`
````

references/templates/code-node-output.md

# Code Node Output

Use this shape when producing n8n Code node JavaScript.

````markdown
## 输入假设

- Mode:
- Incoming items:
- Required fields:

## Code node JavaScript

```javascript
const items = $input.all();

return items.map((item) => ({
  json: {
    ...item.json,
  },
}));
```

## 输出结构

```json
[
  {
    "json": {}
  }
]
```

## 注意事项

- Keep secrets in credentials or environment variables.
- Return valid n8n items.
- Preserve item pairing when downstream nodes rely on per-item mapping.
````

references/templates/http-node-output.md

# HTTP Request Node Output

Use this shape when producing n8n HTTP Request node guidance.

```markdown
## HTTP Request 节点配置

| 配置项 | 值 |
|---|---|
| Method |  |
| URL |  |
| Authentication |  |
| Headers |  |
| Query Params |  |
| Body Content Type |  |
| Body |  |
| Response Options |  |

## n8n 表达式

```text
{{ $json.example }}
```

## 返回值读取

- `{{$json...}}`

## 调试检查

- 状态码：
- 权限：
- 字段类型：
- 分页：
- 幂等：

## 来源

- `references/...`
```

references/templates/runbook-template.md

# n8n Workflow Runbook Template

## Purpose

- What the workflow does and why it exists.

## Triggers

- Cron / Webhook / Manual
- Schedule, timezone, and expected frequency.

## Inputs

- Source systems and credentials. Reference env vars or credential names only.

## Outputs

- Where results go, including naming and retention.

## Idempotency

- Dedup key:
- Safe rerun behavior:

## Error Handling

- Retry policy:
- Failure notifications:
- Review queue link/location:

## Logging And Audit

- Run ID:
- What is logged per run:
- Where logs are stored:

## Operational Checks

- Expected counts/thresholds:
- Stop-the-line conditions:

Github ReposUpdated 2h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.