Dynamic variables

Documentation Index

Fetch the complete documentation index at: https://docs.sigmamind.ai/llms.txt

Use this file to discover all available pages before exploring further.

{{ variable_name }}

Hello {{ customer_name }}, thanks for reaching out!

​

Where Dynamic Variables Are Supported

​

Dynamic variables can be used in any nodes inside SigmaMind:

• Agent Responses – Personalize replies with customer details.
• Email Templates – Insert variables like {{ customer_email }} or {{ order_id }}.
• Campaigns – Pass variables from campaign uploads or APIs to customize conversations.
• Webhooks and Integrations – Include context-specific variables in outbound data.

​

Sources of Dynamic Variables

​

Dynamic variables can come from multiple sources:

​

1. Create Call API

{
    "fromPhoneNumber": 14155552671,
    "toPhoneNumber": 14155552671,
    "agentId": "D5D0p7TUs66TTAEAx",
    "variables": {
        "customer_name": "Michael"
    }
}

​

2. Campaign Uploads

curl --request POST \
  --url https://api.sigmamind.ai/v1/campaigns \
  --header 'Content-Type: multipart/form-data' \
  --header 'X-API-Key: <api-key>' \
  --form 'campaignName=<string>' \
  --form sipPhoneNumber=14155552671 \
  --form agentId=D5D0p7TUs66TTAEAx \
  --form isScheduled=true \
  --form scheduledDate=2023-11-07T05:31:56Z \
  --form scheduledTime=12:00:00 \
  --form scheduledTimezone=America/Los_Angeles \
  --form concurrentCalls=5 \
  --form 'variables={
  "customer_name": "Michael"
}' \
  --form file=@example-file

Phone Number,Customer Name,Order ID
+14155552671,Michael,12345
+14155552672,Sarah,67890

​

3. Inbound Webhooks (Receive Calls)

​

Request Payload

{
  "event": "inbound_call",
  "agent_id": "shvb5xs5fo2D2222",
  "from_number": "+12345678912",
  "to_number": "+12345678913"
}

​

Response

• dynamic_variables: use this to define dynamic variables specific to this inbound call.
• override_agent_id: if you want to override the agent id, you can set it here.

{
"dynamic_variables": {
        "first_name": "Jim",
		"last_name": "Smith"
    },
"override_agent_id":"shvb5xs5fo2D2225"
}

​

End-to-end flow

1.     Customer dials your SigmaMind number.
2.     SigmaMind sends the inbound_call payload to your webhook URL.
3.     Your system performs a CRM or database lookup using from_number.
4.     Your system returns dynamic_variables
5.     SigmaMind connects the agent with all returned variables pre-loaded.
6.     The agent begins the conversation with full customer context already available.

​

Use when:

• Handling inbound calls
• Fetching real-time customer data
• Routing calls dynamically

​

4. Custom Headers

• Not visible to the customer
• Available to backend systems, CRMs, and receiving agents

​

5. Conversation Extracted Variables

• If the agent asks for the customer’s email, it can be extracted and stored as {{ customer_email }}.
• If the agent identifies an order number, it can be stored as {{ order_id }}.

​

Example Usage

• In an Agent Response

Hi {{ customer_name }}, your order {{ order_id }} is confirmed and will be delivered by {{ delivery_date }}.

• In an Email Template

Subject: Order Confirmation for {{ customer_name }}

Dear {{ customer_name }},

Thank you for your purchase! Your order ID is {{ order_id }}.
We will notify you at {{ customerEmail }} once your order ships.

Best regards,  
Team SigmaMind

Hi {{ customer_name }}

• API
• Campaign (CSV)
• Webhook
• Custom Headers
• Conversation

• Agent responses
• Tool execution
• Workflow logic

• Conversation logs
• Node logs
• System logs
• Post-conversation analysis
• Webhook outputs

​

View Dynamic Variables at Runtime (Dashboard)

​

Steps

1. Go to Conversations from the left sidebar
2. Click on any call or chat
3. Open the Dynamic Variables tab

​

What You’ll See

• All variables available during that conversation
• Runtime values (from API, webhook, headers, or extraction)

customer_name → Michael  
order_id → 12345  
last_order_date → 2026-04-20  

​

Why This Is Important

• Debug missing or incorrect variables\
• Verify data passed from API / webhook / CSV\
• Understand how variables change during runtime\

• Transcript → See where variables are used in conversation\
• Node Logs → Debug step-by-step execution\
• System Logs → Check backend events\
• Analysis → View post-conversation insights

​

Best Practices

• Always provide default values to handle missing or undefined variables.
• Keep variable names simple, consistent, and descriptive (e.g., customer_name, order_id).
• Validate and sanitize inputs from external sources such as API, CSV uploads, webhooks, and headers.
• Use the right source for the right use case (API for real-time data, CSV for campaigns, webhook for inbound calls, headers for metadata).
• Prefer conversation-extracted variables to reduce manual data collection during interactions.
• Avoid overloading variables with complex or nested data—keep values clean and usable.
• Test variable population during simulation to ensure values are correctly passed at runtime.

​

Summary:

• Dynamic Variables use the {{ variable_name }} format and allow you to inject real-time data into your agent.
• They are populated at runtime from sources like API calls, CSV campaigns, inbound webhooks, custom headers, and conversation inputs.
• They can be used across all agent nodes to enable personalized, context-aware, and fully automated interactions.