Looks like you’ve got two issues: auth and the tool not firing. GHL API keys are scope-specific if the VAPI app is at agency level but the key came from a location (or vice versa), it won’t work. Try generating a new key from the exact location and check contact write permissions. If the assistant isn’t calling GHL, the tool conditions might not be triggering. Force the GHL tool to run in testing and check VAPI logs to see if it’s skipped or failing. Quick question: does the app install scope match where the API key was created? @Rory M.