Hi, after porting my systemprompt over to make, my tool to trigger my webhook just stopped working and the webhook never gets triggered, was wondering is this a problem with vapi or make, every time I run my scenario on make, on vapi side it asks to sync and then the tool I need it to trigger suddenly disappears. https://cdn.discordapp.com/attachments/1360129869526204536/1360129869824131142/Screenshot_2025-04-10_190629.png?ex=67f9ff26&is=67f8ada6&hm=986bf98fcdc4b6d47ec90ec45ee39c1c468b8dd1fb1842a9a989ccd254be8dc1& https://cdn.discordapp.com/attachments/1360129869526204536/1360129870092308641/Screenshot_2025-04-10_190642.png?ex=67f9ff27&is=67f8ada7&hm=a59a38736eca1f285e3ebc3264cb181de847913ceee66fe288c9f11c86763a56& https://cdn.discordapp.com/attachments/1360129869526204536/1360129870537162772/Screenshot_2025-04-11_014805.png?ex=67f9ff27&is=67f8ada7&hm=d8f3f15d40454ffbdc55639b132319dc7008b56638c0383ff7c9f1a76f50b371&

Hi there! 👋 I understand you're having issues with your webhook not triggering after porting your system prompt to Make, and your tool is disappearing after syncing on the Vapi side. I don't have enough information about your specific Make scenario configuration or the exact content of your system prompt to pinpoint the exact cause. However, I can definitely help with some common reasons and troubleshooting steps for this issue! ## Why Your Tool Might Be Disappearing After Syncing This is actually a known issue that several users have experienced. Here are some potential reasons: 1. **System Prompt Changes Impact**: After porting a system prompt to Make, webhooks can stop triggering. Another user reported exactly the same issue: "after porting their system prompt over to Make, my tool to trigger my webhook just stopped working and the webhook never gets triggered" and "every time I run my scenario on make, on vapi side it asks to sync and then the tool I need it to trigger suddenly disappears." 2. **Vapi UI Bugs**: The Vapi UI has some bugs where settings are not being saved properly, and after reloading, headers or other configurations might disappear. 3. **Secret Tokens Storage Issues**: Secret tokens for tools are sometimes not stored correctly in Vapi, which can lead to tools not functioning as expected. After reloading the UI, the secret field might be empty. 4. **Incorrect Response Format**: Vapi might not be receiving the correct response format from Make, causing errors and the tool to not function properly. ## Troubleshooting Steps Here are some steps you can take to troubleshoot the issue: ### 1. Check Webhook Configuration - Ensure the webhook URL provided by Make is correctly configured in Vapi without any typos - Verify that the HTTP method (GET, POST, etc.) matches what Make expects - Check that the tool name in Vapi matches what Make expects ### 2. Inspect Logs and Data Flow - Look at the Make scenario execution logs for errors

Noticed this myself. My webhook (tool custom function so real-time) was working reliably last week. Starting a couple days ago it has been working inconsistently

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!