Skip to main content
View source

Answers to Documents

View as Markdown

A RocketRide adapter node that turns answers into embeddable documents while preserving the answers lane. Pick it after a model or agent when its answers need to be indexed for later retrieval rather than only sent to a response.

What it does​

The node reads answers and emits one or more documents on documents; the original answer continues on answers. A JSON array produces one document for each item, while a JSON object or non-empty plain-text answer produces one document. Use it to bridge an answer-producing node to an embedding and store pipeline, particularly when each item in a structured answer should be retrievable independently.

Documents are made only when a downstream listener consumes documents. Empty or whitespace text and JSON null produce no documents, while a malformed JSON answer falls back to its non-empty text representation.

Lanes​

Lane inLane outDescription
answersdocumentsEmit one document for each answer item when a downstream listener needs documents.
answersanswersKeep the original answer available to downstream answer consumers.

Configuration​

This node has no configuration fields. Wire an answer-producing node into answers, connect documents to an embedding or storage path when indexing is needed, and retain the answers path when the same result must still be served in the current run.

Notes​

Document content and metadata​

String items in a JSON array become page_content verbatim; object and other non-string items are JSON-serialized with non-ASCII characters preserved. Each emitted document has a chunkId that starts at zero for each input object, and is marked as non-table, active text content. Its remaining provenance metadata is populated from the pipeline context.

Fan-out behavior​

The node writes documents only if a documents listener exists. It does not call a replacement writer for the answers lane, so the engine's normal answer forwarding keeps the exact original answer for downstream consumers.

Schema​

No configuration fields.