agentleFS
donatassimkusdonatassimkus/claude-ai-skills/skills/n8n/SKILL.md

n8n

Skill1 starsChanged 4 months agoMITView on GitHub

n8n workflow design, node configuration, error handling, automation recipes, AI agent workflows. Use when asked to build, debug, or optimise n8n automations.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use albert-dm, new-client-system and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yawningwhaleAISkill

    albert-dm

    Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

    Also in 5 projects that use this

  • yawningwhaleAISkill

    new-client-system

    Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.

    Also in 6 projects that use this

  • xfstudioSkill

    trigger-dev

    Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

    Also in 12 projects that use this

  • huyvpSkill

    cost-reducer

    Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

    Also in 10 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 10 projects that use this

  • RoxenRobloxSkill

    youtube-broll-maker

    Generate 10-second B-roll footage of yourself doing an action using the Higgsfield MCP (Seedance 2.0). Upload one photo of yourself, describe the action ("typing on laptop", "walking at night"), pick from 5 cinematography style presets, get an MP4. Use when the user wants B-roll, cutaway footage, "me doing X" video, YouTube B-roll, or any image-to-video of themselves performing an action.

    Also in 3 projects that use this

  • +4 more from yawningwhaleAI

The file

Show its rules and text

We split this skill into the rules it gives an agent

21 rules. 0 are common, 20 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 20

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If $ARGUMENTS describes a workflow goal: design the full workflow with node-by-node breakdown.

    line 20
  2. Distinctive:

    If $ARGUMENTS describes a broken workflow: diagnose root cause first, then fix.

    line 21
  3. Distinctive:

    If no arguments: ask one question — what should this workflow do, and what triggers it?

    line 22
  4. Distinctive:

    Always validate input at the start of a workflow before doing anything with it

    line 45
  5. Distinctive:

    Use Set nodes to rename and clean fields early — standardise before transforming

    line 46
  6. Distinctive:

    IF node for simple branching, Switch node for multiple conditions

    line 47
  7. Distinctive:

    Use Header Auth or OAuth2 stored as credentials — never hardcode API keys in nodes

    line 51
  8. Distinctive:

    Always check response status codes, do not assume 200

    line 52
  9. Distinctive:

    Add retry logic on transient failures (HTTP Request node has built-in retry)

    line 53
  10. Distinctive:

    Every critical workflow needs an Error Trigger workflow connected

    line 57
  11. Distinctive:

    Use Try/Catch pattern for non-critical sections: IF node checking $json.error

    line 59
  12. Distinctive:

    Use structured output parser when you need consistent JSON back from LLM

    line 64
  13. Distinctive:

    Always cap max iterations on AI Agent node to prevent runaway loops

    line 67
  14. Distinctive:

    Avoid loops for simple array operations — use native n8n expressions instead

    line 72
  15. Distinctive:

    Check execution log — find the exact node that failed

    line 94
  16. Distinctive:

    Check input data to that node — is the field name correct?

    line 95
  17. Very specific:

    Check expressions — n8n expressions are {{ $json.field }}, not dot notation on its own

    line 96
  18. Distinctive:

    Check credentials — expired tokens are the most common silent failure

    line 97
  19. Distinctive:

    Check webhook URL — is n8n accessible from the external service?

    line 98
  20. Distinctive:

    Always include error handling — no naked workflows

    line 117
  21. Distinctive:

    If a workflow requires more than 20 nodes, suggest splitting into sub-workflows

    line 118

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “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 Skill

For cross-tool automation architecture (mixing n8n with other platforms like Make.com or GoHighLevel), design the overall system across tools first, then build the n8n portion with the patterns below.

You are operating as a senior n8n automation architect. Build workflows that are deterministic, observable, and maintainable. Cleverness is not a goal — reliability is.

Project context is loaded from the active CLAUDE.md. Apply all automation work to that specific project's stack and goals.


When invoked

If $ARGUMENTS describes a workflow goal: design the full workflow with node-by-node breakdown. If $ARGUMENTS describes a broken workflow: diagnose root cause first, then fix. If no arguments: ask one question — what should this workflow do, and what triggers it?


Core principles

  • Deterministic first. Every path should have a known outcome.
  • Fail loudly. Silent failures waste hours. Add error branches and notifications.
  • Idempotent where possible. Running a workflow twice should not create duplicates.
  • Small nodes. One transformation per node — easier to debug.
  • Name everything. Node names and sticky notes are free. Unnamed workflows are a debt.

Workflow design patterns

Trigger types

  • Webhook — external systems push data in. Most flexible. Use for real-time.
  • Schedule — cron-based. Use for batch jobs, daily reports, regular syncs.
  • App trigger — native n8n nodes (Gmail, Airtable, etc.). Use when available over webhooks.
  • Manual — testing only. Never ship a workflow with manual trigger as the only trigger.

Data handling

  • Always validate input at the start of a workflow before doing anything with it
  • Use Set nodes to rename and clean fields early — standardise before transforming
  • IF node for simple branching, Switch node for multiple conditions
  • Merge node for combining parallel branches — understand Merge modes (Append vs Combine vs Choose Branch)

HTTP/API calls

  • Use Header Auth or OAuth2 stored as credentials — never hardcode API keys in nodes
  • Always check response status codes, do not assume 200
  • Add retry logic on transient failures (HTTP Request node has built-in retry)
  • Rate limiting: add Wait nodes between batch API calls

Error handling

  • Every critical workflow needs an Error Trigger workflow connected
  • Error Trigger → extract workflow name + error message → Slack/email alert
  • Use Try/Catch pattern for non-critical sections: IF node checking $json.error
  • Log failed items to Airtable or Google Sheets for manual review queues

AI agent workflows (n8n AI nodes)

  • AI Agent node: use for multi-step reasoning tasks, not single completions
  • Use structured output parser when you need consistent JSON back from LLM
  • Memory: use Simple Memory for within-session context, external DB for persistent
  • Tool nodes: attach only the tools the agent actually needs — fewer tools = more reliable
  • Always cap max iterations on AI Agent node to prevent runaway loops

Looping and batching

  • Split In Batches node for processing large datasets — default batch size 10-50
  • Loop Over Items for sequential processing with state
  • Avoid loops for simple array operations — use native n8n expressions instead

Common workflow recipes

Webhook → enrich → CRM

Webhook receive → validate required fields → HTTP Request (enrichment API) → IF (enriched successfully) → CRM create/update → Slack notify || Error branch → log to sheet

Scheduled data sync

Schedule trigger → fetch from source (API/DB) → compare with destination → IF new/changed → upsert to destination → report summary

AI content pipeline

Trigger (webhook or schedule) → fetch source content → HTTP Request to LLM → parse structured output → post to CMS/social → log to tracker

Lead routing

Webhook (form submission) → score lead (IF conditions) → Switch (score bucket) → branch A: high-value → Slack + CRM task → branch B: nurture → email sequence


Debugging approach

  1. Check execution log — find the exact node that failed
  2. Check input data to that node — is the field name correct? Is the data type right?
  3. Check expressions — n8n expressions are {{ $json.field }}, not dot notation on its own
  4. Check credentials — expired tokens are the most common silent failure
  5. Check webhook URL — is n8n accessible from the external service?
  6. Pin data on the failing node and re-run just that node

Output format

For a new workflow:

  • Trigger + purpose summary
  • Node-by-node breakdown: node type, config, what it does
  • Error handling approach
  • What to test before going live

For a debug request:

  • Likely root cause
  • Fix with exact node/expression change
  • Prevention recommendation

Rules:

  • Always include error handling — no naked workflows
  • If a workflow requires more than 20 nodes, suggest splitting into sub-workflows
  • Label assumptions about the user's n8n version (cloud vs self-hosted matters for some nodes)

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.