Skip to content

feat: n8n article#62

Open
gerard-g-dm wants to merge 1 commit intomasterfrom
blog/n8n-article
Open

feat: n8n article#62
gerard-g-dm wants to merge 1 commit intomasterfrom
blog/n8n-article

Conversation

@gerard-g-dm
Copy link
Copy Markdown
Contributor

This pull request adds a comprehensive French-language tutorial post on using n8n locally with Ollama and Qdrant for building an AI-powered document chat system. The article covers project setup, workflow creation, integration details, and a critical review of n8n's strengths and limitations.

Major additions and improvements:

New Tutorial Content

  • Added a detailed guide (_posts/2026-03-19-n8n.md) explaining how to set up n8n, Qdrant, and Ollama using Docker Compose, including configuration recommendations and security considerations.
  • Provided step-by-step instructions for creating two n8n workflows: one for indexing markdown documents into Qdrant, and one for building a chat agent using local LLMs and the vector database.

Integration Guidance

  • Included model selection advice for Ollama, with compatibility notes for embedding and chat models, and instructions for connecting n8n to both Qdrant and Ollama.
  • Detailed the setup of credentials and nodes within n8n to enable seamless document ingestion and AI-powered chat.

Critical Analysis

  • Concluded with a thorough review of n8n, outlining its advantages (visual interface, modularity, extensibility, open-source nature) and significant drawbacks (security risks

@gerard-g-dm gerard-g-dm self-assigned this Apr 19, 2026
Copy link
Copy Markdown
Collaborator

@thomasorgeval thomasorgeval left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

c'est intéressant !!

Comment thread _posts/2026-03-19-n8n.md
author: Gwenolé
title: Utilisation de n8n en local avec Ollama
categories:
- n8N
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo n8n au lieu de n8N non ?

Comment thread _posts/2026-03-19-n8n.md
Comment thread _posts/2026-03-19-n8n.md

Les paramètres ci-dessus sont volontairement largement ouverts pour faciliter le développement et l'expérimentation. **Si vous exposez votre instance n8n sur le web** (nécessaire pour l'intégrer à d'autres services), vous devez absolument restreindre ces paramètres.

n8n est devenue une cible privilégiée pour les attaquants en raison de sa popularité, et plusieurs CVE critiques ont été découverts. Respectez le principe du moindre privilège : n'autorisez que ce qui est strictement nécessaire.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

découverts -> découvertes

Comment thread _posts/2026-03-19-n8n.md
docker ps
```

Vous devriez voir n8n et Qdrant s'exécuter. L'interface de n8n est accessible à **localhost:5678** et le tableau de bord de Qdrant à **http://127.0.0.1:6333/dashboard**.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tu utilises 2 origines locales, je ne sais pas si pour uniformiser il faudrait utiliser soit l'un ou soit l'autre ? et pour localhost:5678 on pourrait ajouter http:// devant

Comment thread _posts/2026-03-19-n8n.md
- Choisissez **"Add documents to vector store"**

**Configuration Qdrant** :
- Créez un nouveau credential Qdrant avec l'URL : `http://qdrant:6333`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

c'est normal le qdrant en url ? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants