Skip to article
/ docs

Search documentation

Popular starting points. Search all 37 articles.

  • Get startedProduct availability and preview limitationsUnderstand what works in the frontend and which product capabilities are not connected yet.
  • Get startedBuild your first RAG pipelineBuild and inspect your first seven-node Basic RAG graph and learn what validation means.
  • Build pipelinesBasic RAG and Hybrid Search templatesCompare Ragify's two starting graphs and decide which pattern to explore.
  • Node referenceUnderstand the node libraryBrowse the ten registered node types by role in the workflow.

↑ ↓ to navigate · Enter to open · Esc to close

Back to Ragify ↗
On this page

Documentation

Configurable frontend node; processing planned

Chunker

Represent text splitting between document loading and embedding.

Category: Processing. Registry label: Chunker.

Purpose #

Chunking splits larger text into smaller passages so retrieval can operate on manageable units. The appropriate strategy depends on document structure and the question patterns an application must support.

Position in the graph #

Document Loader → Chunker → Embedder

Design guidance #

Use this node after Document Loader and before Embedder. Open its configuration dialog to inspect the actual controls available in the current editor. When reasoning about a future runtime, consider the relationship between chunk boundaries, overlap, and retrieval quality, but do not assume a specific splitter implementation is active.

Current limitation #

No document bytes are processed into real chunks by the frontend preview.

Embedder, Configure nodes.