Generate LLM Response
Use this action when you want a workflow step or agent action to send a prompt directly to an LLM and reuse the result in later steps.
Best for
- Summaries, classifications, rewrites, and extraction tasks
- Turning raw API data into natural language
- Producing structured output that later steps can read reliably
Main fields
| Field | What it does |
|---|---|
| Advanced mode | Switches between a simple prompt and a fully configured message-based request |
| Platform | Chooses the LLM provider |
| Model | Chooses the specific model to run (hidden when Platform is OpenRouter — use OpenRouter model instead) |
| OpenRouter model | The model identifier to run on OpenRouter. Shown and required only when Platform is OpenRouter |
| API key | Lets you override the default key when needed. Required when Platform is OpenRouter (bring your own key) |
| Text | Simple prompt field for basic use cases |
| Messages | Advanced prompt format with multiple roles and content types |
| Enable Structured Outputs | Lets you define a schema so the model returns predictable JSON. On its own this still returns plain text — you must also set Structured Output Schema |
| Structured Output Schema | A CEL expression that evaluates to a JSON-Schema string. Required for structured output; without it the toggle returns plain text |
| Structured Output Schema Name | Optional name for the schema (defaults to output) |
| Temperature | Controls how predictable or creative the output is |
| Maximum tokens | Limits the size of the answer |
| Purpose | Optional label for what this step is for, shown in logs (advanced mode only) |
Model, Temperature, Maximum tokens, and the structured-output fields only appear when Advanced mode is turned on; in simple mode you only see Platform, API key, and Text. OpenRouter model appears whenever Platform is OpenRouter.
What later steps can use
The response is available at:
step(N).choicesstep(N).choices[0].message.content
With structured outputs enabled, message.content is returned as a parsed JSON object, so later steps can read its keys directly in conditions, updates, and message templates.
Tips
- Use the simple Text field when you only need one prompt.
- Switch to Advanced mode when you need multiple messages, images, audio, or files.
- Use structured output when later steps need stable keys like
category,score, orsummary— remember to enable the toggle and set Structured Output Schema (a CEL expression that returns a JSON-Schema string). - Debug the step before you build follow-up conditions on the result.