Skip to main content

​
Overview

Flow Builder has two nodes for working with data: the Extraction node uses an LLM to pull structured information from the conversation, and the Variable node sets values directly without AI involvement.

​
Extraction Node

The Extraction node analyzes conversation history and extracts specific data into named variables.

​
Configuring Extractions

Each extraction has three fields:
FieldDescriptionExample
varNameVariable to store the valuecaller_email
varTypeExpected data typestring
descriptionWhat to extract (natural language)“The caller’s email address”

​
Supported Types

TypeExample Values
stringjohn@example.com
number42
booleantrue
array["Mon", "Wed", "Fri"]
object{"city": "Austin", "state": "TX"}

​
Sentinel Sanitization

The extraction engine automatically converts ambiguous values (<UNKNOWN>, N/A, null, none, not provided) to empty strings. This ensures is_empty checks in Logic nodes work correctly.
Connect Extraction nodes via the async handle when you don’t need the extracted data immediately — this keeps the conversation flowing while extraction runs in the background.

​
Variable Node

The Variable node sets values directly — no LLM call, instant execution.

​
Literal Values

varName: lead_status
value: qualified

​
Dynamic Values with Substitution

varName: full_address
value: {{street}}, {{city}}, {{state}} {{zip}}

​
Common Pattern

Chain these nodes together:
  1. Conversation node — Ask the user for information
  2. Extraction node — Extract first_name, last_name, email
  3. Variable node — Compose full_name as {{first_name}} {{last_name}}
  4. Logic node — Check if required fields are present
  5. Request node — POST to your CRM

Variables

Variable system and substitution syntax

Logic Node

Branch based on extracted values

Request Node

Send extracted data to APIs

Data Extraction Guide

How-to guide for data extraction