Skip to content

The n8n workflow repository

33 public n8n workflows for AI and automation. Clone the repository or import any file.

Every workflow in the repository

Matches file names and descriptions. Press / to jump here.

Showing 33 of 33 workflows

What the repository contains

.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 with the JSON for every workflow, for a large-context LLM to read.
Titles and descriptions
The searchable list on this page, mapping each file name to a short description.

Learn the patterns with an LLM

Give the aggregated JSON and the descriptions to any model with a large context window, such as Claude, Gemini or GPT. Then ask questions like these.

  • 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 two of these workflows.
  • What are common parameters for the HTTP Request node in these POST calls?
  • Generate a README draft from this workflow's JSON.
# 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
An example prompt that uses the two files from the repository.

Import a workflow

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

Before you run it

  • Most workflows contain PLACEHOLDER values. Replace them with your own keys, URLs and IDs.
  • Configure credentials in n8n for services such as OpenAI, Google and Telegram.
  • Test the workflow before you rely on its output.

What you need

  • An n8n instance, cloud or self-hosted.
  • Credentials for the services a workflow uses, such as OpenAI, Google Cloud, Telegram, WordPress or the Ollama API.
  • Optionally, n8n community nodes or npm packages (for example youtube-transcript) when a Code node imports them.
  • Familiarity with the underlying services. It helps when something breaks.

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

Stuck after importing a template?

Credentials, auth and edge cases are what a template leaves open. I can review the workflow and finish those parts for your team.