Suggestion: Double-check that your tool names in the workflow and prompts exactly match the names you configured (e.g.,

go_high_level_mcp_contact_get_tool

). For example, your workflow node should reference the tool like this:

json
{
  "type": "gohighlevel.contact.get",
  "function": {
    "name": "go_high_level_mcp_contact_get_tool",
    "description": "Use this tool to retrieve an existing contact from GoHighLevel using the user's email address or phone."
  }
}

*Even a small mismatch in the tool name will prevent the tool from triggering properly*—update your workflow and test again. For more, see the [GoHighLevel integration guide](https://docs.vapi.ai/tools/go-high-level). Sources: - [GoHighLevel Integration](https://docs.vapi.ai/tools/go-high-level) - [Custom tools troubleshooting](https://docs.vapi.ai/tools/custom-tools-troubleshooting)

Hey, I can help you get this working smoothly. The issue likely comes from how the contact ID is being passed between the fetch and calendar tools, GoHighLevel often fails if the contact isn’t properly created or returned before booking. I’ve fixed similar cases by adjusting the workflow logic to ensure the contact gets created first and reused across tools. Could you share the specific error log or API response? @qxh