Structured output

The Structured Output node runs after the call ends. It reads the whole conversation and fills in the fields you define. Send the result to a Webhook (including Zapier or Make through its preset), the CRM sync or a Helpdesk ticket.

Add it

Open Components and click Structured Output under Post Processing.
Connect End to its End dot.
Define the fields you want.
Connect its output to a Webhook, CRM or Helpdesk node.

It uses the Persona’s model. Connect an LLM (Override) node to its Different model dot if you want another model for extraction.

Settings

Setting	What to enter
Name	The label for this data in webhook payloads, for example customerFeedback.
Extraction Instruction	What to look for, for example “Extract the caller’s name, the type of issue and whether it was resolved”.
Output Schema	The fields to fill in. Each has a name, a type and a description.

Field types: String (text), Int (whole number), Float (decimal), Boolean (yes or no), List, or Enum (one of a fixed set of values).

What comes out

A set of named values matching your fields. When sent to a Webhook it arrives under the name you gave the node:

{
  "customerFeedback": {
    "customerName": "Jane Smith",
    "issueType": "billing",
    "resolved": false
  }
}

Mark each call successful or not

Three field names have a meaning of their own. Give one of these fields to any Structured Output node and every session records how the call went, with no extra model call:

Field name	Type	What it records
`success`	Boolean	Whether the call did its job. Sessions shows Successful or Unsuccessful, and the Overview’s Success rate counts it.
`outcome`	Boolean, or Enum with `success` and `failure`	The same, when `success` is not there. Any other value, such as `callback_requested`, is the disposition.
`disposition`	String or Enum	A short label for how the call ended, such as `appointment_booked` or `voicemail`.

Names match in any case. Without a disposition field, the category a Categorize node chose during the call is the disposition. Describe each field for the model as you would any other, for example “true when the caller booked an appointment”. A session with none of these shows No outcome, and the success rate leaves it out instead of counting it as a failure. The outcome is also sent to a Webhook as callOutcome, returned with every session by the public API (GET /v1/sessions), and can trigger a Successful sessions alert. Playground sessions are written by your browser, which does not store the outcome yet, so they show No outcome. Calls to a published agent (phone, campaign, API and share link) record it.

Patterns

End ──▶ Structured Output ──▶ Webhook
End ──▶ Structured Output (email) ──▶ CRM (post-processing)
End ──▶ Structured Output (email) ──▶ Helpdesk

Use cases

Capture leads: name, email, interest level.
Classify support calls and record the details.
Score sentiment or call quality.
Feed the CRM sync and Helpdesk nodes with the caller’s email.

Getting started

Building your agent

Build with AI

Testing

Tools

After the call

Publishing

Self-hosting

Add it

Settings

What comes out

Mark each call successful or not

Patterns

Use cases

​Add it

​Settings

​What comes out

​Mark each call successful or not

​Patterns

​Use cases

Add it

Settings

What comes out

Mark each call successful or not

Patterns

Use cases