Home šŸ” Flows Building šŸ§  Flow Node Functions Explained

šŸ§  Flow Node Functions Explained

Last updated on Feb 05, 2026

Article content

Flows in Flows Building are built by connecting nodes together.
Each node has a specific function and controls how calls and events are handled.

This article explains every node type available in Flows Building, exactly as they appear in the flow editor.

Trigger Nodes

Incoming Call

What it does
Starts the flow when an inbound call is received.

When to use it

  • Call routing

  • IVR menus

  • Time-based or geographic call handling

Important notes

  • The flow will only trigger for calls received after the flow is published

  • Each flow must have at least one trigger

Condition Nodes

Condition nodes evaluate logic and decide which path the flow should follow.

Contact Data Is

What it does
Checks whether specific contact data exists or matches a value.

Common uses

  • Known vs unknown callers

  • Tagged or categorised contacts

Things to watch

  • Contact data may not always exist

  • Always handle false outcomes

Time Is

What it does
Checks the current time against defined hours.

Common uses

  • Business hours vs after-hours routing

  • Lunch breaks or shift changes

Things to watch

  • Time is evaluated at the moment the flow runs

Date-Time Is

What it does
Checks a specific date and time.

Common uses

  • Public holidays

  • One-off events

  • Temporary routing changes

Things to watch

  • Date-time rules override normal time logic

Day Is

What it does
Checks the day of the week.

Common uses

  • Weekday vs weekend handling

  • Different routing by day

Callerā€™s Number Is

What it does
Matches the callerā€™s phone number.

Common uses

  • Blocking specific numbers

  • VIP routing

  • Known caller handling

Things to watch

  • Number formats must match correctly

Callerā€™s Postcode Is

What it does
Checks the callerā€™s postcode based on their number.

Common uses

  • Local call routing

  • Regional service handling

Things to watch

  • Postcode detection depends on number data availability

Callerā€™s State Is

What it does
Checks the callerā€™s state.

Common uses

  • State-based routing

  • Public holiday handling by state

AB Split

What it does
Randomly splits calls into two or more paths.

Common uses

  • Load sharing

  • Testing different call flows

  • Comparing outcomes

Things to watch

  • Use only when random distribution is acceptable

Action Nodes

Action nodes define what happens once a flow is running.

Forward Call

What it does
Forwards the call to another number or destination.

Common uses

  • Route calls to staff or teams

  • Overflow handling

Pause

What it does
Adds a short delay before the next action.

Common uses

  • Natural spacing between announcements

  • Timing control

Say / Play

What it does
Plays a recorded message or text-to-speech audio.

Common uses

  • Greetings

  • Announcements

  • IVR prompts

Record Voicemail

What it does
Records a voicemail from the caller.

Common uses

  • After-hours handling

  • Missed calls

Gather Input

What it does
Collects keypad input from the caller.

Common uses

  • IVR menus

  • Option selection

Things to watch

  • Always handle invalid or no input

Reject Call

What it does
Ends the call without forwarding.

Common uses

  • Blocking unwanted calls

  • Out-of-scope routing

Send Analytics Event

What it does
Sends an analytics event for tracking and reporting.

Common uses

  • Measuring call flow performance

  • Tracking IVR selections

Send Email

What it does
Sends an email notification.

Common uses

  • Alerting staff

  • Voicemail notifications

Send SMS Message

What it does
Sends an SMS message.

Common uses

  • Caller follow-ups

  • Notifications or confirmations

How Nodes Work Together

A typical flow works like this:

  1. Incoming Call trigger starts the flow

  2. Condition nodes decide how the call should be handled

  3. Action nodes perform routing, messaging or recording

Correct order and configuration are essential for predictable behaviour.

Common Node Mistakes

  • Forgetting to publish the flow

  • Placing conditions after actions

  • Not handling false condition paths

  • Missing required fields in actions

Review node order carefully when troubleshooting.

Related Articles

  • Understanding Flow Nodes: Triggers, Conditions, Actions & Variables

  • Flow Examples & Common Patterns

  • Common mistakes when building flows

  • Troubleshooting Flows That Are Not Triggering

  • Using Flow Logs for Troubleshooting