Door 02 · For Builders

The n8n workflow powerhouse.

A public collection of diverse, production-shaped n8n workflows focused on AI, agentic systems, and automation. Clone it. Read it. Ship from it.

33

Workflow templates

JSON

Aggregated for LLM analysis

MCP

Tool integration patterns

Public

Clone, read, iterate

01 · Inside the repo

What you're cloning.

{ }

.json workflow files

Ready-to-import templates covering AI document parsing, agentic chatbots, social media automation, and local LLM integration.

Aggregated raw JSON

One file containing every workflow's JSON — perfect for feeding into a large-context LLM to analyze n8n patterns end-to-end.

Titles + descriptions

A browsable, searchable list (this page) mapping filenames to short descriptions so you can find what you need fast.

02 · Method

Feed it to an LLM.

The aggregated JSON + descriptive metadata aren't just for n8n import — they become a learning substrate when combined with a frontier LLM (Claude, Gemini, GPT — anything with a serious context window). Ask it things like:

  • Explain common patterns for integrating local Ollama models across these workflows.
  • Walk me through the RAG chatbot workflow node-by-node.
  • Draft a new workflow JSON that combines X and Y.
  • What are common parameters for the HTTP Request node in these POSTs?
  • Generate a README draft from this workflow's JSON.
prompt.md● markdown
# Context
I've attached:
- 0. workflows.diy — n8n — public repo.md
  (aggregated JSON of all workflows)
- 1. Workflow Titles and Descriptions.md

# Task
Based on the attached workflows, can you explain the
common patterns used for integrating local Ollama models
for private AI tasks? Reference examples like the
"Private & Local Ollama Self-Hosted + Dynamic LLM Router".

# Output
Return a structured breakdown:
1. shared architectural patterns
2. node-level configuration deltas
3. one annotated example

This is the AI-First way to learn n8n — pair programming, but for patterns.

03 · Index

33 / 33 workflows.

04 · Import

Import a workflow.

  1. 01Open the .json file on GitHub.
  2. 02Select all & copy the JSON content.
  3. 03In n8n, open an empty workflow or the workflows list.
  4. 04Click empty canvas & paste.

Configuration is key

  • Most workflows contain PLACEHOLDER values. Replace them with your own keys, URLs, IDs.
  • Ensure credentials are configured in n8n for services like OpenAI, Google, Telegram.
  • Test thoroughly after configuring.

05 · Prereqs

What you'll need.

  • An n8n instance (cloud or self-hosted).
  • Credentials for services used by a given workflow (OpenAI, Google Cloud, Telegram, WordPress, Ollama API, etc).
  • Optionally, n8n Community Nodes and/or npm packages (e.g. youtube-transcript) if a Code node imports externals.
  • Familiarity with the underlying services helps for troubleshooting and customization.
Disclaimer

These workflows are provided as-is, for educational use. Use at your own risk. Be mindful of API costs, rate limits, and each provider's terms of service.

Hire

Want custom n8n + AI built for your stack?

Templates get you 80% there. The last 20% — integration, auth, edge cases, orchestration — is where most projects stall. Hire me to finish the job.