Skip to main content
NexorAI and Claude with Nexor MCP can inspect and configure Nexor’s integration with HubSpot, GoHighLevel, Kommo, Zoho, custom incoming webhooks and Odoo. This covers the integration settings implemented by Nexor. It does not grant every administrative capability of a CRM, such as creating arbitrary CRM objects or changing its user permissions. These operations require the matching backend and MCP release. An advertised tool alone does not prove the backend has been deployed. Configuration reads require workflows:read; changes and previews that store an approval fingerprint require workflows:write. NexorAI uses the signed-in operator’s permissions. Locked Agents remain protected.

​
Choose the scope first

In an Agent or Group conversation, the assistant uses scoped tools and preserves sibling Agents. Shared defaults, connection-wide imports and reassignment require an account conversation in NexorAI, outside any selected Agent or Group. Claude uses scope: "account" explicitly.
1

Read the current configuration

Ask: “Show the CRM settings and anything preventing synchronization.” The assistant reads exact connection IDs, the configuration revision and available provider choices. Connection-wide evidence is labeled; it is not proof that a specific Agent synchronized.
2

Review the effect

For an account change, the assistant lists every affected Agent, including Agents that inherit defaults. New Agents can also inherit the changed defaults. Do not omit a locked Agent to bypass authorization.
3

Confirm and read back

The write includes the reviewed expected_revision, all affected_workflow_ids and confirm: true. A changed configuration, task membership or lock rejects the action. The assistant rereads the state before requesting another confirmation. A successful save is not a completed import or CRM write.

​
Configuration now available

  • Collected Variables: inspect or replace metadata bindings and value conversions with get_agent_variable_bindings and set_agent_variable_bindings.
  • GoHighLevel: choose intake pipelines, stages, workflow/default routing, recurring import filters and outcome mappings with change_agent_ghl_flow and its catalog tools.
  • Zoho: configure per-Agent fields, Variables, statuses, inheritance and output switches with change_agent_zoho_flow; use change_zoho_account_defaults for shared defaults while preserving overrides.
  • HubSpot: scoped list routing, fields, statuses, portal intake, activity history and Group behavior; list_agent_hubspot_catalog supplies owners, pipelines and properties. change_hubspot_account_controls manages shared intake and history switches.
  • Kommo: create, change, pause, activate or remove a route with change_agent_kommo_route, including unsorted intake for the primary route. Changed routes are saved paused. count_agent_kommo_source counts without importing; has_more means a lower bound.
  • Custom incoming webhooks: create, map, pause, activate or remove with change_agent_custom_intake. reassign_crm_intake moves a custom entry or Kommo route to another Agent and leaves it paused; existing leads do not move.
  • Native booking: choose a HubSpot meeting link or GoHighLevel calendar using the CRM booking tools.
list_crm_account_connections includes unassigned custom entries. get_crm_account_configuration returns shared settings, revision and the Agents to review. get_crm_intake_details returns an authorized receiving URL and, for custom webhooks, recent field paths/types without lead values. Receiving URLs contain a secret: share them only with the authorized sender operator. rotate_kommo_webhook_token replaces that URL after confirmation; configure external senders with the new URL. Old-subscription cleanup is best effort.

​
Imports and manual synchronization

run_crm_account_import queues the saved configuration, which the worker checks again before starting:
  • GoHighLevel dry_run reads only. backfill imports historical contacts without assigning Agents or starting outreach.
  • Kommo run_now scans all enabled routes and may import or move cards and trigger outreach.
  • Odoo inbound follows existing runtime gates and may enroll/contact leads. It cannot execute outbound synchronization.
Use get_crm_import_job with the returned job ID. queued is not completion; a completed job can contain errors or skipped records. not_found is not proof of completion. Never blindly retry a request with an uncertain result. get_hubspot_sync_preview reviews deal synchronization or one contact’s unambiguous active context. run_hubspot_sync requires both configuration and context revisions. Contact replay can synchronize saved status and unsynced history/fields across that contact’s history; it is account-scoped. Deal synchronization applies configured transitions and can trigger their effects. get_agent_crm_diagnostics reports safe connection-level evidence for all supported providers. It omits raw errors, credentials and lead payloads. get_agent_ghl_import_status offers detailed stored GoHighLevel runs. Empty history means there is no stored execution evidence.

​
Odoo boundaries

Use connect_crm with provider: "odoo". Enter the URL, database, username and API key only on the secure hosted form. Reconnecting the same identity rotates its credentials and preserves configuration. Do not paste credentials into chat. For one Agent or Group, use get_agent_odoo_inputs, preview_agent_odoo_inputs, then change_agent_odoo_inputs. The save requires the same successful, fresh preview and exact patch. Routes, field mappings and lifecycle rules preserve other Agents’ settings. Preview counts cover the whole connection, including preserved routes. Use change_odoo_account_inputs for shared routes, cutover, fields and limits. Legacy connections only support legacy-equivalent routes, enablement and cutover. Unsupported upgrades are rejected. list_odoo_sync_conflicts and resolve_odoo_sync_conflict expose persisted conflicts and allowed decisions; resolving records a decision without enqueueing a sync. Incomplete provider visibility cannot be ignored as a business decision.
Odoo’s newer inbound apply engine and outbound execution retain their runtime blocks. change_odoo_account_outputs can save disabled output configuration or request a read-only preview. An incomplete scan is not approval and zero operations from it do not prove that no work exists. Activities, quotations and outbound failure recovery remain outside this release.
The public reference includes account configuration, imports, diagnostics and Odoo inputs. This release adds 21 tools after the preceding 16 CRM parity tools, for 37 additions in that program; it is not the size of the complete Nexor MCP catalog.
Last modified on September 21, 2026