HubSpot connector manage_crm_objects tool: createRequest rejected as String instead of JSON object

Status Open
Maintainer reply None cached
Activity 1 comment · opened Sep 16, 2026

Description

The HubSpot connector's manage_crm_objects tool consistently fails when calling createRequest, even with a minimal, valid nested JSON object payload.

Error

[createRequest] Expected a JSON object (record com.hubspot.integration.tools.model.manage.objects.CreateCrmObjectBatchRequest) but received String. Pass this field as a nested JSON object {}.

Steps to reproduce

Call manage_crm_objects with:

{
  "confirmationStatus": "CONFIRMED",
  "createRequest": {
    "objects": [
      {
        "objectType": "notes",
        "properties": { "hs_note_body": "test" }
      }
    ]
  }
}

Observed behavior

  • Fails every time with the error above, across multiple separate sessions and multiple days.
  • Reloading the tool schema via ToolSearch does not fix it.
  • Reconnecting/checking connector status shows HubSpot as "connected" with tool_count 25 (not in a failed or needs_auth state), ruling out a dropped session.
  • Earlier in the same overall working relationship (different session, same HubSpot connector), the exact same createRequest shape worked successfully to create calls, notes, and tasks. The failure appears to have started after a session/context switch mid-conversation.
  • Tried multiple variations: full batch payload, single-object payload, with and without associations, re-stringified JSON — all produce the identical error.

Impact

Blocks all CRM object creation (notes, calls, tasks, contacts) via this tool for the affected session, while read operations (search_crm_objects, get_crm_objects, query_crm_data) continue to work fine.

Environment

  • Claude Code desktop app
  • HubSpot connector (plugin/connector id 4be071cc-933a-4511-8d86-b97f9a004a18)
  • Tool: manage_crm_objects, createRequest parameter

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗