- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Trigger that starts a published Flow when a connected phone number receives an inbound call.
What it does
Starts the Flow when a call arrives on a phone number bound to this trigger. It is the entry point of an inbound voice Flow, and it hands the rest of the Flow the call it started for.
The number keeps ringing while Flow job starts. The caller is not answered until the Voice Agent 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 in the Trigger category of the node palette. An inbound Flow runs Incoming call → Voice Agent → End Call. The trigger has no canvas properties.
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 UUID of the conversation associated with this call. |
Bind $vars.<triggerNode>.output.callContext to the Call context field on the Voice Agent and End Call nodes. For example, use $vars.incomingCall1.output.callContext.
Debug
To test your Flow, publish the Flow, bind a number to it on the Flow, then dial in. See Deployment. Today, you cannot debug an incoming call trigger from the canvas.
Related pages
- Voice
- Create Outgoing Call — outbound counterpart.
- Voice Agent
- End Call
- Deployment — connecting a number and binding it to this trigger.