Agent skill

Openclaw N8n Orchestrator

by LeoYeAI in LeoYeAI/openclaw-master-skills

When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional…

MITAuto-check: notesProductivity & Automation

Install Openclaw N8n Orchestrator

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-n8n-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills openclaw-n8n-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openclaw-n8n-orchestrator .claude/skills/openclaw-n8n-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openclaw-n8n-orchestrator
GitHub stars
2.2k
Token cost
~4.1k tokens
SKILL.md length
1,100 words
Files
13 (incl. scripts, references)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional…

  • Works in 4 steps: set -euo pipefail (non-negotiable —… → Security Manifest Header → Input sanitization via urllib.parse.quote → …
  • Wants to connect an OpenClaw agent to n8n workflows
  • SKILL.md covers Why Route Through n8n, Mode Detection, Generating OpenClaw Skill… and Ingress: n8n → OpenClaw Gateway, plus 6 more sections
  • Runs Python, JavaScript and Shell scripts from its folder; calls python3, curl and openssl; reaches github.com; needs N8N_WEBHOOK_SECRET and OPENCLAW_GATEWAY_TOKEN

What it does

Openclaw N8n Orchestrator is an agent skill from LeoYeAI/openclaw-master-skills. When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional OpenClaw-to-n8n pipelines, design the proxy orchestration pattern, deploy co-located Docker stacks, implement the n8n-claw architecture, or publish OpenClaw n8n skills to ClawHub — activate this skill. Also trigger for "openclaw webhook," "agent workflow automation," "credential isolation," "gateway ingress," "n8n proxy pattern,"…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and reference files (for example `README.md`, `_meta.json` and `references/deployment.md`).

It sits in Productivity & Automation, covering Workflow automation, Cloud networking and Webhooks. It works with n8n and Docker. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Wants to connect an OpenClaw agent to n8n workflows
  • Create n8n webhook skills for OpenClaw
  • Route agent API calls through n8n for credential isolation
  • Build bidirectional OpenClaw-to-n8n pipelines

Example prompts

  • “openclaw webhook,”
  • “agent workflow automation,”
  • “credential isolation,”
  • “/openclaw-n8n-orchestrator”

Requirements

  • Python 3
  • Node.js
  • A Bash shell
  • Docker
  • A credential in N8N_WEBHOOK_SECRET

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. set -euo pipefail (non-negotiable — prevents silent failures)
  2. Security Manifest Header
  3. Input sanitization via urllib.parse.quote
  4. data-urlencode or pre-encoded payloads (never raw string interpolation)

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python, JavaScript and Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • python3
    • curl
    • openssl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • N8N_WEBHOOK_SECRET
    • OPENCLAW_GATEWAY_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openclaw N8n Orchestrator loads about 4.1k tokens when it runs, and up to ~18k if it reads all its reference files. Until then it costs about 157 tokens; SKILL.md has 1,100 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~18k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:14
    l-level access. Every API key stored in `.env` or skill files becomes an attack vector — leakable through hallucination,
  • NoteMentions a .env fileSKILL.md:408
    OK_URL` and `N8N_WEBHOOK_SECRET` set in `.env`

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,100 words, ~4,077 tokens.

Download SKILL.mdSave it as .claude/skills/openclaw-n8n-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
openclaw-n8n-orchestrator
description
When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional OpenClaw-to-n8n pipelines, design the proxy orchestration pattern, deploy co-located Docker stacks, implement the n8n-claw architecture, or publish OpenClaw n8n skills to ClawHub — activate this skill. Also trigger for "openclaw webhook," "agent workflow automation," "credential isolation," "gateway ingress," "n8n proxy pattern," or when securing autonomous agent API access through deterministic orchestration.

OpenClaw ↔ n8n Orchestrator

Build secure, auditable bridges between OpenClaw autonomous agents and n8n deterministic workflows. This skill generates production-ready OpenClaw skill directories (SKILL.md + scripts) that route all external API interactions through n8n's locked, credentialed pipelines.


Why Route Through n8n

OpenClaw's exec tool grants the LLM shell-level access. Every API key stored in .env or skill files becomes an attack vector — leakable through hallucination, prompt injection, or plaintext logging. The proxy orchestration pattern eliminates this:

  • The agent never touches external API credentials
  • All external calls route through n8n webhooks with locked, encrypted credentials
  • Every agent-triggered action appears as an inspectable node graph (black-box → glass-box)
  • Deterministic loops run at zero token cost in n8n

Mode Detection

Mode 1: Egress (OpenClaw → n8n)

User says: "trigger n8n workflow," "create webhook skill," "call n8n from openclaw" → Generate an OpenClaw skill directory that triggers n8n webhooks

Mode 2: Ingress (n8n → OpenClaw)

User says: "push data to openclaw," "n8n response to agent," "gateway API" → Configure n8n HTTP Request nodes to POST to the Gateway /v1/responses endpoint

Mode 3: Bidirectional (Proxy Pattern)

User says: "round trip," "full integration," "proxy pattern," "credential isolation" → Complete egress + ingress loop with air-gap credential provisioning

Mode 4: n8n-claw Architecture

User says: "rebuild agent in n8n," "n8n-claw," "supabase memory" → Read references/n8n-claw-architecture.md

Mode 5: Publish to ClawHub

User says: "publish skill," "clawhub," "package for registry" → Read references/publishing.md


Generating OpenClaw Skill Directories (Egress)

When building an OpenClaw skill that triggers n8n, generate a complete skill directory — not a loose file. OpenClaw skills are directories containing a SKILL.md with YAML frontmatter.

Required Directory Structure
openclaw-{service}-{action}/
├── SKILL.md              ← YAML frontmatter + instructions (REQUIRED)
├── README.md             ← Human documentation
└── scripts/
    └── trigger.sh        ← Webhook trigger with input sanitization
SKILL.md Template

Every generated SKILL.md must follow this exact structure:

yaml
---
name: openclaw-{service}-{action}
description: "When the user requests {specific trigger condition}, POST a structured JSON payload to the n8n webhook at {path} to execute {what it does}. Use this skill for {explicit use cases}."
homepage: "https://github.com/{user}/{repo}"
metadata:
  clawdbot:
    emoji: "{relevant_emoji}"
requires:
  env:
    - N8N_WEBHOOK_URL
    - N8N_WEBHOOK_SECRET
  bins:
    - "curl"
files:
  - "scripts/*"
user-invocable: true
---

Critical YAML rules:

  • description is the only trigger mechanism. The LLM cannot see the Markdown body until after it selects the skill. Pack ALL trigger heuristics into this single string.
  • Use metadata.clawdbot namespace — NOT metadata.openclaw (the registry ignores the legacy namespace).
  • Use requires.env (singular) — NOT requires.envs (causes parse validation errors).
  • No multi-line strings or YAML block scalars. The parser expects single-line values or valid arrays only.
  • Declare files: ["scripts/*"] — omitting this causes ClawHub security scanners to flag the skill as suspicious.
Markdown Body Structure

Below the frontmatter, write instructions the LLM will follow. Include these mandatory transparency sections for ClawHub compliance:

markdown
# {Skill Name}

## Execution

When triggered, run the webhook script:

\`\`\`bash
exec scripts/trigger.sh "{action}" "{payload_json}"
\`\`\`

The script sanitizes all input, constructs the authenticated webhook request,
and returns the n8n response for the agent to summarize.

## Failure Handling

- If curl returns non-zero exit code, read stderr and report the specific error
- If HTTP 401: webhook secret mismatch — instruct user to verify N8N_WEBHOOK_SECRET
- If HTTP 404: workflow inactive or path wrong — instruct user to check n8n
- If HTTP 5xx: n8n execution failure — report and suggest checking n8n execution logs
- Do NOT hallucinate success if the response is empty or unexpected

## External Endpoints

| URL | Method | Payload |
|-----|--------|---------|
| `${N8N_WEBHOOK_URL}/webhook/openclaw-{service}-{action}` | POST | JSON action + payload object |

## Security & Privacy

- Webhook secret loaded from environment variable, never hardcoded
- All user input sanitized via URL encoding before shell execution
- No data stored locally; payload transmitted to n8n instance only
- Agent has NO access to downstream API credentials (Slack, GitHub, etc.)

## Model Invocation Note

The OpenClaw agent may invoke this skill autonomously without direct human
prompting. To disable autonomous triggering, remove this skill directory
from the active skills path.

## Trust Statement

By using this skill, data is sent to your configured n8n instance.
Only install if you trust your n8n deployment and its configured integrations.
Trigger Script Template

Every webhook trigger script MUST include:

  1. set -euo pipefail (non-negotiable — prevents silent failures)
  2. Security Manifest Header
  3. Input sanitization via urllib.parse.quote
  4. --data-urlencode or pre-encoded payloads (never raw string interpolation)
bash
#!/usr/bin/env bash
set -euo pipefail

# SECURITY MANIFEST:
# Environment variables accessed: N8N_WEBHOOK_URL, N8N_WEBHOOK_SECRET (only)
# External endpoints called: ${N8N_WEBHOOK_URL}/webhook/openclaw-{service}-{action} (only)
# Local files read: none
# Local files written: none

ACTION="${1:?Usage: trigger.sh <action> <payload_json>}"
PAYLOAD="${2:?Usage: trigger.sh <action> <payload_json>}"

# Sanitize inputs — prevents shell injection via command substitution
SAFE_ACTION=$(printf '%s' "$ACTION" | python3 -c \
  'import sys, urllib.parse; print(urllib.parse.quote(sys.stdin.read().strip(), safe=""))')

# Construct and send webhook request
RESPONSE=$(curl -s -w "\n%{http_code}" -X POST \
  "${N8N_WEBHOOK_URL}/webhook/openclaw-${SAFE_ACTION}" \
  -H "Content-Type: application/json" \
  -H "x-webhook-secret: ${N8N_WEBHOOK_SECRET}" \
  --data-urlencode "payload=${PAYLOAD}" \
  --max-time 30)

# Parse response
HTTP_CODE=$(echo "$RESPONSE" | tail -1)
BODY=$(echo "$RESPONSE" | sed '$d')

if [[ "$HTTP_CODE" -ge 200 && "$HTTP_CODE" -lt 300 ]]; then
  echo "SUCCESS (HTTP ${HTTP_CODE}): ${BODY}"
  exit 0
else
  echo "ERROR (HTTP ${HTTP_CODE}): ${BODY}" >&2
  exit 1
fi
Native MCP Tool Alternative

For simple webhook calls, prefer OpenClaw's built-in exec tool with a Node.js one-liner over shell scripts. Node.js avoids shell expansion vulnerabilities entirely:

javascript
// Inline via exec tool — no external dependencies
const https = require('https');
const data = JSON.stringify({action: ACTION, payload: PAYLOAD});
const options = {
  hostname: N8N_HOST, port: 5678, path: '/webhook/openclaw-{service}-{action}',
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-webhook-secret': process.env.N8N_WEBHOOK_SECRET,
    'Content-Length': data.length
  }
};
const req = https.request(options, res => {
  let body = '';
  res.on('data', chunk => body += chunk);
  res.on('end', () => {
    process.stdout.write(body);
    process.exit(res.statusCode >= 200 && res.statusCode < 300 ? 0 : 1);
  });
});
req.on('error', e => { process.stderr.write(e.message); process.exit(1); });
req.write(data);
req.end();

Node.js is preferred because OpenClaw requires Node.js 22+ — it's always available. No dependencies, no shell injection surface.


Ingress: n8n → OpenClaw Gateway

The Gateway /v1/responses endpoint is disabled by default.

Enable the Endpoint

Edit openclaw.json:

json
{
  "gateway": {
    "http": {
      "endpoints": {
        "responses": { "enabled": true }
      }
    },
    "auth": {
      "mode": "token",
      "token": "${OPENCLAW_GATEWAY_TOKEN}"
    }
  }
}
n8n HTTP Request Node Configuration
ParameterValueWhy
MethodPOSTStandard transmission
URLhttp://{gateway-host}:18789/v1/responsesOpenResponses ingress
AuthorizationBearer {token}Gateway auth
Content-Typeapplication/jsonJSON parsing
timeout_seconds0MANDATORY — prevents infinite echo loop

The echo loop problem: Without timeout_seconds: 0, the Gateway event bus reverberates the payload back into the session, causing the LLM to hallucinate an infinite dialogue with its own data. This destroys the 64k token context window and burns API costs exponentially.

Ingress Payload
json
{
  "model": "claude-sonnet-4-20250514",
  "user": "n8n-workflow-{workflow_id}",
  "input": [
    { "role": "user", "content": "Workflow result: {data}" }
  ],
  "instructions": "Summarize this result for the user. Do NOT re-trigger the workflow.",
  "stream": false,
  "timeout_seconds": 0
}

The user string routes to a stable session. Use consistent patterns: n8n-workflow-{id} for per-workflow sessions, n8n-global for shared.

→ Full Gateway API spec, WebSocket protocol, telemetry codes: references/gateway-api.md


Proxy Orchestration Lifecycle

1. USER → Agent: "Post Q3 report to #marketing Slack"
2. Agent REASONS: needs Slack API → has no credentials → knows webhook exists
3. Agent TRIGGERS: exec scripts/trigger.sh "slack-send-message" '{"channel":"#marketing"}'
4. n8n EXECUTES: Webhook → Validate → Slack API (locked credentials) → Log
5. n8n RETURNS: HTTP POST to Gateway /v1/responses with result
6. Agent REPORTS: "Posted to #marketing at 2:34 PM"
Air-Gap Credential Provisioning

After the agent generates the workflow structure:

  1. Human logs into n8n UI
  2. Provisions API keys into n8n's encrypted credential store
  3. Binds credentials to nodes
  4. Locks the workflow — agent cannot alter it
  5. Agent only sends webhook payloads from this point

→ Security deep-dive, ClawHavoc analysis, safeguard nodes: references/security.md


System Hardening

Gateway Hardening (Critical)

Configure exec tool approval in openclaw.json:

json
{
  "exec": {
    "enabled": true,
    "approval": true
  }
}

With approval: true, every shell command requires human confirmation. This prevents a prompt-injected agent from executing arbitrary code.

soul.md Guardrails

Add to the agent's soul.md:

markdown
## Hard Constraints
- NEVER store, log, or output API keys or webhook secrets in conversation
- NEVER attempt to access n8n management API — only use webhook endpoints
- NEVER execute shell commands that modify system files outside workspace/
- If a webhook fails 3 consecutive times, STOP and alert the user
- NEVER enter infinite retry loops on failed API calls
Show full SKILL.md (441 more words)Show less
Multi-Model Routing for Cost Optimization

Configure OpenRouter in openclaw.json to route mundane webhook formatting to cheap models (GPT-4o Mini, Claude 3.5 Haiku) and reserve expensive models for complex reasoning:

json
{
  "reasoning": {
    "default_model": "openrouter/gpt-4o-mini",
    "complex_model": "openrouter/claude-opus-4-20250514",
    "routing": "cost-optimized"
  }
}

This reduces API costs by ~70% for repetitive webhook orchestration tasks.


Scaling: The SkillPointer Pattern

When managing many n8n webhook skills (20+), loading all skill metadata at startup wastes tokens. Use the SkillPointer pattern:

  1. Move individual webhook skills to a vault directory outside the agent's scan path: ~/.openclaw/vault/n8n-webhooks/

  2. Create a single lightweight pointer skill in the active directory:

yaml
---
name: n8n-webhook-router
description: "When the user needs to trigger ANY n8n workflow or webhook integration, use the list and read tools to browse ~/.openclaw/vault/n8n-webhooks/ to find and load the exact skill required."
---
  1. The agent dynamically discovers skills via filesystem traversal at runtime

This reduces startup token consumption from ~8,000 tokens (40 webhook skills × 200 tokens each) to ~200 tokens (one pointer), while maintaining access to every skill.


Deployment

→ Docker Compose templates, network topologies, environment variables: references/deployment.md

Quick reference: OpenClaw Gateway defaults to port 18789, n8n to 5678. Never bind the Gateway to public interfaces. Use SSH tunnels or Tailscale for cross-network ingress.


Failure Mode Reference

Egress
SymptomCauseFix
401 from webhookSecret mismatchVerify N8N_WEBHOOK_SECRET matches n8n Header Auth credential
404 from webhookInactive workflow or wrong pathActivate workflow; verify naming convention
Connection refusedNetwork unreachableCheck topology, ports, firewall
Trigger script hangsMissing set -euo pipefailAdd strict error handling; ensure no interactive prompts
Shell injectionRaw input interpolationUse urllib.parse.quote or Node.js (no shell expansion)
Ingress
SymptomCauseFix
403 from GatewayToken mismatchVerify OPENCLAW_GATEWAY_TOKEN
Infinite echo loopMissing timeout_seconds: 0Add immediately
Session not foundInconsistent user stringUse stable pattern: n8n-workflow-{id}
DEVICE_AUTH_SIGNATURE_EXPIREDClock skewSync NTP across hosts
Skill not loadingInvalid YAML frontmatterCheck for multi-line strings; validate with openclaw skills status

Quick Start Checklist

Egress only:

  • OpenClaw running (Node.js 22+) with workspace/skill/ directory
  • n8n running with webhook endpoint reachable
  • Webhook secret generated: openssl rand -hex 32
  • Skill directory created with SKILL.md (YAML frontmatter) + scripts/trigger.sh
  • N8N_WEBHOOK_URL and N8N_WEBHOOK_SECRET set in .env
  • requires.env and requires.bins declared in YAML frontmatter
  • files: ["scripts/*"] declared in frontmatter
  • Security Manifest Header in trigger.sh
  • set -euo pipefail in trigger.sh
  • Input sanitization via urllib.parse.quote or Node.js
  • n8n workflow created, validated, activated with Header Auth credential
  • Test with manual curl before agent triggers

Add bidirectional:

  • Gateway /v1/responses enabled in openclaw.json
  • exec.approval: true configured in gateway
  • soul.md guardrails written
  • timeout_seconds: 0 in all ingress payloads
  • SSH tunnel or Tailscale for cross-network Gateway access

Reference Files

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (scripts, references) in skills/openclaw-n8n-orchestrator of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • references/deployment.md
  • references/gateway-api.md
  • references/n8n-claw-architecture.md
  • references/publishing.md
  • references/security.md
  • scripts/validate_integration.py
  • templates/docker-compose.yml
  • templates/skill-template-SKILL.md
  • templates/trigger-template.js
  • templates/trigger-template.sh

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Openclaw N8n Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openclaw N8n Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openclaw N8n Orchestrator this skillLeoYeAI/openclaw-master-skills2.2k—~4.1kAutomated safety check: NotesMIT
N8n Workflowsvibeeval/vibecosystem532—~3.3kAutomated safety check: PassMIT
Open Flowoomol-lab/open-flow237—~411Automated safety check: NotesApache-2.0
n8n Expression Syntaxczlonkowski/n8n-skills6.4k—~5.2kAutomated safety check: PassMIT
N8n Expression Syntaxdavila7/claude-code-templates33k4 repos~2.4kAutomated safety check: PassMIT
N8n Workflow Patternsdavila7/claude-code-templates33k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • N8n Workflows

    vibeeval/vibecosystem

    n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

    532 GitHub stars~3.3k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Open Flow

    oomol-lab/open-flow

    Create, inspect, edit, check, run, and publish persistent Open Flow workflows through an existing Server, or assess and convert n8n workflows to Open Flow.

    237 GitHub stars~411 tokensUpdated today
    Productivity & AutomationAuto-check: notes
  • n8n Expression Syntax

    czlonkowski/n8n-skills

    Validates and fixes n8n's double-curly-brace expressions, covering $json, $node, and the webhook body-wrapping mistake.

    6.4k GitHub stars~5.2k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • N8n Expression Syntax

    davila7/claude-code-templates

    Validate n8n expression syntax and fix common errors. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 4 repos~2.4k tokens
    Productivity & AutomationAuto-check passed
  • N8n Workflow Patterns

    davila7/claude-code-templates

    Proven workflow architectural patterns from real n8n workflows.

    33k GitHub starsUsed in 1 repo~2.8k tokens
    Productivity & AutomationAuto-check passed
  • N8n

    aiskillstore/marketplace

    n8n workflow automation patterns and API integration. An agent skill from aiskillstore/marketplace.

    433 GitHub starsUsed in 1 repo~1.6k tokens
    Productivity & AutomationAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,200 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Openclaw N8n Orchestrator

What does Openclaw N8n Orchestrator do?

When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional…. Openclaw N8n Orchestrator is an agent skill from LeoYeAI/openclaw-master-skills. When the user wants to connect an OpenClaw agent to n8n workflows, create n8n webhook skills for OpenClaw, route agent API calls through n8n for credential isolation, build bidirectional OpenClaw-to-n8n pipelines, design the proxy orchestration pattern, deploy co-located Docker stacks, implement the n8n-claw architecture, or publish OpenClaw n8n skills to ClawHub — activate this skill.

When should I use Openclaw N8n Orchestrator?

Openclaw N8n Orchestrator fits situations like: wants to connect an OpenClaw agent to n8n workflows; create n8n webhook skills for OpenClaw; route agent API calls through n8n for credential isolation; build bidirectional OpenClaw-to-n8n pipelines.

How do I install Openclaw N8n Orchestrator in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-n8n-orchestrator -a claude-code`. Or copy the skill folder (skills/openclaw-n8n-orchestrator in LeoYeAI/openclaw-master-skills) into .claude/skills/openclaw-n8n-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Openclaw N8n Orchestrator in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-n8n-orchestrator -a codex`. Or copy the skill folder (skills/openclaw-n8n-orchestrator in LeoYeAI/openclaw-master-skills) into .agents/skills/openclaw-n8n-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Openclaw N8n Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill openclaw-n8n-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-n8n-orchestrator, .gemini/skills/openclaw-n8n-orchestrator, .github/skills/openclaw-n8n-orchestrator and .opencode/skills/openclaw-n8n-orchestrator in your project.

What does Openclaw N8n Orchestrator need to run?

Going by SKILL.md and its folder, Openclaw N8n Orchestrator needs Python, JavaScript and a shell for the scripts in its folder, the command-line tools its instructions call (python3, curl and openssl) and credentials named N8N_WEBHOOK_SECRET and OPENCLAW_GATEWAY_TOKEN. Our summary lists: Python 3; Node.js; A Bash shell; Docker; A credential in N8N_WEBHOOK_SECRET.

Does Openclaw N8n Orchestrator access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Openclaw N8n Orchestrator safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Openclaw N8n Orchestrator use?

Openclaw N8n Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openclaw N8n Orchestrator use?

About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Openclaw N8n Orchestrator?

Skills that share tags, products or a category with Openclaw N8n Orchestrator: N8n Workflows (vibeeval/vibecosystem, 532 stars), Open Flow (oomol-lab/open-flow, 237 stars), n8n Expression Syntax (czlonkowski/n8n-skills, 6.4k stars) and N8n Expression Syntax (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openclaw N8n Orchestrator?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.