> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa Dynamic Variables

> Understand DialNexa dynamic variables across prompts, welcome messages, batch CSVs, workflow leads, API calls, transfer destinations, and call metadata.

DialNexa dynamic variables are call-time values used to personalize or control agent behavior. They appear as placeholders such as `{{first_name}}` and can be supplied by batch CSV rows, workflow leads, API calls, test calls, or defaults saved on the agent version.

<Note>
  For the syntax, value priority order, and how to pass values from each launch surface, see [Dynamic Variables](/agents/dynamic-variables) - that page is the how-to. This page covers how variable data flows through calls and where it goes wrong.
</Note>

<Warning>
  Dynamic values should be true, current, and safe to speak. The agent may say them out loud.
</Warning>

## Dynamic Variable Sources

Call-time data can arrive from several places.

| Source                  | Example                                                 |
| ----------------------- | ------------------------------------------------------- |
| Prompt placeholder      | `{{first_name}}` in the instruction.                    |
| Welcome message         | A personalized first sentence.                          |
| Batch CSV               | Columns for name, due date, city, or amount.            |
| Workflow lead variables | Lead-specific values used in nodes and templates.       |
| API request             | Metadata or variables supplied by an external launcher. |
| Default variables       | Fallback values when a source is missing.               |

## Design Variables Cleanly

<Steps>
  <Step title="Use stable names">
    Prefer `first_name` over `name1` or `customerNameMaybe`.
  </Step>

  <Step title="Document required values">
    Know which variables every launch path must provide.
  </Step>

  <Step title="Add safe defaults">
    Protect calls from incomplete data.
  </Step>

  <Step title="Test missing data">
    Place calls with missing values and listen to the result.
  </Step>
</Steps>

## Dynamic Variable Problems

<AccordionGroup>
  <Accordion title="Variable is spoken with braces">
    The value was not supplied and no safe default existed.
  </Accordion>

  <Accordion title="CSV value goes to wrong field">
    Header does not match the expected variable key.
  </Accordion>

  <Accordion title="Workflow action missing a parameter">
    Lead variable key was absent or misspelled.
  </Accordion>

  <Accordion title="Transfer fails">
    Destination variable was empty or incorrectly formatted.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Agent Dynamic Variables" icon="sparkles" href="/agents/dynamic-variables">
    Use variables in agents.
  </Card>

  <Card title="Default Variables" icon="database" href="/data/default-variables">
    Set fallbacks.
  </Card>

  <Card title="Workflow Variables" icon="workflow" href="/workflows/lead-variables-and-call-attributes">
    Use variables in automation.
  </Card>
</CardGroup>