Skip to main content
DialNexa workflow builder concepts describe how visual automation becomes executable data. Nodes store type, label, position, and config. Edges connect nodes. Leads carry phone numbers, variables, and call attributes. Executions and history show what actually happened. DialNexa workflow builder canvas showing Voice Call, Time, Conditional, Converted, and Dropped nodes with labeled edges.
The canvas is the drawing. The config is the contract. Review both.

DialNexa Workflow Builder Concepts And Data Model

These fields explain what the builder stores.

Outputs Are The Important Part

Outputs decide where a lead moves next.

Voice Call outputs

COMPLETED, FAILED, and DNP route different call outcomes.

Condition outputs

true and false route evaluated conditions.

Time output

A wait node has one next path after the hold expires.

Application outputs

success and failure route integration action results.

Custom Function outputs

Success and Failure route public HTTP request results.

Review A Builder Graph

1

Scan terminal states

Every path should be able to end in converted, dropped, or another intentional final path.
2

Check node configs

Open each node and read settings, not just labels.
3

Check edges by label

A completed call should not route to the failed path by accident.
4

Validate before activation

Use workflow validation and small lead samples before activating.

Review Workflow Readiness And Unsaved Changes

The workflow view can show an issues to resolve count before activation. Select it to open the editor and focus affected nodes when the validation result identifies them. Correct the issues, save the graph, and review validation again before activating. A missing count is not proof that every downstream integration will succeed. While editing, Unsaved changes indicates changes to the graph or its configuration. Leaving edit mode can ask you to Discard unsaved changes. Save first if you want to keep the edits; navigation and zoom alone do not change the workflow. Use Find node to search node labels and center the matching node. Go to start returns to the entry point, Fit all shows the whole graph, and 100% returns to actual-size zoom. These controls change the view, not the graph or its saved configuration. If a large graph opens focused on its start instead of showing every node, use Fit all for an overview and Find node to inspect the branch you need. Check the connections at a readable zoom before saving or publishing changes.

Call Nodes

Configure call outputs.

Condition Nodes

Configure branch logic.

Application Nodes

Run connected actions.