#blocks not sure if it's just me, * but the page is freezing a lot, i have to refresh and go back in, .... * it would be nice to have slightly different colour between tools/ convo / workflow .... * between working on input / block/ output .... it keeps defaulting to output 4 convo, input 4 tools, .... makes it difficult to work and flow through, because we have to keep clicking back to 'block' for convo ... each convo, you have to click back to 'block' ... please stay in last choice, and follow through to save clicks * also for block, please allow bigger viewing area, difficult to scroll through and review prompts.

@Mike I'm sorry to hear that you're experiencing issues with the page freezing and having difficulties with the user interface. Your feedback is very valuable, and I'll make sure to pass it along to the appropriate team for consideration. In the meantime, here are a few suggestions that might help: 1. **Page Freezing**: This could be due to browser issues, heavy cache, or extensions that may interfere with the page. Try clearing your browser cache, disabling unnecessary extensions, or using a different browser to see if the problem persists. 2. **UI Color Differentiation**: Noting your preference for color differentiation between tools, conversation, and workflow, I'll forward this suggestion to our design team for future updates. 3. **Defaulting to Output/Convo/Input**: Your feedback on the default settings causing inconvenience is important. I'll report this to our development team to consider making the last choice sticky to improve workflow efficiency. 4. **Viewing Area for Blocks**: I understand that a larger viewing area would enhance your ability to review prompts. This suggestion will also be passed on to our development team for potential improvements. For the freezing issue, if the problem continues after trying the above steps, please reach out to our support team for further assistance. If there's anything else I can help you with, please let me know!

Hey @Mike can you please record a loom video for the page freezing issue, and another video for the feedback regarding blocks explaining what issue your facing and how you want it to be.

oh no Shubham, @Vapi thank you for making the window larger. i was just working on block, and the save button is not consistent therefore i lost my work, we need autosave feature .... also breaking links between conversation and blocks is VERY difficult, please allow similar to make.com (ie. highlight link and perhaps in the right side panel, have a breaklink) or if allowing a drag and drop function, when however need to be able to select which link is being moved.

@Mike I'm really sorry to hear about the issues you're facing with saving your work and managing the links between conversations and blocks. Losing work can be frustrating, and I understand the need for a more intuitive interface for link management. 1. **Autosave Feature**: I agree that an autosave feature would be a valuable addition to prevent loss of work. I'll make sure to pass this suggestion on to our development team. 2. **Breaking Links Between Conversations and Blocks**: Your suggestion for a more user-friendly way to break links, similar to the functionality on make.com, is a great idea. I'll forward this feedback to our team to consider implementing a feature that allows you to easily manage links. In the meantime, please make sure to manually save your work frequently to prevent any further loss. If you encounter any more issues or have additional feedback, don't hesitate to reach out. Your input is crucial for us to improve our service. Thank you for bringing these matters to our attention.

saved button either is not there sometimes, or being covered by the 'we're in beta' banner

@Mike I apologize for the inconvenience caused by the 'Save' button being obscured or not appearing due to the 'We're in beta' banner. This is certainly something that needs to be addressed to ensure a smooth user experience. I will report this issue to our development team so they can work on a fix to prevent the 'Save' button from being covered or missing. In the meantime, if you're able to move the interface elements around or zoom out in your browser, it might temporarily help to access the 'Save' button. Thank you for your patience and for reporting this issue. If there's anything else I can assist you with, please let me know.

Why is it not possible to pass variables through the server url when using Vapi blocks? I mean when initiating a call from Make. I don't really understand why there isn't any way to modify the input schema for the start block

#blocks if blocks were used for an outbound agent, would receiving an 'input' from a tool via make.com not be the trigger (currently not possible, or please provide doc support on this type of event).

The two things I tried before realizing it wasn't possible: 1. trying to reference global variables (which were also defined in the assistant Analysis settings) by {{global.first_name}} and so on 2. Instructing that the start block be completely ignored the second method does actually work in some scenarios, but it's pretty buggy https://cdn.discordapp.com/attachments/1307015817808056412/1311764187726217357/image.png?ex=674a0b19&is=6748b999&hm=32d2b76b63ac198b857dbf50a362eca5e23409e4b81b9114e79d4352901ae786&

@Vapi @Shubham Bajaj Can you please setup that external triggers, can initiate blocks? Do you have an in progress list available to share for features in general?

@Mike It sounds like you're looking for a way to initiate VAPI blocks using external triggers, such as incoming data from Make.com (formerly Integromat). Currently, if VAPI blocks do not support receiving input directly from a tool via an external trigger, this would be a feature request that needs to be considered by the development team. As for setting up external triggers to initiate blocks and providing an in-progress list of features, I don't have the capability to implement new features or access to a development roadmap. However, I can certainly pass your request and feedback to the relevant team. For now, please ask support for more info on this, as they would be able to provide you with the most accurate and up-to-date information regarding feature requests and the development roadmap. Your input is valuable, and it helps shape the future of the platform. Thank you for your suggestions!

I think the only development necessary would be adding a new API call that can trigger Vapi blocks the same way API calls can be used to trigger normal Vapi assistants. There are some small technical things that need to be sorted but it seems like an important feature

@jon Your suggestion to add a new API call that can trigger VAPI blocks, similar to how API calls can trigger normal VAPI assistants, is indeed an insightful one. This feature would enhance the flexibility and integration capabilities of VAPI with external systems like Make.com. I understand that while there may be technical considerations to address, the ability to initiate VAPI blocks through an API would be a significant improvement for developers looking to create more dynamic and responsive voice applications. I will forward your suggestion to the development team for review. They will assess the feasibility and potential impact of implementing such a feature. Your feedback is greatly appreciated, and it plays a crucial role in the continuous improvement of the platform. Please keep an eye on official updates or reach out to support for the latest information on new features and developments. If you have any more ideas or need further assistance, feel free to share!

Hey @Mike we have added delete edges/links, when you mouse over, you will a see a delete icon along with minor usability improvements. i think it's rolled out to production two days back. can you take a look?

Yes the delete link is much better thank you @User , just testing setup for what I currently am doing with vapi. 2 items, support for knowledge base, and support for external trigger to get vapi running, for referencing table info for return callers

> NOTED: 2 items, support for knowledge base, and support for external trigger to get vapi running, for referencing table info for return callers

@Shubham Bajaj Any update on external triggers for running blocks?

bump on this + knowledge base and adding context for the prompts in blocks other than the instruction itself @Shubham Bajaj

@krish450 it's in our list for blocks, once pushed to PROD you will be notified.

#1316501572355756103 @Vapi we need a way to edit which assistant a block is pointing to, current this is only possible when setting up the initial block 😭

@Mike I understand how being able to edit the assistant that a block points to after its initial setup would be very useful for managing and updating your workflows more efficiently. I'll make sure to pass on your feedback to the development team so they can consider adding this feature in a future update. It's important that our tools evolve to meet the needs of our users, and your input is crucial in this process. For now, if you need to change the assistant a block is pointing to and can't do it through the current interface, please reach out to support for assistance. They might be able to provide a workaround or help you with the changes you need to make. Thank you for bringing this to our attention, and please let me know if there's anything else I can do for you!