The HubSpot Connector for Claude Will Not Draft Your Campaign: What It Reads, What It Writes, What to Connect Alongside It
The stack is common enough to have a shape: HubSpot as the CRM, a paid Claude seat for everyone on the marketing team, and the HubSpot connector switched on in Claude’s connector directory. It works well for the first week. Then someone asks Claude to draft the nurture in HubSpot, and Claude explains, politely, that it cannot.
This is a capability audit of the HubSpot connector for Claude as of September 2026: what it reads, what it writes, where the walls are, and what to run beside it so Claude can move from answering questions about your contacts to drafting the marketing that reaches them. It is not a case for replacing HubSpot. Marqeable syncs audiences from HubSpot and complements it. The case is for a second connector in the same chat.
If your team is on ChatGPT instead, the equivalent audit is connect HubSpot to ChatGPT: what marketers actually get.
What the HubSpot connector for Claude reads and writes
HubSpot documents the connector in two places: the setup and usage guide and a changelog entry from August 2025 that expanded the object list and added admin controls. Read together, they give a clear picture.
| HubSpot object | Read | Write | Notes |
|---|---|---|---|
| Contacts, companies, deals, tickets | Yes | Create and update, up to ten records per request | No delete |
| Custom objects | Partial | Limited | Reported as awkward in practice |
| Notes, tasks, engagements | Yes | Notes and tasks | Engagement data is blocked when Sensitive Data settings are on |
| Marketing emails, campaigns | Read-only | No | Includes campaign attribution, read-only |
| Workflows and sequences | No | No | Documentation states the connector cannot create or edit them |
| Sending anything | No | No | There is no send action |
Third-party write-ups line up with HubSpot’s own. Hubjoy’s connector overview notes the ten-record cap and that attribution is read-only; SyncGTM’s integration guide covers the same limits from the Claude Code side. The connector also requires a paid Claude plan, and on Team or Enterprise an Owner has to add it before members can connect.
Setting it up on a Team plan
The setup is quick, and the one thing that trips people up is the ownership rule. On Claude Team and Enterprise, custom and directory connectors are added at the organization level. Per Anthropic’s custom connector guide, only an Owner can add a connector, after which every member sees it and clicks Connect to sign in with their own HubSpot login. Members without permission see a request button rather than an add button.
That ownership rule is a feature. It means the person who decides which systems Claude can reach is the person who owns the workspace, and each member’s access is scoped to their own login. Keep it in mind when you add a second connector: the same Owner adds it the same way.
The three walls people hit
The ten-record cap. Ask Claude to update the lifecycle stage on the 60 contacts who attended the webinar and it will do ten, then stop. HubSpot caps bulk creates and updates at ten records per request, a deliberate guard against an assistant rewriting a large slice of the CRM in one call. It makes the connector safe for handoff notes and small property fixes and unsuitable for list-scale changes, which is the right trade.
Marketing objects are read-only. Claude can tell you how the spring campaign attributed, which emails a contact received, and what the open rates looked like. It cannot create the next email, edit the campaign, or touch the workflow. One developer found this frustrating enough to build his own MCP server for HubSpot marketing email drafts, and wrote it up on dev.to. He left the send action out on purpose, to prevent accidental sends. That single decision, made independently by an individual builder, is the same one every trustworthy marketing connector should make.
There is no workflow object. This is the wall behind the other two. The connector exposes records. It does not expose the plan for what happens to those records next: which automation a contact is in, what step fires Friday, what is scheduled for the 16th. A re-engagement email Claude drafts for a stalled cohort may land on top of a follow-up HubSpot is already going to send, and nothing in the connector can warn you.
What a CRM connector is for
None of the above is a complaint. A CRM connector should be excellent at who questions, and this one is.
- “Which deals in proposal have had no activity for two weeks, and who owns them?”
- “Summarize the last five touches on Northwind before my call.”
- “Create a task for the owner of every deal that stalled after the pricing page visit.”
- “Which webinar attendees are at companies with more than 200 employees and no open deal?”
Those questions are answered from the system of record for people, which is HubSpot, and the answers come back faster than a saved view. The connector also keeps its writes small and reversible, which is exactly what you want from an assistant touching the CRM. If the connector did nothing else, it would still be worth switching on.
The mistake is expecting it to hold the marketing. HubSpot holds contacts, companies, deals and activity. The voice guide, the calendar, the automations and the approval queue are a different system of record, and Claude needs a connector to that one as well. The broader version of this argument is in HubSpot will not run your campaigns.
What to connect alongside it
Marqeable’s MCP server holds the marketing half. Ten read tools cover your business context (brand, ICP, voice, offers), campaigns with their pieces and send days, semantic search over existing content, the content calendar with scheduled sends and market dates, and every automation with its plan. Six write tools create campaign drafts, content drafts, anchored suggestions on existing copy, brief updates and automation drafts. Every write is a draft. There is no send, launch, publish or delete tool, and every result links to the page in Marqeable where a person approves it.
Here is a session with both connectors on. HubSpot answers the first question. The rest is what a CRM connector structurally cannot return.
You: From HubSpot, how many contacts moved to Sales Qualified Lead in August, and how many of those have a demo booked?
Claude: 41 contacts entered Sales Qualified Lead in August. 17 have a meeting logged; 24 do not.
You: What do we have running or scheduled that would reach the 24?
Claude: From Marqeable: your campaign list shows one active nurture campaign, “Fall pilot”, with four pieces, and the calendar has its second email going out on the 9th and a LinkedIn post on the 11th. The automation overview shows no automation triggered on Sales Qualified Lead, so the 24 are only reached if they are on the Fall pilot list. 9 of them are not.
You: Draft a customer-story campaign for SQLs with no demo booked. Three pieces, start the 15th, light volume, use the finance-team story we published in June.
Claude: I searched your content and found the June finance-team story. I created a campaign draft called “SQL customer story” of type nurture starting the 15th with three pieces: a short email leading with the story on day 0, a LinkedIn post on day 3, and a direct demo-offer email on day 7, all using the current pilot offer from your business context. Copy only, no images generated, and it is a draft waiting for your review: [link to the campaign draft in Marqeable].
Two things in that exchange are impossible with the HubSpot connector alone. Claude read the calendar and the automation plan to find out that nine people were falling through. And the result landed as a campaign draft in the system that will run it, not as text in the chat. The approval is still yours, which is the whole point; the design reasoning is in the draft-only rule.
Run both connectors in every marketing chat. HubSpot for who: contacts, deals, lifecycle stages, small record updates. Marqeable for what and when: voice and offers, the calendar, campaigns, automations, and drafts back into the queue. Neither replaces the other.
Adding Marqeable to Claude
The server is https://app.marqeable.com/mcp, a remote MCP server over HTTP with OAuth 2.1. You sign in with your normal Marqeable login in a browser window, and Claude sees exactly what your account can see. There are no API keys.
On a personal plan, in Claude on the web or desktop: open Settings > Connectors, click Add custom connector, name it “Marqeable”, paste the address, click Add, then Connect and sign in. Enable it from the tools menu in a chat, next to HubSpot. On Team or Enterprise, the Owner adds it the same way under Organization settings, and each member clicks Connect. As of September 2026 custom connectors are available on every Claude plan, with the free tier limited to one.
A good first prompt with both on: “Run whoami, then get_business_context, then tell me what is on the calendar this month, then pull this month’s new Sales Qualified Leads from HubSpot.” If both halves answer, you have the setup. For the deeper question of what to do at each HubSpot lifecycle stage once the two are connected, see HubSpot lifecycle stages are not lifecycle marketing, and for the workflow-builder comparison, HubSpot workflows vs AI agents.
Frequently asked questions
Can the HubSpot connector for Claude create marketing emails or workflows?
No. As of September 2026, HubSpot’s documentation says the connector cannot create or edit workflows or sequences, and the marketing objects it exposes, such as campaigns and attribution, are read-only. It can create and update CRM records such as contacts, companies and deals, in batches of up to ten.
Why does the HubSpot Claude connector stop at ten records?
HubSpot caps bulk create and update actions through the connector at ten records per request. It is a deliberate guard against an assistant rewriting a large slice of the CRM in one call. It makes the connector safe for handoff notes and small property updates and unsuitable for list-scale changes.
Who can add the HubSpot or Marqeable connector on a Claude Team plan?
On Claude Team and Enterprise, only an Owner can add a custom connector, under Organization settings. Once it is added, each member clicks Connect and signs in with their own login. HubSpot’s connector also requires a paid Claude plan.
What should I connect alongside HubSpot in Claude?
A marketing-native connector that holds what the CRM does not: brand voice and offers, the content calendar, campaigns with their pieces, every automation and its plan, and a draft queue. Marqeable’s MCP server does this, syncs audiences from HubSpot, and never sends, so every draft waits for your approval.
The bottom line
The HubSpot connector for Claude is a good CRM connector: fast who questions, small safe writes, read-only marketing data, and no workflow object. Those are limits of what a CRM is, not defects to wait out. The marketing half of your work lives in a different system of record, and Claude needs a connector to that one too: voice and offers, the calendar, campaigns, automations, and a queue where every draft waits for you. Add it beside HubSpot, in the same chat, and the “why can’t Claude draft the nurture” moment goes away.
See the second connector live: Marqeable’s agents build and run your campaigns, run behavior-triggered automations across text and email, answer and qualify every visitor with AI website chat, and tie revenue to the exact message with attribution.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
