N8n 1.0.2

ReviewAudited by ClawScan on May 10, 2026.

Overview

This n8n skill appears purpose-aligned, but it uses an n8n API key and can trigger or change workflows, so it should be used with care.

Install only if you intend to let the agent interact with your n8n instance. Use a limited-scope API key if available, keep the key secure, and manually review requests that activate, deactivate, or execute workflows.

Findings (3)

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.

Medium

#ASI02: Tool Misuse and Exploitation

What this means

Using this skill can start or change automations that may affect other services connected to n8n.

Why it was flagged

The skill can change workflow state and manually trigger workflows through the n8n API. This is aligned with its stated purpose, but these actions can affect connected automations.

Skill content

def activate_workflow(self, workflow_id: str) -> Dict: ... PATCH ... {'active': True}; ... def execute_workflow(self, workflow_id: str, data: Dict = None) -> Dict: ... POST ... f'workflows/{workflow_id}/execute'

Recommendation

Use a least-privilege n8n API key where possible and review workflow IDs and payloads before activating, deactivating, or executing workflows.

Medium

#ASI03: Identity and Privilege Abuse

What this means

Anyone or any agent process with access to this environment variable may be able to use the configured n8n API permissions.

Why it was flagged

The skill requires an n8n API key and base URL to access the user’s n8n instance. This is expected for the integration, though the registry metadata lists no required env vars or primary credential.

Skill content

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

Recommendation

Store the API key securely, avoid sharing shell environments unnecessarily, and prefer an API key with only the permissions needed for the intended tasks.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

A future dependency version could behave differently from the version the author tested.

Why it was flagged

The setup installs an unpinned Python dependency. The dependency is common and purpose-aligned, but the exact version is not locked.

Skill content

requests>=2.28.0

Recommendation

Install in the documented virtual environment and consider pinning or reviewing dependency versions in higher-security environments.