How do I install the N8n skill?

Run npx skillmds add majiayu000/n8n-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with N8n?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

N8n by majiayu000 — Agent Skill

Name: N8n
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

n8n Workflow Management

Manage your n8n automation platform: list workflows, trigger executions, check status, and activate/deactivate workflows.

Setup

Set these environment variables:

N8N_API_URL="https://your-n8n-instance.com"   # Base URL (no trailing slash)
N8N_API_KEY="your-api-key-here"                # Settings → API → Create API Key

List all workflows

curl -s "$N8N_API_URL/api/v1/workflows" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, name, active}'

Get workflow details

curl -s "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" | jq .

Execute a workflow

curl -s -X POST "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}/execute" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}' | jq .

With input data:

curl -s -X POST "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}/execute" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": {"key": "value"}}' | jq .

Activate a workflow

curl -s -X PATCH "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"active": true}' | jq .

Deactivate a workflow

curl -s -X PATCH "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"active": false}' | jq .

List executions

curl -s "$N8N_API_URL/api/v1/executions" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, workflowId, status, startedAt, stoppedAt}'

Filter by workflow:

curl -s "$N8N_API_URL/api/v1/executions?workflowId={WORKFLOW_ID}" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, status, startedAt}'

Get execution details

curl -s "$N8N_API_URL/api/v1/executions/{EXECUTION_ID}" \
  -H "X-N8N-API-KEY: $N8N_API_KEY" | jq .

Trigger via webhook

If a workflow has a Webhook trigger node, call its URL directly:

curl -s -X POST "https://your-n8n-instance.com/webhook/{WEBHOOK_PATH}" \
  -H "Content-Type: application/json" \
  -d '{"event": "deploy", "status": "success"}'

Notes

Replace {WORKFLOW_ID}, {EXECUTION_ID}, and {WEBHOOK_PATH} with actual values.
Always list workflows first to find the correct ID before executing.
Webhook URLs are separate from the API — they use the path configured in the Webhook node.
n8n API uses pagination. Add ?limit=100&cursor=... for large result sets.
Be cautious activating workflows that have external triggers — they start listening immediately.

---name: n8n-3description: Manage n8n workflows — list, execute, activate/deactivate, and monitor executions via the n8n REST API.--- # n8n Workflow Management Manage your n8n automation platform: list workflows, trigger executions, check status, and activate/deactivate workflows. ## Setup Set these environment variables: ```bash N8N_API_URL="https://your-n8n-instance.com" # Base URL (no trailing slash) N8N_API_KEY="your-api-key-here" # Settings → API → Create API Key ``` ## List all workflows ```bash curl -s "$N8N_API_URL/api/v1/workflows" \ -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, name, active}' ``` ## Get workflow details ```bash curl -s "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \ -H "X-N8N-API-KEY: $N8N_API_KEY" | jq . ``` ## Execute a workflow ```bash curl -s -X POST "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}/execute" \ -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{}' | jq . ``` With input data: ```bash curl -s -X POST "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}/execute" \ -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{"data": {"key": "value"}}' | jq . ``` ## Activate a workflow ```bash curl -s -X PATCH "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \ -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{"active": true}' | jq . ``` ## Deactivate a workflow ```bash curl -s -X PATCH "$N8N_API_URL/api/v1/workflows/{WORKFLOW_ID}" \ -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{"active": false}' | jq . ``` ## List executions ```bash curl -s "$N8N_API_URL/api/v1/executions" \ -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, workflowId, status, startedAt, stoppedAt}' ``` Filter by workflow: ```bash curl -s "$N8N_API_URL/api/v1/executions?workflowId={WORKFLOW_ID}" \ -H "X-N8N-API-KEY: $N8N_API_KEY" | jq '.data[] | {id, status, startedAt}' ``` ## Get execution details ```bash curl -s "$N8N_API_URL/api/v1/executions/{EXECUTION_ID}" \ -H "X-N8N-API-KEY: $N8N_API_KEY" | jq . ``` ## Trigger via webhook If a workflow has a Webhook trigger node, call its URL directly: ```bash curl -s -X POST "https://your-n8n-instance.com/webhook/{WEBHOOK_PATH}" \ -H "Content-Type: application/json" \ -d '{"event": "deploy", "status": "success"}' ``` ## Notes - Replace `{WORKFLOW_ID}`, `{EXECUTION_ID}`, and `{WEBHOOK_PATH}` with actual values. - Always list workflows first to find the correct ID before executing. - Webhook URLs are separate from the API — they use the path configured in the Webhook node. - n8n API uses pagination. Add `?limit=100&cursor=...` for large result sets. - Be cautious activating workflows that have external triggers — they start listening immediately.

Frequently asked questions