Skip to main content

​
SubVerse Agents

The SubVerse Agents node executes a SubVerse AI agent on a specific communication channel — voice, WhatsApp, email, or chat. It initiates an agent conversation and can optionally wait for the conversation to complete before passing results downstream. SubVerse Agents Node

​
Use Cases

  • Initiate an outbound voice call handled by a SubVerse AI agent
  • Send a WhatsApp message and have an AI agent conduct the conversation
  • Launch an AI agent over email to gather information from a contact
  • Embed an AI chat session in an orchestration and use the outcome downstream

​
Node Reference

​
Parameters

ParameterTypeRequiredDescription
Agent ChannelSelectYesThe communication channel: Voice, WhatsApp, Email, or Chat
AgentSelectYesThe SubVerse AI agent to execute (select from list)
Agent VersionStringNoThe agent version to use: default, draft, or a specific version (e.g. v1)
Wait for CompletionBooleanNoIf enabled, the orchestration pauses until the agent conversation finishes
Customer MetadataKey-ValueNoCustom key-value pairs passed to the agent. Reference them in agent prompts using {{key}} syntax.

​
Channel-Specific Parameters

​
Voice

ParameterTypeRequiredDescription
Customer Phone NumberStringYesThe phone number to call (E.164 format, e.g. +912298765432)
Bot Phone NumberSelectNoThe SubVerse AI outbound caller number — leave empty to use the default

​
WhatsApp

ParameterTypeRequiredDescription
Customer Phone NumberStringYesThe WhatsApp number to message (E.164 format)
Bot Phone NumberSelectNoThe SubVerse AI WhatsApp sender number — leave empty to use the default

​
Email

ParameterTypeRequiredDescription
Customer EmailStringYesThe recipient email address

​
Chat

ParameterTypeRequiredDescription
Session IDStringNoOptional session identifier for continuing an existing chat
Initial MessageStringNoThe first message to send to the agent

​
Customer Metadata

Provide custom key-value pairs that the agent can reference during the conversation using {{key}} in prompts:
Example KeyExample ValueDescription
customerNameJohn DoeCustomer’s full name
orderIdORD-12345Relevant order reference
languageenPreferred language for the conversation

​
Wait for Completion

When Wait for Completion is enabled:
  • The orchestration run pauses while the SubVerse AI agent handles the conversation.
  • Once the agent marks the conversation as complete, execution resumes.
  • The full conversation outcome (transcript, status, extracted data) is available downstream.
When disabled:
  • The node starts the agent conversation and immediately moves to the next node.
  • The conversation happens asynchronously — the SubVerse AI Trigger can be used to react to the completion in a separate orchestration when it finishes.

​
Output Data

When the agent conversation completes: 
{
  "conversationId": "conv_XXXXXXXXX",
  "channel": "voice",
  "status": "completed",
  "outcome": "resolved",
  "agentName": "Support Agent",
  "customerNumber": "+919876543210",
  "duration": 120,
  "transcript": [
    { "role": "agent", "text": "Hello! How can I assist you today?" },
    { "role": "user", "text": "I need to reschedule my appointment." },
    { "role": "agent", "text": "Sure, let me help with that." }
  ],
  "extractedData": {
    "intent": "reschedule_appointment",
    "preferredDate": "2025-03-15"
  },
  "startedAt": "2025-03-10T09:00:00.000Z",
  "endedAt": "2025-03-10T09:02:00.000Z"
}
Reference in downstream nodes: 
{{ subverseAgents.outcome }}
{{ subverseAgents.extractedData.intent }}
{{ subverseAgents.transcript }}
{{ subverseAgents.conversationId }}
  • SubVerse AI Trigger — React to a completed SubVerse AI call in a separate orchestration
  • Conditions — Branch based on the agent’s outcome or extracted intent