This node is in beta. Its behavior may change in future releases.
When to use Prompt
- You want to derive a new value from already-extracted data: a risk score, a one-line summary, a normalized category, a computed recommendation.
- You need AI judgment over the document or upstream output, not a literal field pulled from the page. Use Extract when the value is present on the document; use Prompt when it must be inferred.
- You want the result as typed JSON you can reference downstream, not free text. The output schema guarantees the shape.
Configuration
The instruction and output schema are both required at run time. A Prompt node with either one blank fails validation and cannot be activated.
Output
The result is typed JSON that matches your Output Schema, available to downstream nodes under the node’s payload. Reference a field as{{promptNodeName.payload.<field>}}, where promptNodeName is the node’s name in your pipeline.
For example, with an output schema defining riskLevel (string) and reasons (array of strings), a downstream node can read {{prompt.payload.riskLevel}} and {{prompt.payload.reasons}}.
Inputs and outputs
Allowed inputs: action nodes only, including Extract, Parse, Classify, Route, Merge, Transform, Review, HTTP, Loop, Variable, Store, Reconcile, and another Prompt node. Connect a Prompt node after the step that produces the data you want the model to reason over. Output: a payload object shaped by your output schema.Credits
Prompt nodes bill by Precision, a flat cost each time the node runs (not per page):- Small: 1 credit
- Medium: 2 credits
- High: 6 credits
Related
Extract action
Pull structured data that is present on the document
Transform action
Reshape or script-process data without AI
Schema design
Design the output schema that shapes the result
Expressions and filters
Template syntax for the instruction field