# Incoming call

> What the Incoming call trigger does in a voice workflow, the output variables it provides, and how to debug it.

## What it does

Starts the deployed workflow when a call arrives on a phone number bound to this trigger. It is the entry point of an inbound voice workflow, and it hands the rest of the workflow the call it started for.

The number keeps ringing while the workflow job starts. The caller is not answered until the [Voice Agent](./node-voice-agent.md) node is ready, so a slow start sounds like a longer ring rather than dead air on pickup. That wait is capped at 12 seconds from the moment the call arrives:

* If the job does not start within it, the call is **rejected**.
* If the job starts but no agent attaches in time, UiPath **answers anyway**, and the caller hears silence until one does. A call that never attaches an agent ends after about 25 seconds.

The node is labeled **Incoming call** (Preview) in the **Change trigger** list. An inbound workflow runs **Incoming call** → **[Voice Agent](./node-voice-agent.md)** → **[End Call](./node-end-call.md)**. The trigger has no canvas properties.

:::note
Voice workflows need a phone number connected to your UiPath account. Without one, the **From** list of Create Outgoing Call is empty and the node shows an error, and no call can reach an Incoming Call trigger. Ask your administrator to connect a number, as [Administration](administration.md#phone-numbers-for-voice-workflows) describes.
:::

## Output variables

| Path | Type | Description |
|---|---|---|
| `output.callContext.type` | string | Call medium: `phone` or `web`. Only `phone` is supported today. |
| `output.callContext.id` | string | The provider-side call identifier. |
| `output.callContext.conversationId` | string | The universally unique identifier (UUID) of the conversation associated with this call. |
| `output.callContext.from` | string | The number the call came from, that is, the caller. Can be `null`. |
| `output.callContext.to` | string | The number that was called, that is, your connected number. Can be `null`. |

Bind `$vars.<triggerNode>.output.callContext` to the **Call context** field on the [Voice Agent](./node-voice-agent.md) and [End Call](./node-end-call.md) nodes. For example, use `$vars.incomingCall1.output.callContext`.

## Debug

To test your workflow, deploy it, bind a number to it on the workflow, then dial in. [Deployment](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-voice-deployment) describes how to bind a number. Today, you cannot debug an incoming call trigger from the canvas.

## Next steps
- [Voice](./conversational-voice.md): all the voice nodes.
- [Create Outgoing Call](./node-create-outgoing-call.md): outbound counterpart.
- [Voice Agent](./node-voice-agent.md): the agent that handles the call.
- [End Call](./node-end-call.md): ends the call.
- [Deployment](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/conversational-agents-voice-deployment): connecting a number and binding it to this trigger.
- [Community](community.md): ask questions and share workflows with other builders on the UiPath Forum.