Token导航 LogoToken导航

Agent Skill · 研究检索

n8n-automation-berzaf(N8N 自动化 Berzaf)

n8n-automation-berzaf 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

n8n-automation-berzaf 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 20,947。

总安装 5,033周安装 214GitHub Stars 公开资料未说明下载 1,763核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:n8n-automation-berzaf(N8N 自动化 Berzaf)
来源仓库:https://github.com/beraiautomation/n8n-automation-berzaf
安装命令:
openclaw skills install n8n-automation-berzaf
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install n8n-automation-berzaf

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

n8n-automation-berzaf 通过自然语言触发 n8n 自动化工作流程。支持潜在客户培育、邮件序列与社交媒体发布。适用于营销与销售团队的流程自动化需求。需提前配置好 n8n 实例与相关服务连接器。建议设置执行日志与异常告警机制。

n8n-automation-berzaf 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install n8n-automation-berzaf;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

n8n-automation-berzaf 怎么安装?

在终端执行 openclaw skills install n8n-automation-berzaf。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

n8n-automation-berzaf 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

n8n-automation-berzaf 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

n8n-automation-berzaf 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

n8n-automation-berzaf 用的人多吗?

公开数据是累计安装 5,033 次,近一周安装 214 次,下载 1,763 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

n8n-automation-berzaf 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
n8n-automation-berzaf

N8N 自动化 Berzaf · 本页

5,033—接触敏感数据MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
n8n-automation
description
>
version
1.0.0
author
berzaf
metadata
openclaw
emoji
⚡
requires
env
bins
install
kind
manual
label
Set N8N_WEBHOOK_BASE_URL and N8N_API_KEY in your environment

⚡ n8n Automation Skill

Overview

This skill connects your OpenClaw agent directly to your n8n instance so you can trigger powerful multi-step automations using plain natural language — no coding required at runtime.

What makes this skill different: It does not just call webhooks. It confirms before acting, validates inputs, reports results, handles errors gracefully, and remembers what was last triggered so you can easily repeat or modify runs.


Setup (One Time)

Before using this skill, export these two environment variables in your terminal or add them to your shell profile:

export N8N_WEBHOOK_BASE_URL="https://your-n8n-instance.com/webhook"
export N8N_API_KEY="your-n8n-api-key-here"

Then restart your OpenClaw gateway:

openclaw gateway restart

You will know setup worked when you type:

"n8n status"

And the agent responds with your instance URL confirmed.


Trigger Phrases

You can trigger this skill with any of these natural language phrases:

  • "trigger n8n [workflow name]"
  • "run automation for [contact/task]"
  • "send [email type] to [name]"
  • "post to social: [content]"
  • "update CRM for [name]"
  • "follow up with [name] from [meeting]"
  • "check competitors"
  • "send invoice reminder to [client]"
  • "n8n status" — checks your instance is reachable

Workflow 1 — Lead Nurture Email Sequence

What it does: Triggers a multi-step email sequence in n8n for a new lead. Sends welcome email on Day 1, value email on Day 3, case study on Day 7, and soft pitch on Day 14. All personalized.

Trigger examples:

  • "Send lead nurture to John Smith at john@company.com"
  • "Start nurture sequence for sarah@startup.io, she found us via YouTube"
  • "Add Maria to lead nurture, source is LinkedIn"

Required fields:

  • first_name
  • email
  • source (where they came from — optional but improves personalization)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/lead-nurture

Payload sent:

{
  "first_name": "string",
  "email": "string",
  "source": "string",
  "triggered_at": "ISO timestamp",
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "queued", "sequence_id": "..." }


Workflow 2 — Social Media Auto-Post

What it does: Takes content you describe or provide and posts it to your connected social platforms via n8n. Supports LinkedIn, X (Twitter), Instagram caption, Facebook, and Threads.

Trigger examples:

  • "Post to social: Just launched my new n8n + OpenClaw skill on ClawHub!"
  • "Post this to LinkedIn and X: [your content]"
  • "Schedule social post for tomorrow 9am: [content]"

Required fields:

  • content (the post text)
  • platforms (list: linkedin, x, instagram, facebook, threads)
  • schedule_time (optional — defaults to immediate)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/social-post

Payload sent:

{
  "content": "string",
  "platforms": ["linkedin", "x"],
  "schedule_time": "ISO timestamp or null",
  "hashtags": ["optional", "array"],
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "posted", "post_ids": {...} }


Workflow 3 — Meeting Follow-Up

What it does: After a meeting, triggers n8n to send a personalized follow-up email with meeting summary, action items, and next steps. Also optionally creates a follow-up task in your CRM.

Trigger examples:

  • "Send follow-up to Mike from today's discovery call"
  • "Follow up with the Acme team, meeting was about their automation needs"
  • "Post-meeting email to jennifer@client.com, action items: send proposal, book next call"

Required fields:

  • contact_name
  • contact_email
  • meeting_topic
  • action_items (list of strings)
  • next_step (optional)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/meeting-followup

Payload sent:

{
  "contact_name": "string",
  "contact_email": "string",
  "meeting_topic": "string",
  "action_items": ["item1", "item2"],
  "next_step": "string or null",
  "meeting_date": "ISO date",
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "sent", "email_id": "..." }


Workflow 4 — CRM Contact Update

What it does: Updates a contact record in your CRM (works with HubSpot, GoHighLevel, Airtable, Google Sheets CRM, or any CRM connected to your n8n). Logs notes, updates status, and sets follow-up date.

Trigger examples:

  • "Update CRM for John Smith — he said he's ready to buy next month"
  • "Mark Sarah as hot lead, she opened all emails"
  • "Log call with Mike: discussed pricing, follow up in 2 weeks"

Required fields:

  • contact_name or contact_email
  • notes
  • status (lead / warm / hot / closed-won / closed-lost)
  • follow_up_date (optional)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/crm-update

Payload sent:

{
  "contact_name": "string",
  "contact_email": "string or null",
  "notes": "string",
  "status": "string",
  "follow_up_date": "ISO date or null",
  "triggered_by": "openclaw",
  "logged_at": "ISO timestamp"
}

Expected n8n response: { "status": "updated", "contact_id": "..." }


Workflow 5 — Competitor Monitor Report

What it does: Triggers n8n to scrape and compare your top competitors — pricing pages, new blog posts, social activity, job postings (signals of growth or product changes). Returns a formatted report directly in your chat.

Trigger examples:

  • "Check competitors"
  • "Run competitor report for [your niche]"
  • "What changed on my competitors' sites this week?"

Required fields:

  • None (uses your pre-configured competitor list in n8n)
  • Optional: niche or specific competitor URL to add

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/competitor-monitor

Payload sent:

{
  "include_niche": "string or null",
  "add_competitor_url": "string or null",
  "report_type": "full or summary",
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "complete", "report": "markdown string" }

Display the report content directly in chat formatted as markdown.


Workflow 6 — Invoice Reminder

What it does: Sends a polite, personalized invoice reminder to a client. Supports first reminder, second nudge, and final notice tones. Logs the outreach attempt in your CRM automatically.

Trigger examples:

  • "Send invoice reminder to Acme Corp, invoice #1042, $2,500 due"
  • "Second reminder to mike@client.com for invoice 203"
  • "Final notice to sarah@company.com, overdue 30 days"

Required fields:

  • client_name
  • client_email
  • invoice_number
  • amount
  • due_date
  • reminder_type (first / second / final)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/invoice-reminder

Payload sent:

{
  "client_name": "string",
  "client_email": "string",
  "invoice_number": "string",
  "amount": "number",
  "due_date": "ISO date",
  "reminder_type": "first | second | final",
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "sent", "email_id": "..." }


Workflow 7 — YouTube / Content Repurpose

What it does: Takes a YouTube video URL or blog post URL and triggers n8n to repurpose it into: Twitter/X thread, LinkedIn post, email newsletter snippet, and short-form hook. Returns all versions in chat for your review before posting.

Trigger examples:

  • "Repurpose this video: https://youtube.com/watch?v=..."
  • "Turn my latest blog post into social content: [URL]"
  • "Create social posts from: [URL]"

Required fields:

  • url (YouTube or blog URL)
  • formats (thread, linkedin, email, hook — defaults to all)

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/content-repurpose

Payload sent:

{
  "url": "string",
  "formats": ["thread", "linkedin", "email", "hook"],
  "brand_voice": "punchy and direct",
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "complete", "content": { "thread": "...", "linkedin": "...", "email": "...", "hook": "..." } }

Display all content versions in chat for review.


Workflow 8 — Daily Briefing

What it does: Triggers n8n to pull together your full daily briefing: new leads from last 24 hours, open deals status, social media performance, emails that need replies, and your top 3 priorities for the day.

Trigger examples:

  • "Morning briefing"
  • "What happened overnight?"
  • "Daily digest"
  • "Give me my briefing"

Webhook endpoint: $N8N_WEBHOOK_BASE_URL/daily-briefing

Payload sent:

{
  "date": "ISO date",
  "sections": ["leads", "deals", "social", "email", "priorities"],
  "triggered_by": "openclaw"
}

Expected n8n response: { "status": "complete", "briefing": "markdown string" }

Display the briefing content formatted in chat.


Error Handling

If any webhook call fails, follow this sequence:

  1. Report the error clearly: "The [workflow name] webhook returned [error]. Here is what was sent: [payload summary]"
  2. Ask: "Should I retry, or would you like to check your n8n instance?"
  3. Do NOT silently fail or pretend the workflow ran
  4. Log the failed attempt in memory: "Failed workflow: [name] at [timestamp] — Error: [message]"

Rules (Always Follow These)

  • ALWAYS confirm what you are about to trigger before sending
  • NEVER expose API keys, webhook URLs, or credentials in chat
  • NEVER trigger a workflow without all required fields
  • If a required field is missing, ask for it before proceeding
  • NEVER send test data to production webhooks unless user confirms
  • Always report the n8n response status back to the user
  • If triggering email workflows, confirm the recipient email address out loud before sending
  • Log every successful trigger to daily memory: "[Workflow] triggered for [target] at [time]"

Status Check

At any time the user can type "n8n status" and you should:

  1. Run: python3 scripts/n8n_status.py
  2. Display the output exactly as returned
  3. If any workflows show as inactive, suggest running:

python3 scripts/n8n_validator.py

Scripts Reference

All scripts live in the scripts/ folder and use only environment variables — no secrets stored in files.

ScriptPurposeCommand
n8n_trigger.pyTrigger any workflowpython3 scripts/n8n_trigger.py <command>
n8n_validator.pyValidate all webhookspython3 scripts/n8n_validator.py
n8n_status.pyQuick status dashboardpython3 scripts/n8n_status.py

Quick test after setup:

python3 scripts/n8n_validator.py --env-only
python3 scripts/n8n_status.py
python3 scripts/n8n_trigger.py health --pretty

Slash Commands

  • /n8n-nurture — Quick trigger lead nurture
  • /n8n-post — Quick trigger social post
  • /n8n-followup — Quick trigger meeting follow-up
  • /n8n-crm — Quick trigger CRM update
  • /n8n-competitors — Quick trigger competitor report
  • /n8n-invoice — Quick trigger invoice reminder
  • /n8n-repurpose — Quick trigger content repurpose
  • /n8n-briefing — Quick trigger daily briefing
  • /n8n-status — Check instance health

平台分布

OpenClaw

74.95%
按下载量换算1,321

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills