Flovello AI

Description

Asks Flovello AI to produce a value of a chosen model from the given input. Pick the output model in the inspector, describe the task in the instruction, and wire in the source data. Branches on solved/not solved, so the pipeline can handle cases the model could not fulfil. Consumes AI step coins per run.

When to use

Use the Flovello AI step when a piece of the automation needs judgement rather than a fixed rule — extracting structured fields from messy text, classifying or summarising content, or transforming input into a target shape that would be awkward to express with ordinary nodes. Pick the output model in the inspector so the result is strongly typed, write a clear Instruction, and wire the source data into Input.

The node sits on the execution flow and branches: the solved pin fires with a typed Result when the AI produced a value that fits the model; the not-solved pin fires when it could not, so you can fall back or log the case. Each run consumes AI step coins from your plan’s monthly allowance — see the Extra and Enterprise tiers on the pricing page.

This is the in-pipeline AI node, distinct from the Flovello AI assistant that builds and edits whole pipelines from a description in the editor.

Pins

Input pins

Pin	Type	Default	Notes
Instruction	string	—	A natural-language description of what to produce from the input — for example "extract the shipping address" or "classify the sentiment".
Input	model	—	The source data the AI reads to produce its answer. Wire from any node that produces a model.

Output pins

Pin	Type	Notes
Result	model	The produced value, typed to the model selected in the inspector. Available on the `solved` branch. Wire into a Break node to read its fields.

Execution pins

Pin	Direction
In	Input
Solved	Output
Not solved	Output

Example

Extract a structured contact from a free-text enquiry. Wire the parsed request body into the Input of the Flovello AI step, set the Instruction to “extract the sender’s name and email”, and select a Contact model in the inspector. On the Solved execution output, wire the Result into a Break node to read the name and email fields; on the Not solved execution output, wire a Log message node so unhandled enquiries are recorded.