Prompt
The Prompt component — render a text template, filling its parameters with values from earlier steps.
The Prompt component renders a text template, filling in values from earlier steps. It's a deterministic step — no model is involved — so it's a lightweight way to shape text, such as building a message for an agent or an input for an API call.
The template
Click Template on the card to write the text. Wherever a value should go, write a parameter in double braces:
Summarize the following ticket for {{customer_name}}:
{{ticket_body}}Parameters
Each {{name}} in the template declares a parameter — an input of the node,
listed on the card under the template. Bind each one like any other input: click it
to open the mapper and pick the upstream value, or type a literal. The template
editor shows parameters in green once they're bound and amber until they are.
- Parameter names are bare names — letters, digits,
_, and-, starting with a letter or_. - Every parameter is required: an unbound one is a validation error that blocks deployment.
- Remove a
{{name}}from the text and its binding goes with it. - Values are inserted as text: numbers as written, true/false as
True/False, objects and lists as JSON, and an empty value as nothing.
A dotted placeholder such as {{ticket.body}} isn't a parameter — it stays in the
text as written, and validation warns you. Declare {{body}} instead, and bind it
to the ticket's body field in the mapper.
The same parameters work in an Agent node's System
Instructions on the canvas, so an agent's instructions can be composed from live
data. There, {{input}} is special: it's filled with the agent's input
automatically.
How it connects
The Prompt outputs the rendered text. A common pattern is to wire it into an
Agent node, where it becomes the agent's input —
the message it works on. To use a Prompt's text as an agent's instructions
instead, write {{instructions}} in the agent's System Instructions and bind that
parameter to the Prompt's output.