Voice Agent as a workflow node
You can invoke a voice agent from inside any Tool using the Voice Agent node — typically to trigger an outbound call as part of a larger workflow.
Adding the node
In the Tool builder, open the node picker and select Voice Agent. The node configuration form mirrors the outbound calling API:
- Phone number connection — selector for which telephony connection to use (same selector pattern used elsewhere on the platform).
- Voice Agent — dropdown to select a published voice agent from the workspace.
- Target user phone number — required field. The number to dial.
- Target user name — optional field. Available to the agent's prompt and shown in run history.
Node output
The node returns a single value:
- Conversation ID — a unique identifier for the call that was placed.
Chaining nodes
You can use the Conversation ID as input to a subsequent node to fetch:
- The call recording (audio).
- The conversation transcript (turn-by-turn text).
Both are stored on the voice agent's Run history entry for that Conversation ID and are accessible programmatically.
Typical patterns
- Follow-up call after a form submission. A Tool collects user details from a form, then uses the Voice Agent node to place an outbound call.
- Notification calls. A Tool monitors a data source and triggers a call when a condition is met (e.g., "your shipment is delayed").
- Multi-step voice flow. Place a call, wait for the conversation to complete, then fetch the transcript and run downstream logic (summarization, CRM update, classification).
Constraints
- The Voice Agent must be published to be selectable in the node.
- The phone number connection must be active.
- The Voice Agent node respects the same telephony provider limits as direct API outbound calling.
In the trace
When a Tool runs and uses the Voice Agent node, the node appears as a span in the Tool's trace. Note that the voice agent's own call has its own run record in voice run history — the Tool's trace shows the dispatch; the voice run shows the call itself.