[IMAGE: Node palette showing all six node types with icons]
Node Types at a Glance
| Node | Icon | Purpose | When to Use |
|---|---|---|---|
| Default | π· | Conversation step | Each conversation point |
| Transfer Call | π | Handoff to human | Connect to live agent |
| API Call | β¬οΈ | External data | Fetch/send mid-conversation |
| End Call | βοΈ | Terminate call | Natural endings |
| Pre-Call API | π΅π | Load context | Get data before call starts |
| Post-Call API | π π΅ | Save data | Send data after call ends |
Default Node
The workhorse of your flow. Each Default node represents one step in the conversation.[IMAGE: Default node card showing title and connection points]
Configuration
[IMAGE: Panel showing all Default node settings]
| Field | Purpose |
|---|---|
| Name | Identifier shown on canvas |
| Prompt | What the agent says at this step |
| Branches | Output paths based on caller response |
Example Prompts
- Greeting
- Question
- Confirmation
Branching
Default nodes can have multiple output branches:[IMAGE: Node showing three output connections with condition labels]
Transfer Call Node
Hands the conversation to a human agent via phone transfer.[IMAGE: Transfer Call node card with phone icon]
Configuration
[IMAGE: Transfer settings panel showing all options]
| Field | Purpose |
|---|---|
| Name | Identifier |
| Description | When this transfer should trigger |
| Phone Number | Transfer destination (with country code) |
| Transfer Type | Cold or Warm |
Transfer Types
- Cold Transfer
- Warm Transfer
[IMAGE: Diagram showing immediate handoff]
- Simple escalations
- When context isnβt needed
- Time-sensitive transfers
API Call Node
Makes external API requests during the conversation.[IMAGE: API Call node card with arrow icon]
Configuration
[IMAGE: API settings panel with all fields]
| Field | Purpose |
|---|---|
| Name | Identifier |
| URL | Endpoint to call |
| Method | GET, POST, PUT, DELETE |
| Headers | Request headers |
| Body | Request payload |
| Response Mapping | Map response to variables |
Example: Customer Lookup
[IMAGE: API node configured for customer lookup]
End Call Node
Terminates the conversation.[IMAGE: End Call node card with scissors icon]
Configuration
[IMAGE: End Call settings panel]
| Field | Purpose |
|---|---|
| Name | Identifier |
| Closing Message | Final words before hanging up |
Example Closings
- Successful
- Transferred
- Not Qualified
Pre-Call API Node
Fetches data before the conversation begins.[IMAGE: Pre-Call API node with distinctive coloring]
When It Runs
[IMAGE: Timeline showing API call happening before Start node]
- Phone rings
- Pre-Call API executes β Here
- Data available
- Conversation starts
Use Cases
| Scenario | API Call |
|---|---|
| CRM Lookup | Get caller history before greeting |
| Account Status | Check if caller has issues |
| Personalization | Load name, preferences |
| Routing | Determine which flow to use |
Example
[IMAGE: Pre-Call API configured for customer lookup]
Post-Call API Node
Sends data after the conversation ends.[IMAGE: Post-Call API node with distinctive coloring]
When It Runs
[IMAGE: Timeline showing API call happening after End Call]
- Conversation ends
- Call terminates
- Post-Call API executes β Here
- Data saved externally
Use Cases
| Scenario | What to Send |
|---|---|
| CRM Update | Call summary, outcome |
| Ticket Creation | Issue details, priority |
| Lead Capture | Collected qualification data |
| Analytics | Custom metrics, disposition |
Example
[IMAGE: Post-Call API configured to update CRM]
Choosing the Right Node
[IMAGE: Flowchart: βWhat do you need?β β branches to different nodes]
| If you need to⦠| Use |
|---|---|
| Ask a question or give info | Default Node |
| Transfer to a human | Transfer Call Node |
| Get external data mid-conversation | API Call Node |
| End the conversation | End Call Node |
| Load data before call starts | Pre-Call API Node |
| Save data after call ends | Post-Call API Node |

