
N8n
- 45 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
n8n is a Claude Code skill that provides n8n workflow-automation patterns and REST API integration for building webhook-driven workflows.
About
n8n is a Claude Code skill for building and managing n8n automation workflows. It documents the workflow and node JSON structure, common patterns (webhook triggers, HTTP requests, IF branching, batch loops), the n8n REST API for CRUD and activation, and expression syntax. A developer uses it when authoring n8n workflows or driving n8n programmatically via its API.
- Documents n8n workflow, node, and connection JSON structure
- Reusable node patterns: webhook trigger, HTTP request, IF branch, SplitInBatches loop
- Full n8n REST API reference (list/get/create/update/activate/executions) plus expression syntax
N8n by the numbers
- 45 all-time installs (skills.sh)
- Ranked #1,117 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
n8n capabilities & compatibility
Free skill; requires a running n8n instance and an N8N_API_KEY.
- Capabilities
- workflow automation · webhook setup · api integration
- Works with
- n8n
- Use cases
- orchestration · api development
- Pricing
- Bring your own API key
What n8n says it does
This skill enables creating and managing n8n workflows for automation tasks.
n8n workflow automation patterns and API integration.
Creates an HTTP endpoint that triggers workflow execution:
npx skills add https://github.com/89jobrien/steve --skill n8nAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 45 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Author and manage n8n automation workflows using their JSON structure, webhooks, and REST API.
Who is it for?
Developers building n8n workflows or managing n8n programmatically through its REST API.
Skip if: Users of other automation platforms, or those without an n8n instance and API key.
When should I use this skill?
Creating n8n workflows, using webhooks, managing workflows via the REST API, or integrating n8n with MCP servers.
What you get
Valid n8n workflow JSON and correct REST API calls to create, update, and activate workflows.
- n8n workflow JSON
- webhook endpoint
- REST API integration
By the numbers
- 4 common workflow patterns (webhook, HTTP request, IF, SplitInBatches)
- 6 documented expression syntax forms
Files
n8n Workflow Automation Skill
This skill enables creating and managing n8n workflows for automation tasks.
Prerequisites
n8n instance running with API access:
N8N_HOST=localhost
N8N_PORT=5678
N8N_API_KEY=your-api-keyCore Concepts
Workflow Structure
Every n8n workflow is JSON with this structure:
{
"name": "Workflow Name",
"nodes": [],
"connections": {},
"settings": {
"executionOrder": "v1"
}
}Node Structure
Each node has:
{
"id": "unique-id",
"name": "Display Name",
"type": "n8n-nodes-base.nodetype",
"typeVersion": 1,
"position": [x, y],
"parameters": {},
"credentials": {}
}Connection Structure
Connections define data flow between nodes:
{
"Source Node": {
"main": [
[{"node": "Target Node", "type": "main", "index": 0}]
]
}
}Common Workflow Patterns
1. Webhook-Triggered Workflow
Creates an HTTP endpoint that triggers workflow execution:
{
"name": "Webhook Handler",
"nodes": [
{
"id": "webhook",
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"typeVersion": 2,
"position": [250, 300],
"webhookId": "my-webhook",
"parameters": {
"path": "my-endpoint",
"httpMethod": "POST",
"responseMode": "responseNode"
}
},
{
"id": "respond",
"name": "Respond",
"type": "n8n-nodes-base.respondToWebhook",
"typeVersion": 1.1,
"position": [450, 300],
"parameters": {
"respondWith": "json",
"responseBody": "={{ $json }}"
}
}
],
"connections": {
"Webhook": {
"main": [[{"node": "Respond", "type": "main", "index": 0}]]
}
}
}Access at: http://localhost:5678/webhook/my-endpoint
2. HTTP Request Pattern
Make external API calls:
{
"id": "http",
"name": "HTTP Request",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [450, 300],
"parameters": {
"method": "POST",
"url": "https://api.example.com/endpoint",
"authentication": "predefinedCredentialType",
"nodeCredentialType": "myApiCredential",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "={{ JSON.stringify($json) }}"
},
"credentials": {
"myApiCredential": {"id": "cred-id", "name": "My Credential"}
}
}3. Conditional Branching (IF Node)
Route data based on conditions:
{
"id": "if",
"name": "IF",
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"position": [450, 300],
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "strict"
},
"conditions": [
{
"leftValue": "={{ $json.status }}",
"rightValue": "success",
"operator": {
"type": "string",
"operation": "equals"
}
}
],
"combinator": "and"
}
}
}4. Loop Over Items (SplitInBatches)
Process items in batches:
{
"id": "batch",
"name": "Loop Over Items",
"type": "n8n-nodes-base.splitInBatches",
"typeVersion": 3,
"position": [450, 300],
"parameters": {
"batchSize": 10,
"options": {}
}
}n8n REST API
List Workflows
curl -s "http://localhost:5678/api/v1/workflows" \
-H "X-N8N-API-KEY: $N8N_API_KEY"Get Workflow
curl -s "http://localhost:5678/api/v1/workflows/{id}" \
-H "X-N8N-API-KEY: $N8N_API_KEY"Create Workflow
curl -s -X POST "http://localhost:5678/api/v1/workflows" \
-H "X-N8N-API-KEY: $N8N_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "New Workflow", "nodes": [...], "connections": {...}}'Update Workflow
curl -s -X PUT "http://localhost:5678/api/v1/workflows/{id}" \
-H "X-N8N-API-KEY: $N8N_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Updated", "nodes": [...], "connections": {...}}'Activate/Deactivate
curl -s -X POST "http://localhost:5678/api/v1/workflows/{id}/activate" \
-H "X-N8N-API-KEY: $N8N_API_KEY"
curl -s -X POST "http://localhost:5678/api/v1/workflows/{id}/deactivate" \
-H "X-N8N-API-KEY: $N8N_API_KEY"Get Executions
curl -s "http://localhost:5678/api/v1/executions?workflowId={id}&limit=10&includeData=true" \
-H "X-N8N-API-KEY: $N8N_API_KEY"Expression Syntax
n8n uses expressions for dynamic values:
| Syntax | Description |
|---|---|
={{ $json.field }} | Access current item field |
={{ $json.body.param }} | Access nested field |
={{ $('Node Name').item.json.field }} | Access output from specific node |
={{ $input.first().json }} | First input item |
={{ $input.all() }} | All input items |
={{ JSON.stringify($json) }} | Convert to JSON string |
Common Node Types
| Node | Type | Purpose |
|---|---|---|
| Webhook | n8n-nodes-base.webhook | HTTP trigger |
| HTTP Request | n8n-nodes-base.httpRequest | API calls |
| Respond to Webhook | n8n-nodes-base.respondToWebhook | Return HTTP response |
| IF | n8n-nodes-base.if | Conditional branching |
| Switch | n8n-nodes-base.switch | Multi-way branching |
| Set | n8n-nodes-base.set | Transform data |
| Code | n8n-nodes-base.code | Custom JavaScript |
| Split In Batches | n8n-nodes-base.splitInBatches | Loop processing |
| Merge | n8n-nodes-base.merge | Combine branches |
MCP Integration
n8n can expose workflows as MCP tools via the built-in MCP server:
1. Enable MCP in workflow settings: "availableInMCP": true 2. Access MCP endpoint: http://localhost:5678/mcp-server/http 3. Use supergateway for Claude Code integration
Tips
1. Webhook Response: Use responseMode: "responseNode" with Respond node for control 2. Credentials: Store API keys in n8n credentials, reference by ID 3. Error Handling: Add Error Trigger node for failure notifications 4. Testing: Use /webhook-test/ path during development 5. ADF Format: Jira/Confluence require Atlassian Document Format for rich text
# Example Asset File
This placeholder represents where asset files would be stored.
Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
Asset files are NOT intended to be loaded into context, but rather used within
the output Claude produces.
Example asset files from other skills:
- Brand guidelines: logo.png, slides_template.pptx
- Frontend builder: hello-world/ directory with HTML/React boilerplate
- Typography: custom-font.ttf, font-family.woff2
- Data: sample_data.csv, test_dataset.json
## Common Asset Types
- Templates: .pptx, .docx, boilerplate directories
- Images: .png, .jpg, .svg, .gif
- Fonts: .ttf, .otf, .woff, .woff2
- Boilerplate code: Project directories, starter files
- Icons: .ico, .svg
- Data files: .csv, .json, .xml, .yaml
Note: This is a text placeholder. Actual assets can be any file type.
Reference Documentation for N8n
This is a placeholder for detailed reference documentation. Replace with actual reference content or delete if not needed.
Example real reference docs from other skills:
- product-management/references/communication.md - Comprehensive guide for status updates
- product-management/references/context_building.md - Deep-dive on gathering context
- bigquery/references/ - API references and query examples
When Reference Docs Are Useful
Reference docs are ideal for:
- Comprehensive API documentation
- Detailed workflow guides
- Complex multi-step processes
- Information too lengthy for main SKILL.md
- Content that's only needed for specific use cases
Structure Suggestions
API Reference Example
- Overview
- Authentication
- Endpoints with examples
- Error codes
- Rate limits
Workflow Guide Example
- Prerequisites
- Step-by-step instructions
- Common patterns
- Troubleshooting
- Best practices
Related skills
FAQ
What does the n8n skill cover?
Workflow JSON structure, node patterns, the n8n REST API for workflow CRUD and activation, and n8n expression syntax.
What do I need to use it?
An n8n instance running with API access, configured via N8N_HOST, N8N_PORT, and N8N_API_KEY.