N8n 1.0.2

Manage n8n workflows and automations via API. Use when working with n8n workflows, executions, or automation tasks - listing workflows, activating/deactivating, checking execution status, manually triggering workflows, or debugging automation issues.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 1.6k · 2 current installs · 2 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The name, description, and code align with an n8n API client (listing, activating, executing workflows). However the registry metadata claims no required env vars or primary credential while the SKILL.md and n8n_api.py clearly require N8N_API_KEY (and N8N_BASE_URL). The missing declared primaryEnv and absent homepage/source are additional red flags about provenance.
Instruction Scope
SKILL.md instructions are scoped to calling the n8n REST API and match the provided scripts. They do instruct the user to place the API key in shell rc files (~/.zshrc or ~/.bashrc), which persists a secret in plain text environment configuration — a security/privacy consideration but functionally consistent with the skill's purpose.
Install Mechanism
This is an instruction-only skill with no install spec. It includes a requirements.txt (requests) and instructs creating a virtualenv and pip installing dependencies — a low-risk, conventional installation path.
!
Credentials
The skill legitimately needs N8N_API_KEY and N8N_BASE_URL, but the registry metadata does not list any required env vars or primary credential. That mismatch makes it unclear how secrets will be provided to the agent. Storing an API key in shell rc as recommended persists the secret in plaintext environment and may be inappropriate for some users.
Persistence & Privilege
The skill does not request always:true, does not modify system-wide settings, and is user-invocable only. It does not attempt to change other skills' configs or gain permanent elevated presence.
What to consider before installing
This skill's code matches an n8n API client, but the package metadata did not declare that it needs an API key or base URL. Before installing: (1) confirm the skill's source/maintainer (no homepage was provided); (2) supply N8N_API_KEY and N8N_BASE_URL only for a trusted n8n instance and prefer a short-lived or scoped key; (3) avoid adding secrets to shell rc files if you can — use a secure secret manager or the agent's secret storage; (4) inspect the included scripts (n8n_api.py) yourself — they only call the provided base URL with your API key, but the provenance mismatch is the main concern; (5) if you proceed, rotate the API key after use and limit its permissions where possible.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
latestvk97avq1br089wckbb7zm359v3x7zwz16

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

n8n Workflow Management

Interact with n8n automation platform via REST API.

Setup

First-time setup:

  1. Install dependencies (virtual environment):
cd skills/n8n-1.0.2
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
  1. Configure environment variables in ~/.zshrc (or ~/.bashrc):
export N8N_API_KEY="your-api-key-here"
export N8N_BASE_URL="https://your-n8n-instance.com"
  1. Reload shell and verify connection:
source ~/.zshrc
./skills/n8n-1.0.2/scripts/n8n.sh list-workflows --pretty

Tip: Get your API key from n8n UI: Settings → API

Quick Reference

List Workflows

./scripts/n8n.sh list-workflows --pretty
./scripts/n8n.sh list-workflows --active true --pretty

Get Workflow Details

./scripts/n8n.sh get-workflow --id <workflow-id> --pretty

Activate/Deactivate

./scripts/n8n.sh activate --id <workflow-id>
./scripts/n8n.sh deactivate --id <workflow-id>

Executions

# List recent executions
./scripts/n8n.sh list-executions --limit 10 --pretty

# Get execution details
./scripts/n8n.sh get-execution --id <execution-id> --pretty

# Filter by workflow
./scripts/n8n.sh list-executions --id <workflow-id> --limit 20 --pretty

Manual Execution

# Trigger workflow
./scripts/n8n.sh execute --id <workflow-id>

# With data
./scripts/n8n.sh execute --id <workflow-id> --data '{"key": "value"}'

Python API

For programmatic access:

from scripts.n8n_api import N8nClient

client = N8nClient()

# List workflows
workflows = client.list_workflows(active=True)

# Get workflow
workflow = client.get_workflow('workflow-id')

# Activate/deactivate
client.activate_workflow('workflow-id')
client.deactivate_workflow('workflow-id')

# Executions
executions = client.list_executions(workflow_id='workflow-id', limit=10)
execution = client.get_execution('execution-id')

# Execute workflow
result = client.execute_workflow('workflow-id', data={'key': 'value'})

Common Tasks

Debug Failed Workflows

  1. List recent executions with failures
  2. Get execution details to see error
  3. Check workflow configuration
  4. Deactivate if needed

Monitor Workflow Health

  1. List active workflows
  2. Check recent execution status
  3. Review error patterns

Workflow Management

  1. List all workflows
  2. Review active/inactive status
  3. Activate/deactivate as needed
  4. Delete old workflows

API Reference

For detailed API documentation, see references/api.md.

Troubleshooting

Authentication error:

  • Verify N8N_API_KEY is set: echo $N8N_API_KEY
  • Check API key is valid in n8n UI

Connection error:

  • Check N8N_BASE_URL if using custom URL

Command errors:

  • Use --pretty flag for readable output
  • Check --id is provided when required
  • Validate JSON format for --data parameter

Files

5 total
Select a file
Select a file to preview.

Comments

Loading comments…