n8n-workflow-patterns

n8n-workflow-patterns is a skill for Claude Code, Codex from PCT-BR/n8n-mcp. It costs 144 tokens per session (4,800 once invoked), scanned A, a copy of n8n-workflow-patterns, MIT.

A guide to common designs for n8n workflows. n8n is a tool for connecting services and automating multi-step tasks.

In plain words
What is it for?
Planning workflows that receive web requests, call APIs, work with databases, use AI agents, run on a schedule, or process data in batches.
Why use it?
It helps you choose a suitable workflow structure instead of designing webhook, API, database, AI, scheduled, or batch flows from scratch.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Planning workflows that receive web requests, call APIs, work with databases, use AI agents, run on a schedule, or process data in batches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pct-br/n8n-mcp/n8n-workflow-patterns
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add PCT-BR/n8n-mcp --skill n8n-workflow-patterns
Clone the repo
git clone --depth 1 https://github.com/PCT-BR/n8n-mcp

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for n8n-workflow-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/pct-br/n8n-mcp/n8n-workflow-patterns/github.svg)](https://agentmods.dev/skills/pct-br/n8n-mcp/n8n-workflow-patterns)
Your own site
<a href="https://agentmods.dev/skills/pct-br/n8n-mcp/n8n-workflow-patterns"><img src="https://agentmods.dev/badge/skills/pct-br/n8n-mcp/n8n-workflow-patterns/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for n8n-workflow-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/pct-br/n8n-mcp/n8n-workflow-patterns"><img src="https://agentmods.dev/badge/skills/pct-br/n8n-mcp/n8n-workflow-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 144 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,800 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00144 $0.04800
Opus 5 $0.00072 $0.02400
Sonnet 5 $0.00029 $0.00960
Haiku 4.5 $0.00014 $0.00480

Measured 9d ago against content hash 10ad2eee8d60, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

n8n-workflow-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

95% identical to n8n-workflow-patterns — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

data/skills/n8n-workflow-patterns/SKILL.md · 547 lines

How it starts

The opening of the file, as written. The whole thing — 547 lines — stays where its author put it; the contents beside it link to each section on GitHub.

n8n Workflow Patterns

Proven architectural patterns for building n8n workflows.


The 6 Core Patterns

Based on analysis of real workflow usage:

  1. Webhook Processing (Most Common)

    • Receive HTTP requests → Process → Output
    • Pattern: Webhook → Validate → Transform → Respond/Notify
  2. HTTP API Integration

    • Fetch from REST APIs → Transform → Store/Use
    • Pattern: Trigger → HTTP Request → Transform → Action → Error Handler
  3. Database Operations

    • Read/Write/Sync database data
    • Pattern: Schedule → Query → Transform → Write → Verify
  4. AI Agent Workflow

    • AI agents with tools and memory
    • Pattern: Trigger → AI Agent (Model + Tools + Memory) → Output
  5. Scheduled Tasks

    • Recurring automation workflows
    • Pattern: Schedule → Fetch → Process → Deliver → Log
  6. Batch Processing (below)

    • Process large datasets in chunks with API rate limits
    • Pattern: Prepare → SplitInBatches → Process per batch → Accumulate → Aggregate

Pattern Selection Guide

When to use each pattern:

Webhook Processing - Use when:

  • Receiving data from external systems
  • Building integrations (Slack commands, form submissions, GitHub webhooks)
  • Need instant response to events
  • Example: "Receive Stripe payment webhook → Update database → Send confirmation"

HTTP API Integration - Use when:

  • Fetching data from external APIs
  • Synchronizing with third-party services
  • Building data pipelines
  • Example: "Fetch GitHub issues → Transform → Create Jira tickets"

Database Operations - Use when:

  • Syncing between databases
  • Running database queries on schedule
  • ETL workflows
  • Example: "Read Postgres records → Transform → Write to MySQL"

AI Agent Workflow - Use when:

  • Building conversational AI
  • Need AI with tool access
  • Multi-step reasoning tasks
  • Example: "Chat with AI that can search docs, query database, send emails"

Read the full file on GitHub · 547 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 547 lines · 144 tokens per session scan A 10ad2eee8d60

Subscribe to this mod's changes

n8n-workflow-patterns is a skill published in the GitHub repository PCT-BR/n8n-mcp (0 stars, last pushed 22d ago), licensed MIT. It adds 144 tokens to every session and 4,800 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to n8n-workflow-patterns, differing in 1 line, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens