KOwl64

n8n workflow automation

AI 智能体v1.0.0
作者:KOwl64更新于 2026-05-11n8n-workflow-automation@clawhub_kowl64/n8n-workflow-automation
Agent 框架任务自动化工作流编排#N8n#Workflow Automation#Json

据 AlphaMoat 统计,截至 2026-10,n8n workflow automation 累计下载 48,550 次、获 162 个星标,按累计下载量在本次参与排名的 10,914 个 AI 技能中排名第 510 位,在「AI 智能体」分类(1,632 个)中排名第 101 位。

列表默认按累计下载量排序,也可按星标排序;详情页排名按累计下载量计算。

累计下载
4.9万
星标
162
全站下载量排名
#510
全站前 5% · 「AI 智能体」前 7%
平台累计下载星标评论
ClawHub ↗3.5万1624
SkillHub ↗4.9万162—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

输出的工作流强调稳健的触发器、幂等、错误处理、日志、重试与人工复核队列,并附一份 runbook 说明。适合需要可审计的自动化流程;如果只想写代码、不打算用 n8n,则不属于本技能范围。

资料发布于 2026-10-27

可以用来做什么

  • 把一段手工流程改写成带重试的 n8n 工作流
  • 为失败任务加人工复核队列

什么时候用

  • 需要可审计、可回放的自动化时
  • 流程需要幂等以避免重复写入时

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

把这个审批流程写成 n8n 工作流,带错误处理和重试
让这条流程重复执行也不会产生重复记录

月度数据趋势

累计下载4.9万
2.5万3.8万5.0万2026-03 · 累计下载 2.7万2026-05 · 累计下载 3.3万2026-06 · 累计下载 3.4万2026-07 · 累计下载 3.5万2026-08 · 累计下载 3.5万2026-09 · 累计下载 3.7万2026-10 · 累计下载 4.9万26-0326-0926-10
星标162
1181421652026-03 · 星标 1212026-05 · 星标 1502026-06 · 星标 1582026-07 · 星标 1622026-08 · 星标 1622026-09 · 星标 1622026-10 · 星标 16226-0326-0926-10

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。 该技能有同名的其他版本,调整前的数据归属当前下载量最大的这一个。

月份累计下载环比星标
2026-104.9万—162
2026-093.7万—162
2026-083.5万+1.1%162
2026-073.5万+2.2%162
2026-063.4万+2.7%158
2026-053.3万—150
2026-032.7万—121

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

3.9 KB · ClawHub v1.0.0
---
name: n8n-workflow-automation
description: Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queues. Use when you need an auditable automation that won’t silently fail.
---

# n8n workflow automation with retries, logging, and review queues

## PURPOSE
Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queues.
展开全部(共 95 行)
## WHEN TO USE
- TRIGGERS:
  - Build an n8n workflow that runs every Monday and emails the compliance summary.
  - Add error handling and retries to this workflow, plus a review queue for failures.
  - Create a webhook workflow that logs every run and writes a status row to a tracker.
  - Make this n8n flow idempotent so it does not duplicate records when it reruns.
  - Instrument this workflow with audit logs and a human approval step.
- DO NOT USE WHEN…
  - You need code-only automation without n8n (use a scripting/CI skill).
  - You need to bypass security controls or hide audit trails.
  - You need to purchase or recommend prohibited items/services.

## INPUTS
- REQUIRED:
  - Workflow intent: trigger type + schedule/timezone + success criteria.
  - Targets: where to write results (email/Drive/Sheet/DB) and required fields.
- OPTIONAL:
  - Existing n8n workflow JSON to modify.
  - Sample payloads / example records.
  - Definition of dedup keys (what makes a record unique).
- EXAMPLES:
  - Cron: Monday 08:00 Europe/London; send summary email + Drive upload
  - Webhook: receive JSON; route to folders

## OUTPUTS
- Default (read-only): a workflow design spec (nodes, data contracts, failure modes).
- If explicitly requested: `workflow.json` (n8n importable JSON) + `runbook.md` (from template).
Success = workflow is idempotent, logs every run, retries safely, and routes failures to a review queue.


## WORKFLOW
1. Clarify trigger:
   - Cron/webhook/manual; schedule/timezone; concurrency expectations.
2. Define data contract:
   - input schema, required fields, and validation rules.
3. Design idempotency:
   - choose dedup key(s) and storage (DB/Sheet) to prevent duplicates on retries.
4. Add observability:
   - generate `run_id`, log start/end, store status row and error details.
5. Implement error handling:
   - per-node error branches, retry with backoff, and final failure notification.
6. Add human-in-the-loop (HITL) review queue:
   - write failed items to a queue (Sheet/DB) and require approval to reprocess.
7. “No silent failure” gates:
   - if counts/thresholds fail, stop workflow and alert.
8. Output:
   - If asked for JSON: produce importable n8n workflow JSON + runbook.
9. STOP AND ASK THE USER if:
   - destination systems are unknown,
   - no dedup key exists,
   - credential strategy (env vars) is not specified,
   - the workflow needs privileged access not yet approved.


## OUTPUT FORMAT
If outputting **n8n workflow JSON**, conform to:

```json
{
  "name": "<workflow name>",
  "nodes": [ { "name": "Trigger", "type": "n8n-nodes-base.cron", "parameters": {}, "position": [0,0] } ],
  "connections": {},
  "settings": {},
  "active": false
}
```

Also output `runbook.md` using `assets/runbook-template.md`.


## SAFETY & EDGE CASES
- Read-only by default; only emit workflow JSON when explicitly requested.
- Do not include secrets in JSON; reference env vars/credential names only.
- Include audit logging + failure notifications; avoid workflows that can silently drop data.
- Prefer least privilege: call only required APIs and minimize scopes.


## EXAMPLES
- Input: “Cron every Monday, email compliance summary, retry failures.”  
  Output: Node map + `workflow.json` with Cron → Fetch → Aggregate → Email, plus error branches to review queue.

- Input: “Webhook that logs runs and writes status row.”  
  Output: Webhook → Validate → Process → Append status row; on error → log + notify + queue.

「AI 智能体」分类下的热门技能

KOwl64 的其他技能

数据月份:2026-10 · 下载/星标数聚合自公开技能注册库(ClawHub、SkillHub),按月更新。口径说明见数据方法。