maestro
latest
false
Maestro user guide
- 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
Node that places an outbound call from a connected phone number and waits for it to be answered.
What it does
Dials an outbound phone call and waits until the call is answered by a human or voicemail. Debug runs place real calls, billed by your provider like any other.
The node is labeled Create outgoing call in the Tool > Voice tools category of the node palette. An outbound Flow runs Create outgoing call → Voice Agent → End Call.
Configuration reference
| Field | Required | Default | Description |
|---|---|---|---|
| From | Yes | None | The originating number. The picker lists connected numbers with a direction of Outgoing or Both. See Deployment on how to configure a phone number. |
| To | Yes | None | The destination number, in E.164 format — for example, +12025551234. The field opens in fixed-value mode; switch it to expression mode to bind a variable. |
If either field is empty, the run fails with From number is required or Destination phone number is required.
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. |
error | object | Populated on failure. Refer to Error handling. |
Bind $vars.<node>.output.callContext to the Call context field on the Voice Agent and End Call nodes. For example, use $vars.createOutgoingCall1.output.callContext.
Related pages
- Voice
- Incoming Call — inbound counterpart.
- Voice Agent
- End Call
- Deployment — connecting an outbound number.