I’ve hit this exact wall before! When you set a server URL on your tool, Vapi basically hijacks the tool-call/function-call events and sends them there instead of your main webhook. It’s annoying but that’s how they designed it. Your edit is spot on - server URL = no webhook events for tools, no server URL = you get the events but have to handle the API calls yourself. I usually go with option 2: keep the server URL but grab the call metadata from conversation-update events at the start of each call, then correlate it with your tool executions. Works pretty well once you set it up. If you’re stuck on the implementation details, I’ve done this exact setup for a few clients and could walk you through it. The correlation logic can be a bit tricky to get right.