When I receive a webhook with type: assistant-request i am preparing my responce and sending it back to the workflowId (specific workflow).

{
  "workflowId": "this-is-my-workflow-id",
  "workflowOverrides": {
    "variableValues": {
      "first_name": "Peter"
    }
  }
}

at the workflow i add this varuable {{first_name}} at the prompt and at the first message of the conversation node, and when call (inbound) my phone number, the agent did not see the value of the variable. * The phone number is imported and it is not assigned to a specific workflow. According to the documentation: https://docs.vapi.ai/api-reference/webhooks/server-message#response.body.messageResponse.AssistantRequest.workflowOverrides.variableValues this is the right way to respond to the webhook in order to override the variables at the Workflow. Please for your help because I am stucked with this and can not continue. My workarround is to start with an api call first and get the data and then start the conversation but this is not ideal for me.

You can’t set workflowOverrides.variableValues during the assistant-request webhook instead, pass assistantOverrides.variableValues when initiating the call via the API or SDK, before the conversation starts..

you mean to respond to the agent-request webhook with

{
  "workflowId": "workflow-id-here",
  "assistantOverrides": {
    "variableValues": {
      "first_name": "Peter"
    }
  }
}

Yes

I test it and it does not work with passing assistantOverrides.variableValues and the conversation node does not see my variable value. Also there is no assistant at the workflow so it is confusing for me because I thought that each node is an assistant at Workflows. At the other hand the override is working because I had to pass the caller-number because initially it was removed by the override. The problem is that the conv. node does not say the variable (maybe it is not passed to it but I don't know how to debug it). I am attaching a screenshot of the workflow if it helps. https://cdn.discordapp.com/attachments/1389161117863120947/1389173359484342352/image.png?ex=6863a802&is=68625682&hm=057e03b8ffa5fe1be5bd0da11227228424acf7b71563559dc83bb5fc86a8b26d&

Peter, originally you were doing it correctly. Could you share the call ID so I could take a look at what went wrong?

I described it in great details. You can simply follow my steps to recreate it. You will not be able to see anything by call ID because simply the variables are not comming to the workflow. @Shubham Bajaj I am pushing hard to use VAPI but there are so much issues with that software that I am thinking in moving to other solution. It is really frustrated

Hey, let me check with our team and get back to you with an update.

Is there any updates here? I really need to test the workflows with dynamic variables

Hey Peter Iliev, Thanks for reaching out! We're currently swamped with a bunch of tickets and it's taking us longer than usual to get back to everyone. I know waiting isn't fun, but we want to make sure we give your issue the attention it deserves rather than rushing through it. We'll circle back with you soon to get this sorted out.