Yeah, I’ve run into this before, Vapi can say the connection succeeded, but the integration doesn’t actually stick, so nothing fires. Most of the time it’s an account or permission mismatch, or the integration isn’t attached to the agent that’s running. GHL sub-accounts also cause this a lot even though there’s no error shown. Happy to help you sort it out properly. When you connected it, was it from the same workspace and account your Vapi agent is using? @5ull3n