Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Text Generation

Use Text Generation to create text from a prompt, or to return a structured result such as an object or a choice from a list.

Configure the action

FieldWhat it does
ProviderThe AI provider to use.
ModelThe model for that provider. The list updates when you change the provider.
Input TypePrompt for a single instruction, or Messages for a conversation.
PromptThe instruction to send. Shown when Input Type is Prompt. You can bind this to a parameter or variable.
MessagesA list of messages with a Role (User, Assistant, or System) and Content. Shown when Input Type is Messages.
SystemOptional instructions for how the model should behave, for example "Reply in one short paragraph."
Stream ResponseSend the text as it is generated, instead of waiting for the full result.
Output TypeText for a normal reply. Object, Array, or Choices when you need a structured result.

If you choose Object or Array, add a Schema that describes the shape you want back. If you choose Choices, add the allowed options in Choices.

Schema Name and Schema Description are optional. They help the model understand what you want.

Learn how to choose a provider →

Use the result

  • For Text, use the action result text.
  • For Object, Array, or Choices, use the action result output.

In the next action, bind those fields from the Text Generation result. For example, return text with Send Response, or save output to a table.

Stream the reply

Turn on Stream Response when you want the interface to show text as it arrives, such as a chat reply.

Then, on the interface action that calls the API Endpoint, open Advanced and enable Handle stream.

Learn more about streaming responses →

Common pitfalls

Structured output fails

If Output Type is Object or Array, the Schema must describe every field you expect. List every property in required. If a value might be empty, keep it required and allow null in the type.

A schema that looks valid but skips required on a nested object is a common reason the action fails.