ClawTrust
4k Downloads
Overview
Control and inspect an n8n automation instance from OpenClaw via the n8n REST API, including managing workflows and reviewing executions for both n8n Cloud and self-hosted setups.
Key Advantages
1.Centralizes operational control of n8n (list, inspect, create, activate/deactivate, delete workflows) directly from OpenClaw.
2.Supports both n8n Cloud and self-hosted instances via simple environment configuration (N8N_API_URL, N8N_API_KEY).
3.Covers key operational workflows: listing executions, filtering by status/workflow, inspecting execution details, and basic health checks.
4.Enables triggering workflows via webhooks, including production and test endpoints, making it suitable for on-demand automation runs.
5.Leverages standard REST/HTTP patterns with API-key auth, so behavior is predictable and compatible with typical DevOps practices.
Use Cases
- List all workflows, see which are active, and quickly toggle activation status during incident response or maintenance windows.
- Inspect recent executions, filter for failures, and fetch execution details to debug problematic workflows and nodes.
- Trigger specific webhook-based workflows from OpenClaw as part of guided runbooks or operator-driven automation.
- Create new workflows from JSON definitions stored or generated elsewhere, enabling infrastructure-as-code–style workflow management.
- Perform periodic health checks that count active workflows and failed executions over a time window, then summarize status for operators or alerts.
Evaluation Scores
7.5
/ 10
Reliability
7.0
Functionality
8.0
Usability
7.5
Safety
6.5
Performance
8.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.5/103/19/2026▼
OS: darwin-x64LLM: minimax/minimax-m2.5
**Judgment:** This skill is a solid, production-capable bridge between OpenClaw and n8n’s REST API, well-suited for teams that already rely on n8n for workflows and need operational control from a conversational interface.
**What it does well**
- Exposes the core n8n management surface: list/get/create/delete workflows, activate/deactivate, trigger via webhook, and inspect executions.
- Works with both n8n Cloud and self-hosted instances using simple environment variables (N8N_API_URL, N8N_API_KEY).
- Provides patterns for real operational tasks: filtering executions by status or workflow, health checks, and debugging failed runs.
**Key risks / cautions**
- **High-privilege API key:** Typical n8n API keys have full access on non-enterprise plans; misconfiguration or over-broad use could lead to unintended changes (e.g., deleting or overwriting workflows, mass-triggering webhooks).
- **Production impact:** Activating/deactivating workflows or triggering webhooks from a chat interface can directly affect live automations; access should be restricted and audited.
- **Data exposure:** Execution details can contain sensitive payloads; consider who is allowed to query or view execution logs via this skill.
- **Error handling assumptions:** The documentation shows raw API usage but does not demonstrate robust handling of network errors, timeouts, or API changes; expect behavior to mirror n8n’s API reliability and your network conditions.
**Recommended scenarios**
- Operations, SRE, or platform teams that already operate n8n and want a conversational assistant to inspect, toggle, and lightly manage workflows.
- Support/engineering teams debugging automation incidents by quickly listing failed executions and drilling into execution details from chat.
- Internal tools or copilots where controlled operators can trigger specific n8n workflows on demand as part of a guided runbook.
- Environments where both self-hosted and cloud n8n instances exist, and a uniform control surface via OpenClaw is desirable.
Use in tightly controlled contexts (limited users, clear guardrails, possibly separate API keys per environment) to mitigate the elevated risk that comes with full API control over your n8n instance.
Comments (0)
No comments yet. Be the first!