# Apify blog walks through building a live RAG pipeline with n8n and Qdrant

> Apify published a tutorial showing how to crawl a website, sync changed pages into Qdrant via n8n, and re-embed only the diffs, with measured run times and cost figures.

- Canonical: https://extractfeed.io/story/apify-blog-walks-through-building-a-live-rag-pipeline-with-n-fcb6b67/
- JSON: https://extractfeed.io/api/v1/stories/apify-blog-walks-through-building-a-live-rag-pipeline-with-n-fcb6b67.json
- Beat: Open Source & Tooling · Evidence: Primary source · Type/significance: analysis/2 · First seen: 2026-09-16T23:46:07.277015+00:00 · Updated: 2026-09-16T23:46:07.277015+00:00 · Edition: 2026-11-05
- Framing: model-written (headline, standfirst, why it matters, tags); source facts deterministic

## Briefing
- Apify: Apify published a tutorial showing how to crawl a website, sync changed pages into Qdrant via n8n, and re-embed only the diffs, with measured run times and cost figures.

## Why it matters
This tutorial demonstrates a practical, cost-aware approach to keeping a retrieval-augmented generation (RAG) index fresh without full re-crawls, which is a common pain point for teams building production knowledge bases. By combining Apify's crawling, n8n's workflow automation, and Qdrant's vector storage, it offers a reference architecture that could reduce both compute and API costs for incremental indexing. The inclusion of real cost figures makes it actionable for practitioners evaluating similar pipelines.

## Sources
- Primary source · Apify · 2026-09-16 — [Build a live RAG pipeline with Apify, n8n, and Qdrant](https://blog.apify.com/live-n8n-rag-pipeline/)

## Watch next
Will this incremental re-embedding pattern be adopted as a standard template in n8n's community workflows or Apify's actor library?

Topics: Apify, n8n, Qdrant, rag, crawling, vector-database, workflow-automation, incremental-indexing

---
extractfeed is an agent-readable changefeed for web scraping and data extraction. Index: https://extractfeed.io/agents.md