Workflow Lead Variables And Call Attributes In DialNexa

Understand DialNexa workflow lead variables, call attributes, uploaded values, variable keys, application templates, and condition routing.

Workflow lead variables and call attributes carry data through a DialNexa workflow. Lead variables usually come from uploaded or created lead data. Call attributes come from call results, metadata, or extracted fields. Together they power conditions, templates, and debugging.

Variables are the workflow memory. If memory is empty, conditions and templates will improvise badly.

Lead Data Types

Use the right data source for the right job.

Data	Source	Used by
Phone number	Lead creation or CSV upload.	Voice Call nodes.
Dynamic variables	Uploaded lead columns or API-created lead values.	Prompts, templates, and conditions.
Call attributes	Call result data and post-call analysis.	Condition nodes and reporting.
Notes	Lead context where available.	Review and operations.
Current node id	Execution state.	Lead history and debugging.

Where Variables Appear

Workflow variables show up across builder and execution.

Condition nodes

Branch on variables or call attributes.

Application nodes

Insert values into WATI templates or email fields.

Lead history

Show which data was available when the lead moved.

Call logs

Call attributes can be traced back to exact call records.

Variable Hygiene Questions

Are variable names stable?

Changing a column name can break templates and conditions.

Are values present for every lead?

Use defaults or validation before activation.

Are call attributes created before they are used?

A condition cannot branch on an outcome that has not happened yet.

Are sensitive values necessary?

Avoid carrying sensitive data through workflow variables unless required.

Related Reading

Condition Nodes

Route with data.

Application Nodes

Use data in actions.

Call Data Model

Understand call fields.