Chunker
These chunker nodes apply AI-powered enhancements to existing chunks rather than splitting content by character or structure.Workflow placement
- Place the Contextual chunking node after one of the standard text chunkers (such as
chunk_by_character,chunk_by_page,chunk_by_similarity, orchunk_by_title), as it enriches existing chunks rather than creating them. - The Chunk by Table Merging node pairs well with a Table to HTML enrichment earlier in the workflow.
Embedder
Configure an Embedder node to convert chunked document elements into vector embeddings for similarity search in vector stores.Extract
Learn about the available extraction methods.Prompter
Learn about the available enrichments.Workflow placement
- Always place enrichment nodes after a Partitioner node.
-
Place enrichment nodes before Chunker nodes, unless otherwise noted.
- For example, a
table2htmlenrichment is often paired with achunk_by_table_mergingnode later in the workflow. - An exception is the NER enrichment, which should be placed after any Chunker nodes.
- For example, a
-
When more than one enrichment writes to the same element’s
textfield, all of the results are kept. This applies, for example, to an image description enrichment and an OCR enrichment on the same image. Each result is labeled with the name of the enrichment that produced it, in the order that the enrichment nodes run. Learn how Unstructured combines enrichment results.

