Feature Requests

Want long term conversational memory to be built in.

Currently, there’s no way to add background sound during a call that uses workflow, which makes the conversation feel unrealistic and the pauses awkward. It would be great to have the same level of voice customization in workflows as we have with agents.

Currently, when building a workflow, users must configure the model and voice settings individually on each node. This can be repetitive and time-consuming, especially for large workflows. Proposal: Introduce global settings for model and voice at the workflow level. These settings would automatically apply to all nodes by default. If needed, users could override the global settings on a per-node basis. Benefits: Simplifies the workflow creation process Reduces setup time and configuration errors Enhances maintainability by centralizing default settings

Character limits for Conditions increased from 1,000 to 3,000 or more

Would like to be able to add <break time='2s' /> commands in workflows.

Calls have office background sounds on. Would a way to toggle it off.

Calendly Integration for checking appointment times and booking appointments.

Allow the Transfer module to accept a Server URL (webhook endpoint) that can be called at runtime to dynamically retrieve the phone number (or SIP address) for call transfer. This enables context-aware routing decisions (e.g., based on customer data, location, or time) without hardcoding numbers into the agent configuration. The endpoint would return a standard destination JSON object per Vapi’s existing transfer-destination-request schema.

Hi there, hope you are doing well. I wanted to ask a specific question regarding the tool function node created directly through the tool panel in the dashboard. I have created several functions up until now through VAPI, and all of them are working just fine with separate agents. The problem is that when I decide to use the created tool in a workflow (that is supposed to send the call info to Make.com scenario), it does not trigger the function, even though the conversation was passed onto the function node. This problem occurred 3-4 days ago and none of the functions created inside the VAPI, used inside the workflow, have not worked since then. Before, it worked just fine. We also tried it on different accounts, and it doesn't work there either. The api call node, on the other hand, works well and sends the info to make.com scenario, but without the call info such as call ID, customer panel, etc. I have all edges and conditions set well which allows the workflow to pass the conversation onto the tool function node. The function does not require any variable to be gathered, it is there with no variables (it is used just to gather call info). The function determines that either user is allowed (on the whitelist) or banned (on the blacklist) thanks to Make.com scenario and sends a response to the vapi system. My question is what could be the problem, why it doesn't work. Is it a problem on my side due to incorrect setup, or are you experiencing some problems on your side? Thanks for the answer

Most of the times, when adding variables to a node in a workflow, I've to add string variables. I've to: Click in add variable. Go to variable and press edit. Edit the name. Save Having in line edit will be good, at least when you only have to edit variable name