agentleFS
realjaymesrealjaymes/marketingagentskills/skills/n8n-automation/SKILL.md

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

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
  1. Distinctive:

    Consider rate limits and quotas

    line 57
  2. Distinctive:

    Use the node reference to find:

    line 61
  3. Distinctive:

    Test each node individually

    line 69
  4. Distinctive:

    Use test data before production

    line 70
  5. Distinctive:

    When configuring AI agent prompts:

    line 108
  6. Distinctive:

    IF, Switch, Merge, Split

    line 173
  7. Distinctive:

    Always consider rate limits when designing workflows

    line 183
  8. Distinctive:

    Test with small data sets before scaling

    line 184
  9. Distinctive:

    Use credentials properly (never hardcode secrets)

    line 186
  10. Distinctive:

    Consider execution timeout limits

    line 187
  11. Distinctive:

    Document complex workflows for maintainability

    line 188

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ComponentPurpose
Trigger nodesStart workflows (webhooks, schedules, app events)
Regular nodesProcess data, call APIs, transform data
AI nodesLLM calls, agents, tools, memory
Core nodesControl 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

  1. Identify trigger type
  2. List required integrations
  3. Define data transformations
  4. Plan error handling
  5. 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 Destination

Notification Pattern

Trigger (Event) → Filter/Condition → Format Message → Send Notification

AI Agent Pattern

Trigger → AI Agent Node → Tools (API calls, Search) → Response Handler

Multi-Step Processing

Trigger → Split Data → Process Each → Merge Results → Output

AI 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:

  1. Define the agent's role clearly
  2. Specify available tools and when to use them
  3. Set output format expectations
  4. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.