Skip to main content
For an Agent with an appointment goal and a connected HubSpot or GoHighLevel account, NexorAI and Claude with Nexor MCP can configure native CRM booking. The account must grant calendar access. Changes require an authorized operator or an API key with workflows:write; reads require workflows:read.
1

Inspect the current setup

Ask: “Show the CRM booking setup for this Agent and the available calendars.”The assistant reads the saved provider, calendar or meeting link, installed tools and current revision. GoHighLevel calendars include their location, so calendars from different sub-accounts remain distinguishable.
2

Choose and confirm

Ask: “Use the Sales calendar for this appointment Agent.”The assistant resolves the exact choice from the CRM catalog and confirms the change. Setup verifies provider access and installs the native tools together with the booking configuration. HubSpot also requires an identifiable host and available slots in its setup check. Another provider’s configuration or a manually managed setup can block replacement.
3

Read back the result

The assistant reports the saved calendar or meeting link and active tools. This verifies setup, not a successful customer booking. A separate booking test is still needed to verify the complete appointment flow.

​
Change or remove setup

Ask to switch to another listed choice, or to remove native CRM booking from this Agent. Both actions require confirmation. Removal deactivates the native tools and clears their booking configuration; it does not cancel existing meetings. A locked Agent requires its authorized owner. If configuration changes during the request, the assistant must reread it before retrying. HubSpot’s native change tool requests a reschedule or cancellation from the team. It does not automatically reschedule or cancel the meeting in HubSpot.

​
Check GoHighLevel import evidence

Ask: “Show the latest import runs for this GoHighLevel connection and explain anything blocking recurring imports.” The assistant can read the latest 20 stored runs, timestamps, safe counters, failure codes, recurrence settings and whether automatic imports can run. These records cover a connection, which may feed several Agents. Their counters do not prove that one particular Agent synchronized. An empty history means no stored execution evidence. A connected account is not proof of a completed import. This diagnostic operation does not launch an import or replay failed work. It does not expose raw lead payloads or provider error messages.

​
Public MCP and API

  • list_agent_crm_booking_choices: verified HubSpot links or GoHighLevel calendars.
  • get_agent_crm_booking: saved configuration and current revision.
  • change_agent_crm_booking: configure or remove with confirm=true and expected_revision.
  • get_agent_ghl_import_status: connection-level import evidence.
Each tool requires workflow_id. Groups must choose a concrete member Agent. For REST request fields and responses, see configure or remove and import evidence.
Last modified on September 21, 2026