I am using the web snippet and i can send the following payload in the body when i connect to my assistant : Body { "assistant_id": "2ab83bb5-88a6-447c-a133-399a0292df6b", "assistant_overrides": { "metadata": { "jira_host": "hidden for this support request", "jira_email": "hidden for this support request", "jira_project_key": "****", "environment": "development" } } } ###how to make sure that when i call a function, the following fields are automatically field in. they are part of the function property: "jira_host" and "jira_email" and "jira_project_key" ? In other words, how to automatically map metadata fields to function parameters so that i don't have to ask the user to voice over complex information to connect to their systems ? @Sahil

@GetInference To ensure that the fields "jira_host," "jira_email," and "jira_project_key" are automatically filled in when calling a function, you can implement a mechanism within your Voice API (VAPI) that maps the metadata provided in the

assistant_overrides

to the function parameters. Here's a general approach you can take: 1. **Extract Metadata**: When the payload is received, extract the

metadata

object from the

assistant_overrides

. 2. **Map to Function Parameters**: Before calling the function, map the extracted metadata values to the corresponding function parameters. This mapping should be done programmatically within your VAPI system. 3. **Call the Function**: With the parameters now containing the necessary metadata, call the function using these parameters. For example, if you have a function that requires

jira_host

,

jira_email

, and

jira_project_key

as parameters, your VAPI system should automatically take the values from the metadata and pass them to the function call like this:

javascript
function callFunctionWithMetadata(metadata) {
  const functionParameters = {
    jira_host: metadata.jira_host,
    jira_email: metadata.jira_email,
    jira_project_key: metadata.jira_project_key,
    // ... other parameters if needed
  };

  // Assuming 'functionToCall' is the function that needs these parameters
  functionToCall(functionParameters);
}

This way, the user does not need to voice over complex information each time they want to connect to their systems. The VAPI system handles the mapping automatically based on the initial payload provided. If you have a specific function in mind that you need to call with these parameters, please provide the function name and any additional context so I can assist you further. If this is a general inquiry, the approach above should guide you in the right direction.

@GetInference Metadata is not used directly within your assistant. Instead, you need to use dynamic variables and include them in your assistant's prompt. Then, using prompting, you must explicitly pass these variables to your tool calls. This is how you will end up using them. Let me know if you need further help.

thank you @Shubham Bajaj

@Shubham Bajaj @User @Vapi @Vapi Support Bot I am using POST to initiate a outbound call. It is triggering the correct assistant which is calling the correct number. Now I want to know how I can access the params from metadata in the prompts without using Workflow? https://cdn.discordapp.com/attachments/1330616857522212978/1371081643519119370/image.png?ex=6821d6c9&is=68208549&hm=0cdb7a734ecfb4bf48e3b33b24c766155c67f2280d47e79e73b80fa1ec27741a&

To access parameters from metadata in your prompts without using Workflow, you should use dynamic variables in your assistant's prompt template. When you initiate the outbound call and include metadata (like email and name), make sure your prompt references these variables. Then, when constructing the prompt, map the values from the metadata to the corresponding dynamic variables. This way, the assistant can use the metadata fields directly in the conversation or tool calls, even without Workflow. If you need to pass these values to a function or tool, include the dynamic variables in your prompt so they are available when needed.

@Vapi Support Bot I have tried using {{name}}, {{metadata.name}} in the prompts - but no luck. how to use dynamic variable for this? where do I ensure that params are getting populated from the metadata when the assistant is triggered

It sounds like you're working to ensure that metadata fields such as jira_host, jira_email, and jira_project_key are automatically mapped to function parameters in your assistant, and that these values are accessible in prompts using dynamic variables like {{name}} or {{metadata.name}}. From the information provided, the recommended approach is to extract and map metadata programmatically or to pass these values as dynamic variables in your prompt templates, so they can be populated when the assistant is triggered. If you're experiencing issues with dynamic variables not being populated, it may be related to how the metadata is being passed or accessed at runtime. Ensuring that the metadata is correctly set and available to the assistant when it is triggered is key to having these variables populate as expected. If you have control over the code or configuration that triggers the assistant, double-check that the metadata is included and structured as needed for the dynamic variables to resolve properly.

This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.