> ## 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 Workflow Call Nodes

> Configure DialNexa workflow Voice Call nodes with phone numbers, outbound agent assignment, completed failed and did-not-pick outputs, and call log evidence.

A DialNexa workflow Voice Call node places an outbound call to a workflow lead through a configured phone number. The phone number must be active and must have an outbound agent id and version number assigned, or the workflow cannot create the call correctly.

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/workflow-voice-call-node-leads.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=2c4d698b855ecb056134c09ff32fcad4" alt="DialNexa workflow map with a Voice Call node selected and the lead history panel showing completed call evidence." style={{ width: '100%', maxWidth: '1100px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="3420" height="1850" data-path="images/documentation/screenshots/workflow-voice-call-node-leads.png" />

<Warning>
  A Voice Call node must use an active phone number with an outbound agent assignment. Without that route, the workflow cannot place the call correctly.
</Warning>

## Voice Call Node Config

These fields decide how the call runs and where the lead goes afterward. `phone_number_id` is the stored form of the **Phone number** dropdown in the builder; the outputs are the edges you connect on the canvas.

| Field             | Purpose                                                                                            |
| ----------------- | -------------------------------------------------------------------------------------------------- |
| phone\_number\_id | The active organization phone number used to place the call (the builder's Phone number dropdown). |
| COMPLETED output  | Next node when the call completes successfully.                                                    |
| FAILED output     | Next node when the call fails.                                                                     |
| DNP output        | Next node when the recipient did not pick up.                                                      |
| Call log id       | Stored in history metadata so the lead path can link to the exact call.                            |

## Voice Call Status Routing

The Voice Call node waits for the linked call log to reach a final status before routing the lead.

| Call status                                                | Output followed | Meaning                                                                                                                                     |
| ---------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| `created`, `initiated`, `received`, `connected`, `waiting` | No output yet   | The call is still in progress or waiting for a final update.                                                                                |
| `completed`                                                | `COMPLETED`     | The call connected and ended.                                                                                                               |
| `did_not_pick`, `busy`                                     | `DNP`           | The recipient did not complete a live conversation.                                                                                         |
| `failed`, `no_answer`                                      | `FAILED`        | The call failed or the provider returned no answer.                                                                                         |
| `cancelled`, `retry_expired`                               | Review required | These are final call statuses, but they are not default Voice Call node outputs. Inspect lead history if the lead remains at the call node. |

## Prepare A Call Node

<Steps>
  <Step title="Choose an active number">
    The phone number must exist, be active, and not deleted.
  </Step>

  <Step title="Confirm outbound assignment">
    The number needs outbound agent id and outbound version number.
  </Step>

  <Step title="Wire all relevant outputs">
    Route completed, failed, and did-not-pick outcomes intentionally.
  </Step>

  <Step title="Test with one lead">
    Open lead history and the linked call detail after execution.
  </Step>
</Steps>

## Call Node Failure Reasons

<AccordionGroup>
  <Accordion title="Phone number not active">
    Use an active number in the selected workspace.
  </Accordion>

  <Accordion title="No outbound agent configured">
    Configure a valid outbound agent version for the selected phone number before activating the workflow.
  </Accordion>

  <Accordion title="Output missing">
    If the node has no configured output for a final call status, the lead can get stuck.
  </Accordion>

  <Accordion title="Call already active">
    Workflow execution avoids restarting a pending or active call for the same lead-node combination.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Phone Numbers" icon="phone" href="/calls/phone-numbers">
    Review active numbers and outbound routing context.
  </Card>

  <Card title="Lead History" icon="route" href="/workflows/lead-history-and-debugging">
    Open the linked call.
  </Card>

  <Card title="Statuses" icon="list" href="/reference/statuses">
    Understand call outcomes.
  </Card>
</CardGroup>