Diska
Flow Builder

Flow structure

Required nodes, subflows and connection rules for the Flow Builder.

The main flow always follows a required backbone. Subflows have a simpler entry structure.

Main flow

Main Flow → Before conversation → Greeting message → next step

These nodes are structural and cannot be deleted.

Subflows

A subflow starts with:

Subflow → Entry conditions

It can be triggered by another flow through the Trigger subflow node. Use subflows to reuse common logic: for example, identity validation or address collection.

Node connection rules

SourceCan connect to
maintrigger
triggergreeting_message, conversation, message, custom_action, during_call_sms, transfer, booking, placeholder
greeting_messageconversation, message, jump, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder (cannot connect to branch without a conversation before)
conversationbranch, message, jump, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder
messagegreeting_message, conversation, message, branch, jump, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder
branchconversation, message, jump, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder
jumpconversation, message, branch, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder
trigger_subflowconversation, message, branch, jump, custom_action, during_call_sms, transfer, booking, end, placeholder
custom_action, during_call_sms, transfer, bookinggreeting_message, conversation, message, branch, jump, trigger_subflow, custom_action, during_call_sms, transfer, booking, end, placeholder
endafter_conversation
after_conversation(no outputs)

Placeholders

The Next step node is a visual placeholder. Replace it with real nodes as you expand the flow.

Copyright © 2026