n8n
ReviewAudited by ClawScan on May 18, 2026.
Overview
This appears to be a coherent n8n management skill, but it gives the agent broad control over your n8n workflows through your API key.
Install this only if you want your agent to manage your n8n instance. Use a trusted N8N_BASE_URL, protect or revoke the API key as needed, and require explicit review before activating, executing, deleting, or deploying workflows that touch external services.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone using the skill is granting it the ability to act through their n8n API access.
The client authenticates API calls using the user's n8n API key and configured n8n URL. This is expected for the stated purpose, but it grants account-level authority to the skill.
self.base_url = base_url or os.getenv('N8N_BASE_URL') ... self.api_key = api_key or os.getenv('N8N_API_KEY') ... 'X-N8N-API-KEY': self.api_keyUse a revokable, least-privileged n8n API key where possible, point N8N_BASE_URL only to your trusted n8n instance, and revoke the key if you stop using the skill.
A mistaken command or misunderstood workflow ID could change, run, or delete automations in your n8n instance.
The helper exposes mutating n8n operations, including workflow creation, deletion, activation, deactivation, and manual execution. These are central to the skill's purpose, but they can have real downstream effects.
def create_workflow ... POST 'workflows' ... def delete_workflow ... DELETE ... def activate_workflow ... {'active': True} ... def execute_workflow ... POST ... '/execute'Review workflow IDs and payloads before running mutating commands, validate or dry-run workflows first, and back up important workflows before deletion or major updates.
A faulty workflow could post publicly, modify business data, or call external services repeatedly if activated without review.
The documented workflow templates and use cases can connect n8n automations to external services, public posting, payments data, scraping, or databases. That is normal for n8n, but activation or execution can propagate mistakes across systems.
social-media-crosspost | Multi-platform posting ... revenue-dashboard | Stripe integration ... lead-scraping | Web scraping, data enrichment, DB storage
Start new workflows inactive, test with sample data, limit connected-service credentials, and monitor initial executions closely.
Users have less provenance information for the included helper scripts and may need to ensure local Python dependencies are available.
The skill includes runnable Python scripts, but the provided metadata has limited provenance and no install specification. This is not evidence of malicious behavior, but it reduces setup and source-verification clarity.
Source: unknown; Homepage: none ... No install spec — this is an instruction-only skill ... Code file presence: 3 code file(s)
Inspect the scripts before use if provenance matters, install dependencies from trusted sources, and prefer skills with clear source/homepage metadata when available.