Prompt

View as Markdown

A RocketRide transformation node that merges multiple pipeline inputs into a single enriched question before it reaches an LLM or agent.

What it does

Assembles a structured Question object from multiple pipeline inputs and emits it downstream. This is the primary mechanism for injecting retrieved documents, extracted text, and table content into a question before it reaches an LLM or agent node.

Each input lane maps to a different section of the rendered prompt. Inputs are collected as they arrive; the fully assembled question is not emitted until the node is closing, at which point all accumulated inputs are merged with the configured instructions and the enriched question is emitted on the questions lane.

If no instructions are configured, the default profile supplies a single instruction: "Please provide a detailed and helpful response to the following question:". If an error occurs during the merge, the node logs the error and the enriched question is not emitted.

Use Prompt instead of Question when a downstream LLM needs a question together with instructions or accumulated context. Use Question when text only needs to be converted into a question without assembling a prompt.

Lanes

Lane in	Lane out	Description
documents	(none)	Added to the ### Documents: section of the prompt
text	(none)	Added to the ### Context: section of the prompt
table	(none)	Added to the ### Context: section of the prompt
questions	questions	Collects question inputs; emits the fully assembled question when the node closes

Configuration

The default profile supplies one detailed-response instruction. Most pipelines only need to change the setting when their downstream model needs a different role, format, or response constraint.

Instructions

Each instruction is added with the name User Instruction; when multiple instructions are configured they are numbered (User Instruction 1, User Instruction 2, and so on). A single string value is also accepted and treated as a one-element list.

Use a short, specific instruction when the retrieved context already states the task. Add separate instructions when their order matters; they are added in their configured order before the collected context and question.

Requirements

The node is marked GPU-capable in its metadata, but its implementation only assembles a Question object and does not load or call a model itself. Any hardware requirement comes from the downstream LLM or agent that consumes the result.

Notes

Rendered prompt structure

When the question is consumed by an LLM or agent, it is rendered in this order:

### System Instructions:
    1) **User Instruction**: [your configured instructions]

### Context:
    1) [text or table content from text/table lanes]

### Documents:
    Document 1) Content: [document content from documents lane]

### Current Task:
    [question text from questions lane]

---

Typical use

The most common use is passing retrieved documents or extracted text alongside a question into an agent or LLM, giving it context it would not otherwise have.

RAG into an LLM:

           ┌──→ vector store ──→ documents ─┐
source ────┤                                ├──→ Prompt ──→ LLM
           └──────────────── questions ─────┘

Passing context to an agent:

text extractor ──→ text ──────────────────┐
vector store ───→ documents ──────────────┤
                                          ├──→ Prompt ──→ agent
source ─────────→ questions ──────────────┘

---

Schema

Field	Type	Description	Default
instructions	array	Instructions Multiple instructions to add to questions before sending to LLM