Issue: Dynamic variables defined using the format {{variable}} in the model → message → content structure are not being identified or treated as variables when retrieving assistant details through VAPI. This results in these placeholders not being dynamically processed or replaced. Question: Is there a way to define dynamic variables within the model → message → content structure such that they are recognized by VAPI and can be dynamically processed? Example: In the following content: { "model": "gpt-4o-mini", "messages": [ { "role": "system", "content": "If {{experience}} is greater than 5, suggest top travel destinations in Bali." } ] } The {{experience}} variable is not identified as a dynamic variable, and hence its value cannot be retrieved or replaced when fetching assistant details. Desired Outcome: We want {{experience}} and similar variables to be dynamically recognized and resolved, allowing for flexibility in tailoring responses. Solutions or Suggestions?: Is there a specific syntax or annotation that VAPI recognizes for dynamic variables? Should these variables be pre-defined or declared in a separate structure? Are there updates or workarounds in VAPI to support such use cases? Any guidance on how to handle dynamic variables effectively within this structure would be greatly appreciated!

@mauryasumit To ensure that dynamic variables like

{{experience}}

are recognized and processed by VAPI, you should follow the syntax and guidelines provided by VAPI for defining dynamic variables. Here are some steps you can take to address the issue: 1. **Check Documentation**: Review the VAPI documentation on dynamic variables to understand the correct syntax and usage. There might be specific guidelines on how to declare and use dynamic variables within the

model → message → content

structure. 2. **Correct Syntax**: Ensure that you are using the correct syntax for dynamic variables as per VAPI standards. If the documentation provides a different way to denote variables, update your content structure accordingly. 3. **Variable Declaration**: Verify if dynamic variables need to be pre-declared or defined in a separate structure within your VAPI configuration. Some systems require an explicit declaration of variables and their types before they can be used. 4. **Updates and Workarounds**: Check if there have been any recent updates to VAPI that introduce new features or workarounds for handling dynamic variables. The support or changelog sections of the VAPI documentation might provide this information. 5. **Support Inquiry**: If the documentation does not clearly address your issue, or if you have followed all guidelines and the problem persists, reach out to VAPI support for further assistance. If you need help locating the correct documentation or have any other questions, please let me know, and I'll do my best to assist you!

I am not sure why everyone has a hard time with this. Did you map the variable?

@mauryasumit You need to fill out the values for dynamic variables using assistant overrides either right before making the call or while creating the call. From your description, it seems you may have misunderstood how this works these values don't get auto-filled or replaced automatically from somewhere else. You have to explicitly pass the values using assistant overrides.

example

json
{
  "name": "using-dynamic-variables",
  "assistantId": "insert-your-assistant-id-here",
  "assistantOverrides": {
    "variableValues": {
      "insertVariableNameHere": "insertVariableValueHere",
      "dynamicVariableKey": "dynamicVariableValue"
    }
  }
}