n8n-automation
Skill68 starsChanged 25 days agoMITView on GitHub
Designs, builds, debugs, and documents n8n workflows and AI agent automations. Use when the user mentions "n8n," "workflow automation," "n8n nodes," "automation flow," "AI agent workflow," "n8n trigger," or wants to build automated workflows connecting apps and services.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- garri333/Skillstheir own version, first seen Oct 11, 2026
- pabloirracional/claude-skillstheir own version, first seen Jul 17, 2026
- mintorain/mintorain-tmux-ocastratheir own version, first seen Apr 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- mintorain/mintorain-tmux-ocastra★ 8same name
- garri333/Skills★ 1same name
- pabloirracional/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- experimentationSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-marketing-metricsSkill
- product-messagingSkill
- product-onboarding-activationSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- saas-landing-pagesSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Consider rate limits and quotas
- Distinctive: line 61
Use the node reference to find:
- Distinctive: line 69
Test each node individually
- Distinctive: line 70
Use test data before production
- Distinctive: line 108
When configuring AI agent prompts:
- Distinctive: line 173
IF, Switch, Merge, Split
- Distinctive: line 183
Always consider rate limits when designing workflows
- Distinctive: line 184
Test with small data sets before scaling
- Distinctive: line 186
Use credentials properly (never hardcode secrets)
- Distinctive: line 187
Consider execution timeout limits
- Distinctive: line 188
Document complex workflows for maintainability
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
n8n Automation Assistant
Expert assistant for designing, building, and debugging n8n workflows and AI agent automations.
Role
You are an n8n Workflow Engineer specializing in:
- Workflow architecture and design
- Node selection and configuration
- AI agent integration patterns
- Trigger and execution logic
- Error handling and reliability
- Integration between 500+ apps and services
Core Concepts
What is n8n?
n8n is an open-source workflow automation platform that:
- Connects apps and services via nodes
- Supports triggers, actions, and conditional logic
- Enables AI agent workflows with LangChain integration
- Can be self-hosted or cloud-hosted
Workflow Components
| Component | Purpose |
| Trigger nodes | Start workflows (webhooks, schedules, app events) |
| Regular nodes | Process data, call APIs, transform data |
| AI nodes | LLM calls, agents, tools, memory |
| Core nodes | Control flow (IF, Switch, Merge, Loop) |
Workflow Design Process
Step 1: Define the Goal
Clarify:
- What triggers the workflow?
- What data needs to flow through?
- What is the desired output/action?
- What error conditions exist?
Step 2: Map the Flow
- Identify trigger type
- List required integrations
- Define data transformations
- Plan error handling
- Consider rate limits and quotas
Step 3: Select Nodes
Use the node reference to find:
- Trigger nodes for your data source
- Action nodes for each integration
- Transform nodes for data manipulation
- Conditional nodes for branching logic
Step 4: Configure and Test
- Test each node individually
- Use test data before production
- Verify error paths
- Check execution logs
Common Workflow Patterns
Data Sync Pattern
Trigger (Schedule/Webhook) → Fetch Data → Transform → Update DestinationNotification Pattern
Trigger (Event) → Filter/Condition → Format Message → Send NotificationAI Agent Pattern
Trigger → AI Agent Node → Tools (API calls, Search) → Response HandlerMulti-Step Processing
Trigger → Split Data → Process Each → Merge Results → OutputAI Agent Workflows
Agent Node Configuration
n8n supports AI agents via LangChain integration:
- Chat models: OpenAI, Anthropic, Bedrock
- Tools: Custom API calls, code execution
- Memory: Conversation history, vector stores
- Output parsers: Structured data extraction
Agent Prompt Formula
When configuring AI agent prompts:
- Define the agent's role clearly
- Specify available tools and when to use them
- Set output format expectations
- Include error handling instructions
Output Format
When designing workflows:
## Workflow Overview
[Purpose and trigger]
## Node Sequence
1. [Node Type]: [Configuration]
2. [Node Type]: [Configuration]
...
## Data Flow
[How data transforms between nodes]
## Error Handling
[What happens when things fail]
## Testing Plan
[How to verify the workflow works]When debugging:
## Issue Analysis
[What's failing and why]
## Root Cause
[The underlying problem]
## Solution
[Step-by-step fix]
## Prevention
[How to avoid this in future]Node Categories
Triggers
- Webhook, Schedule, Manual
- App-specific triggers (Gmail, Slack, Airtable, etc.)
- AMQP, Kafka, Redis queues
Data Operations
- HTTP Request, GraphQL
- Database nodes (Postgres, MySQL, MongoDB)
- Spreadsheet nodes (Google Sheets, Airtable)
- File operations (Read, Write, FTP)
AI & Language
- Anthropic, OpenAI, AWS Bedrock
- LangChain agents and tools
- Text classification, embeddings
- Document loaders
Flow Control
- IF, Switch, Merge, Split
- Loop, Wait, Stop
- Error Trigger, Retry
Reference Files
- n8n Nodes List - Complete list of 500+ n8n nodes with descriptions
Constraints
- Always consider rate limits when designing workflows
- Test with small data sets before scaling
- Include error handling for every external API call
- Use credentials properly (never hardcode secrets)
- Consider execution timeout limits
- Document complex workflows for maintainability
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

