Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Operate n8n via its public REST API from OpenClaw. Use for workflow management, executions, and automation tasks such as listing, creating, publishing, triggering, or troubleshooting. Works with both self-hosted n8n and n8n Cloud.
Operate n8n via its public REST API from OpenClaw. Use for workflow management, executions, and automation tasks such as listing, creating, publishing, triggering, or troubleshooting. Works with both self-hosted n8n and n8n Cloud.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill when you need to drive n8n programmatically. It covers the same core actions you use in the UI: workflows, executions, tags, credentials, projects, and more.
The public API is unavailable during the free trial. Upgrade your plan to enable API access.
Recommended environment variables (or store in .n8n-api-config): export N8N_API_BASE_URL="https://your-instance.app.n8n.cloud/api/v1" # or http://localhost:5678/api/v1 export N8N_API_KEY="your-api-key-here" Create the API key in: n8n Settings โ n8n API โ Create an API key.
All requests require this header: X-N8N-API-KEY: $N8N_API_KEY
The API playground is only available on self-hosted n8n and operates on real data. For safe experiments, use a test workflow or a separate test instance.
curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" "$N8N_API_BASE_URL/workflows" \ | jq '.data[] | {id, name, active}'
curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" "$N8N_API_BASE_URL/workflows/{id}"
# Activate (publish) curl -s -X POST -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{"versionId":"","name":"","description":""}' \ "$N8N_API_BASE_URL/workflows/{id}/activate" # Deactivate curl -s -X POST -H "X-N8N-API-KEY: $N8N_API_KEY" \ "$N8N_API_BASE_URL/workflows/{id}/deactivate"
# Production webhook curl -s -X POST "$N8N_API_BASE_URL/../webhook/{webhook-path}" \ -H "Content-Type: application/json" \ -d '{"key":"value"}' # Test webhook curl -s -X POST "$N8N_API_BASE_URL/../webhook-test/{webhook-path}" \ -H "Content-Type: application/json" \ -d '{"key":"value"}'
# Recent executions curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" \ "$N8N_API_BASE_URL/executions?limit=10" \ | jq '.data[] | {id, workflowId, status, startedAt}' # Failed only curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" \ "$N8N_API_BASE_URL/executions?status=error&limit=5"
curl -s -X POST -H "X-N8N-API-KEY: $N8N_API_KEY" \ -H "Content-Type: application/json" \ -d '{"loadWorkflow":true}' \ "$N8N_API_BASE_URL/executions/{id}/retry"
Count active workflows and recent failures: ACTIVE=$(curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" \ "$N8N_API_BASE_URL/workflows?active=true" | jq '.data | length') FAILED=$(curl -s -H "X-N8N-API-KEY: $N8N_API_KEY" \ "$N8N_API_BASE_URL/executions?status=error&limit=100" \ | jq '[.data[] | select(.startedAt > (now - 86400 | todate))] | length') echo "Active workflows: $ACTIVE | Failed (24h): $FAILED"
List failed executions to get the execution ID. Fetch execution details and identify the failing node. Review node parameters and input data. Suggest a fix based on the error message.
See assets/n8n-api.endpoints.md for the full list of endpoints.
If you want a refresher, these are commonly recommended: KnowledgeOwl: working with APIs (intro) IBM Cloud Learn Hub: what is an API / REST API MDN: overview of HTTP
The n8n API node can call the public API from inside workflows. Webhook URLs are not the same as API URLs and do not use the API key header. Execution records may be pruned based on instance retention settings.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.