Can ChatGPT edit HubSpot custom objects?

Not through HubSpot's own MCP server as documented today. ChatGPT can write to 12 standard object types, and custom objects need your own tool.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

The short answer

  • ChatGPT can't edit HubSpot custom objects through HubSpot's MCP server as documented in September 2026. HubSpot's list of writable objects covers contacts, companies, deals, tickets and eight other standard types, and custom objects aren't on it.
  • A ChatGPT Business user reported the same gap on the OpenAI community forum on March 27, 2026. The HubSpot connector reached standard objects but gave no usable access to custom objects, even with custom-object scopes granted.
  • HubSpot's CRM API does support custom objects, so the working route today is a custom MCP tool or script that calls the API with custom-object scopes.
  • Check which object your process lives on before you plan an AI workflow around HubSpot. A custom object puts it outside what the stock connection can touch.

Why custom objects fall outside the connector

HubSpot's MCP server gives an AI client a fixed set of tools. Each tool knows one type of record, like a contact or a deal. HubSpot publishes that list, and says it will grow as they add more tools.

Custom objects are different by design. You define them yourself, with your own name, fields and links, so a stock tool can't know their shape in advance. That's why the forum poster's objects, named things like monthly site surveys and service actions, never showed up. Their scopes were right. The connector simply had no tool for them.

HubSpot also limits associations to the same set of standard objects. If your custom object links deals to sites, ChatGPT can see the deal but not the link.

What ChatGPT can reach in HubSpot over MCP

From HubSpot's MCP server documentation.

AccessHubSpot objects listedSource
Read and writeContacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions, segmentsdevelopers.hubspot.com/mcp
Read and writeEngagements: calls, emails, meetings, notes, tasksdevelopers.hubspot.com/mcp
Read onlyUsers, teams, reporting structures, owners, roles, seatsdevelopers.hubspot.com/mcp
Read onlyCampaigns and campaign metrics, landing pages, website pages, blog postsdevelopers.hubspot.com/mcp
Custom objectsNot in HubSpot's MCP object list; reachable through the CRM API with custom-object scopesdevelopers.hubspot.com/mcp; community.openai.com

Checked on developers.hubspot.com/mcp and the OpenAI community thread of March 27, 2026, in September 2026. HubSpot says the object list will grow, so re-check before you build.

Your options if your data lives in a custom object

You have three routes. First, build a small MCP server of your own that calls HubSpot's custom-object endpoints, and add it to ChatGPT as a connector. It works, but you now own the code and its token.

Second, move the data onto a standard object HubSpot's MCP server can write, such as deals or tickets with custom properties. That's a data-model change your whole team will feel.

Third, run your sales work in a CRM where the AI connection covers every action. In SalesCrew, every action in the app is also an MCP tool, 140-plus in all, with the same effect as the button. That includes custom fields, which you create and fill through MCP tools as well as the UI. Tokens are issued per user and scoped like a logged-in user, and any external send waits in one approval queue.

Check the object before you promise the workflow

Teams often discover this gap after they've sold an AI workflow internally. Before you start, open HubSpot's object list and find where each step of the process stores its data. If one step writes to a custom object, plan for your own tool from day one.

Questions

Which HubSpot objects can ChatGPT write to through MCP?
HubSpot's MCP page lists read and write access for contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions and segments. Calls, emails, meetings, notes and tasks are writable too. Users, teams, owners, campaigns and website content are read-only, as of September 2026.
Does HubSpot's API support custom objects?
Yes. HubSpot's CRM API has custom-object scopes, such as crm.objects.custom.read and crm.schemas.custom.read. The user who raised the problem on the OpenAI forum in March 2026 confirmed the API itself could reach their custom objects. The gap was in the ChatGPT connector, not in HubSpot's data.
Can I build my own MCP tool for HubSpot custom objects?
Yes, if you have a developer. You write a small MCP server that calls HubSpot's custom-object endpoints with an access token from a HubSpot app, then add it to ChatGPT or Claude as a connector. You then own that code, its token scopes and its upkeep when HubSpot changes the API.
Who can connect HubSpot's MCP server to ChatGPT?
HubSpot says the account admin has to connect first, and other users can connect after that. Access is controlled through a user-level app and its scopes, and you need to be on HubSpot's new developer platform to create that app.