Is there a way to store temporary variables within the VAPI call session memory that the assistant can access during the call? Not when starting the call with override variables, but to update them during the call to change the context.

Vapi doesn’t support updating variableValues mid-call, but you can retain context using semantic caching or manage dynamic state externally via webhooks or APIs during the call..

@Kings_big💫 Does the new Vapi workflow not support "connection of workflow to assistant"?

The new Vapi workflow no longer connects directly to Assistants instead, workflows run independently and are triggered via phone numbers or event..

Yeah, I noticed that. I replaced my previous assistant id with my new workflow id, tried connecting on my website, but it doesn't.

Can you send me a loom video to understand more about it?

I screen recorded with loom, but the console didn't show in the video. https://www.loom.com/share/a5707214eafb46269b587fcbbb9917f3?sid=c8793320-a7ee-45df-93d2-30ae9e904429 workflow id: *18c16662-ac96-4c0f-9944-954205cc84f5 * @Sahil @Shubham Bajaj https://cdn.discordapp.com/attachments/1385998823603568820/1388144476576284832/image.png?ex=685fe9c9&is=685e9849&hm=26ca35f3a9874513abbc2a924e087c67e7bcfed20549e14ce0348fcb6dc09790&

I see, well what you can do is use live call control https://docs.vapi.ai/calls/call-features and through that you can inject the data.

I think the problem is that it works if I use my old assistant id. since when you've a new update, saying that we can use workflow id directly, that was when I created a new workflow and replaced it with the id and the error log says "Couldn't Get Assistant" while I'm using a workflow id, could've said "Couldn't Get Workflow" instead. @Sahil @Shubham Bajaj ???

Hey! When you create web calls using Web SDK, this time you have to pass workflow ID as the 4th parameter. The first parameter is reserved for Assistant ID, the second for Transient Assistant, the third one for SQuAD, and the 4th one for Workflow ID. So pass the first three parameters as NULL and then the 4th one with the workflow ID if you are using Web SDK. Correct me if I'm wrong

Can you provide a code example for the parameters? In my implementation, I only passed the id to vapi.start. here's my example implementation when starting a conversation

const startVapiConversation = async (): Promise<boolean> => {
    try {
      if (type === "generate") {
        await vapi.start(process.env.NEXT_PUBLIC_VAPI_WORKFLOW_ID!, {
          variableValues: {
            username: userName,
            userid: userId,
          },
        });
      } else {
        const formattedQuestions = formatQuestions(questions);
        await vapi.start(interviewer, {
          variableValues: {
            questions: formattedQuestions,
          },
        });
      }
      return true;
    } catch (error) {
      console.error("Failed to start Vapi conversation:", error);
      return false;
    }
  };

@Shubham Bajaj

Can you share the steps to reproduce this?

why is it asking thesame questions multiple time? https://cdn.discordapp.com/attachments/1385998823603568820/1390047917682987221/20250702-1905-10.8273804.mp4?ex=6866d681&is=68658501&hm=7c3070057c130ae60f737d48555e0815cc9046c35215e804f4e1b49cc4cd16cf&

Hey there, I think we're having a bit of a misunderstanding here. I'm referring to the shared screenshot you provided earlier, where you're encountering an error. However, what you've actually shared is a workflow video and workflow property screenshot that doesn't clearly illustrate how we can reproduce this error. If I'm understanding correctly, you're trying to convey that using the workflow you mentioned results in an error on the VAPI dashboard. If that's the case, could you please share your WORKFLOW ID so I can investigate the logs further?

you seem to be the one misunderstanding here, I already replied to the earlier bug, saying "Fixed" then I said there's another bug You said I should provide steps to reproduce, and I clearly said that my voice agent is "asking the same questions multiple times" with a video. What's hard to understand there? call id: 33cbc0cb-2756-43c9-a2eb-404e706d30ba

@druxamb.base.eth @Vazgen Our vision for workflows was to create an AI assistant or automation board that seamlessly handles common issues like prompting, hallucination, and logical flow management. By controlling the logic through our end, we aim to provide a smooth experience where users can focus on conversational notes and other communication aspects. However, we encountered challenges with the workflow, particularly with repetitions. This issue was persistent and required multiple fixes, affecting not only you but also other users who reported similar problems. We value your feedback and assistance in resolving these issues. Could you take some time this week to try the updated workflow in front of me? With the recent changes, we can discuss and implement any suggestions you might have to enhance the experience.

Alright, the old workflow + assistant was all cool and works pretty much fine. When's the best time to share this with you? kindly share the link to you cal or calendly @Shubham Bajaj

Cc: @Shubham Bajaj

Thanks @druxamb.base.eth I am looking into your issue reported in another thread, for meet please check your DM.