Knowledge

The Knowledge block connects a workflow to your knowledge bases. It works with both knowledge-base engines:

RAG knowledge bases — classic vector search over chunked documents.
Memex knowledge bases — the structured, page-based knowledge graph.

The block is engine-aware: pick a knowledge base and the block automatically does the right thing for that engine. You don't choose the engine — the knowledge base already knows what it is.

Operations

Operation	What it does	Engines
Search	Find relevant content for a query	RAG + Memex
Get Document	Retrieve a single document/page's full text by reference	RAG + Memex
Upload Chunk	Append a chunk to an existing document	RAG only
Create Document	Create a new document from text	RAG only

Upload Chunk and Create Document apply to RAG knowledge bases. Memex knowledge bases are written to through ingestion and the Memex authoring surfaces, not from the workflow block.

Get Document

Use Get Document to pull a specific document or page into your workflow so a downstream block (an Agent, an API call, a Function) can use its text.

To retrieve a file stored in a Memex knowledge base, use Get Document here — not the File block. The File block fetches by URL; a Memex page is not a URL, and there is no "path" string that addresses one. Pick the page from the list (or pass its id/slug) and Get Document returns its content.

Configure it

Select Operation → Get Document.

Select the Knowledge Base. For a RAG base the picker lists documents; for a Memex base it lists pages by title.

Pick the Document/Page from the list, or use Reference Override to pass a value from an upstream block. The override accepts:

a Memex page id or slug, or
a RAG document id.

When the override is set, it wins over the picker — handy when an earlier block (a Search, a Function) decides which page to read.

Outputs

Output	Description
`content`	The document/page text. (For RAG documents the body lives in chunks; use Search to retrieve RAG text.)
`metadata`	Title, reference ids, and `fileType`. For a Memex page: `title`, `pageId`, `folderPath`, `slug`.
`documentRef`	The resolved reference id.

Example: read a Memex page, then summarize it

Knowledge → Get Document, select your Memex knowledge base, pick the page (e.g. “RFP Template Rollout”).

Agent block — reference <knowledge.content> in the prompt: “Summarize the following document for a customer email: <knowledge.content>”.

API / Response block — send the summary onward.

This is the supported replacement for trying to feed a Memex file path into the File block.

Search

Select Search, choose the knowledge base, and enter a query. Search runs against whichever engine the knowledge base uses (vector search for RAG, Memex retrieval for Memex) and returns ranked results. Knowledge-base access controls and clearance are always enforced.

Errors you might see

Error	Meaning
`KB_NOT_FOUND`	The selected knowledge base doesn't exist or you can't read it.
`DOCUMENT_NOT_FOUND`	No Memex page matched the id/slug (and folder) you gave.
`DOCUMENT_NOT_FOUND_FOR_ENGINE`	The reference doesn't match a document in this knowledge base's engine (e.g. a RAG document id against a Memex base).