How to Use Claude with HubSpot: 4 Quick Wins + Setup

How to Use Claude with HubSpot to Turn CRM Data into Action

If your CRM is just a "dead database," you're leaving revenue on the table. Use Claude with HubSpot to turn CRM data into action: faster work, sharper segmentation, cleaner data, and workflow blueprints — without becoming a full-time HubSpot expert.

Below I walk through the no-code foundations, required permissions, real prompt examples, and guardrails so you can start shipping value today. Whether you run sales, marketing, or RevOps, there is something here for you.

The Full Walkthrough

Here's the full walkthrough video if you're a more visual person.

‍

Why Use Claude with HubSpot (The Practical Case)

Most teams underuse their CRM. Data sits in properties no one reads, contacts go stale, and building a single workflow takes half a day. Claude changes that equation in four ways.

• Speed: Reduce hours of manual work to minutes — draft emails, generate filters, flag bad data. Tasks that used to require toggling between tabs now happen in a single chat window.
• Precision: Get targeted segmentation and focused outputs with fewer UI clicks. Claude can parse your HubSpot schema and recommend the right properties and filters for any segment you describe in plain English.
• Scale: Do the work of multiple admins without adding headcount, especially once you add Claude Code and the HubSpot API later.
• Creative collaboration: Use Claude as a sharp junior operator — give direction, review output, iterate. It surfaces ideas you would not think of because it scans the full schema and recent activity in seconds.

Important note: Claude can be wrong. Treat it like a capable junior you supervise. Always review outputs before acting on them, especially for bulk changes or customer-facing messages.

Three Superpowers Claude Brings to HubSpot

Beyond the day-to-day speed gains, Claude unlocks three strategic advantages that compound over time.

• API and Claude Code potential: The chat connector is just the starting point. Claude Code lets you write scripts against the HubSpot API to create segments programmatically, perform bulk merges, build custom objects, and automate almost anything.
• One-place operations: Instead of hopping between Contacts, Lists, Workflows, and Reports, you run many tasks from the Claude chat interface — pull records, draft follow-ups, flag data issues, all without leaving the conversation.
• Improves with guidance: The more business context you provide — ICP, deal stages, naming conventions — the better Claude performs. Your prompts become a reusable playbook any team member can follow.

Setup: Connect Claude to HubSpot (Non-API Connector)

Getting started takes less than five minutes. Here is what you need and how to install the HubSpot MCP connector for Claude.

Prerequisites

You need super admin or equivalent permissions in HubSpot. Specifically, you need the ability to install and connect marketplace apps. If you are not the portal owner, ask your admin to grant you integration install rights before proceeding.

You also need an active Claude account. The connector works with Claude's chat interface — no API key or developer account is required for this initial setup.

Step-by-Step Installation

Follow these four steps to connect Claude to your HubSpot portal.

1. Navigate to connectors: In HubSpot, go to Settings, then Integrations, then Connectors (or search the Marketplace). Look for the MCP connector category.
2. Install the connector: Search for and install the HubSpot MCP connector for Claude. Click install and authorize access to your portal.
3. Review tool permissions: During setup, you will see options for read, write, and delete permissions. Choose "ask for approval" if you want explicit control over every action Claude takes. Choose "always allow" only if you are precise with your prompts and have rollback plans in place. We recommend starting with "ask for approval" until you are comfortable.
4. Verify the connection: In Claude, enable the HubSpot connector and verify it works by clicking "Add from HubSpot" or trying a simple CRM fetch. A good test prompt is: "Pull the contact record for [your own email address]." If Claude returns your properties and activity, you are connected.

Connector Limits to Know Up Front

The MCP connector is powerful but not unlimited. Knowing the boundaries upfront saves frustration later.

• Cannot access the Leads object: The connector works with contacts, companies, deals, and tickets, but the Leads object is not supported. If your team uses Leads heavily, you will need the API for those records.
• Cannot create quotes, invoices, or HubSpot users: These objects are outside the connector's scope. Creating them requires HubSpot's native UI or the API.
• Cannot delete records: The connector does not support deleting contacts, companies, deals, or any other object. Deletes require the HubSpot API with Claude Code.
• Some actions require the HubSpot API plus Claude Code: Plan API work for deletes, advanced automation, bulk updates, or objects not covered by the connector. The connector is your starting point — the API is your power tool.

4 Quick Wins Using Claude with HubSpot Today

These four use cases require zero code and deliver immediate value from your HubSpot data. Each one includes prompt examples you can copy and adapt right now.

1. Contact Reactivation: Pull Record Activity and Draft Follow-Up Email

Stale leads are money sitting in your CRM waiting to be reactivated. Ask Claude to retrieve a contact's properties and activity, then draft a personalized follow-up.

Prompt example: "Pull activity and property info for john@example.com. Draft a concise, human follow-up to reactivate this stale lead and position our HubSpot admin services."

Another prompt: "Find contacts at example.com who have not been contacted in 60 days. Summarize what we know about each and suggest a re-engagement angle based on their last interaction."

Advanced prompt: "Pull the deal history for john@example.com. If a deal was lost, note the close reason and draft a follow-up that addresses that objection directly."

Options: Open the draft in your email client or ask Claude to sync it as a note on the contact record if it cannot create a sales email directly. You can also ask Claude to adjust the tone — formal for enterprise, casual for startups.

Why it matters: Quick, contextual outreach that saves time and dramatically improves personalization. Instead of a generic "just checking in" email, you send a message rooted in real CRM data.

2. List Segmentation and Filter Ideation

Building smart lists in HubSpot requires knowing which properties exist and how they interact. Claude can scan your schema and suggest exact criteria in seconds.

Prompt example: "Suggest segmentation criteria for a re-engagement campaign targeting non-customers with no activity for 30-plus days and zero open deals."

Another prompt: "I want to find marketing-qualified leads who visited our pricing page in the last 14 days but have no associated deal. What HubSpot properties and filters should I use?"

Advanced prompt: "Audit my current active lists and suggest three new segments I am probably missing based on the properties available in my portal."

Claude will suggest properties like number of associated deals, last activity date, last contacted, lifecycle stage, bounced email exclusions, and created date thresholds. Build the list in HubSpot manually or automate later with Claude Code and the API.

Why it matters: You get smarter segment ideas fast without being a HubSpot wizard. Claude sees your full schema and can suggest combinations you would never think to try on your own.

3. Data Cleanup: Detect Misspelled Email Domains and Suspicious Entries

Bad data silently kills your email deliverability, reporting accuracy, and sales efficiency. Claude can find problems humans miss.

Prompt example: "Extract all contact email domains from my portal and run fuzzy matching to find likely typos like gmal.com, gmial.com, or outlok.com."

Another prompt: "Find contacts with phone numbers that have fewer than 7 digits or contain letters. Flag them for review."

Advanced prompt: "Identify duplicate contacts based on email domain and first name similarity. Group them and suggest which record to keep based on most recent activity."

Claude will flag high-confidence issues and can either suggest fixes or provide direct links to the records in HubSpot for manual merge or deletion if the connector cannot update or delete.

Workflow: Review flagged items, confirm fixes, then merge or update in HubSpot. Use the API later for bulk fixes across hundreds or thousands of records.

Why it matters: Cleaning errors prevents lost emails, improves deliverability, and raises data quality for better reporting. Even fixing 50 misspelled domains can measurably improve your bounce rate.

4. Workflow Blueprinting Before You Build

Building workflows directly in HubSpot's UI without a plan leads to missed edge cases and rework. Ask Claude to map the logic first.

Prompt example: "Build a blueprint to route contacts in the Southeast US to Dan and everyone else to Heather. Include criteria, actions, owners, and test checks."

Another prompt: "Design a lead nurture workflow that sends 3 emails over 10 days after a form submission, with a branch that skips email 2 if the contact opens email 1 and visits the pricing page."

Advanced prompt: "I need a deal stage automation: when a deal moves to 'Negotiation,' assign a task to the deal owner to send a proposal within 48 hours, notify the sales manager, and update a custom property with the proposal deadline date. Map every step."

Claude will return region criteria, owner-finding logic, actions like assign owner and add task and send email, plus edge cases to watch for. Use the blueprint to implement and test the workflow in the HubSpot UI, or automate creation with the API and Claude Code later.

Why it matters: Faster design cycles, fewer mistakes when implementing automation, and a written record of the intended logic that your team can review before anything goes live.

Claude with HubSpot for Different Teams

Different teams get different value from connecting Claude to HubSpot. Here is how each group can use it most effectively.

Sales Teams

Sales reps waste hours researching prospects and writing emails. Claude eliminates that friction. Pull a contact's full history and deal status in one prompt, then have Claude draft a follow-up referencing their last meeting or content they downloaded.

Prompt example: "Pull all activity for jane@bigcorp.com and summarize the relationship in two sentences. Then draft a follow-up referencing our last meeting topic."

Sales managers can use Claude to audit pipeline health — identify deals stuck in a stage for 30-plus days or flag contacts with no activity despite an active deal.

Marketing Teams

Marketers need segments, campaign ideas, and clean data. Claude handles all three. Brainstorm campaign segments based on actual portal data, not guesswork.

Prompt example: "Analyze the distribution of contacts across lifecycle stages. Identify the largest group not in an active campaign and suggest a nurture sequence."

Claude can also write email copy, subject lines, and A/B test variants tailored to the segment you are targeting.

RevOps Teams

RevOps teams are the power users. Claude becomes a Swiss Army knife for auditing data quality, mapping process improvements, and documenting your HubSpot setup.

Prompt example: "Audit my deal pipeline and flag stages where more than 20 percent of deals have been sitting for over 60 days. Suggest process changes."

RevOps can also generate workflow documentation, create runbooks, and onboard new team members by having Claude explain how your portal is configured.

Common Mistakes to Avoid with Claude and HubSpot

Even experienced HubSpot users make mistakes when they first start using Claude. Avoid these pitfalls to get better results faster.

• Vague prompts without context: Saying "clean up my data" gives Claude nothing to work with. Specify which objects, which properties, and what "clean" means to you.
• Trusting outputs without review: Claude is confident even when wrong. Always verify that properties and filters it suggests exist in your portal. Spot-check a few records before acting on bulk recommendations.
• Skipping the test step: Never apply suggestions directly to production. Build in a sandbox, run filters on a small sample, or review the first batch before scaling up.
• Ignoring connector limitations: If you ask Claude to delete records or access the Leads object through the connector, it will fail or hallucinate a workaround. Know the boundaries and plan API work for anything outside them.
• Not saving your prompts: Good prompts are reusable assets. Save what works and build a library so your team gets consistent results without reinventing the wheel.
• Bulk changes without a rollback plan: Export affected records before any bulk update. A CSV backup means you can undo mistakes quickly instead of spending hours on manual recovery.

Best Practices and Guardrails for Claude with HubSpot

Following these governance rules keeps your HubSpot data safe while maximizing the value Claude delivers.

• Provide context and constraints in every prompt: Tell Claude about your data model, business goals, and naming conventions. "Segment contacts for a re-engagement campaign targeting mid-market SaaS companies who evaluated us in Q4" produces dramatically better results than "find contacts to email."
• Treat Claude like a supervised junior operator: Give clear direction, review every output, and iterate when needed. The human in the loop is what makes the system reliable.
• Keep human approval for sensitive actions: Deletes, bulk updates, finance-connected flows, and customer-facing messages should always have a review step. Set the connector to "ask for approval" for any action that touches production data.
• Test in a staging or sample environment: HubSpot sandbox accounts exist for a reason. Use a sandbox portal or limit scope to a small sample before applying changes to production.
• Log your prompts and outputs: Keep a shared document recording what you asked, what Claude returned, and what action you took. This audit trail helps reproduce results, onboard team members, and debug issues.
• Establish team-wide prompt standards: When multiple people use Claude with HubSpot, inconsistent prompts lead to inconsistent results. Create a shared library with tested templates for common tasks.
• Review permissions quarterly: As your team evolves, revisit connector permissions. Remove write access for read-only users and tighten "always allow" back to "ask for approval" when needed.

What to Expect Next (Advanced Options)

The connector-based setup in this guide is just the beginning. Here is what becomes possible as you level up.

• Claude Code plus HubSpot API unlocks full automation: Create segments programmatically, perform bulk merges and updates across thousands of records, build and modify workflows via API, create custom objects, and scale automations that would take days to build manually. Claude Code writes the scripts — you review and run them.
• Custom integrations between HubSpot and other tools: Use Claude Code to build bridges between HubSpot and your other systems — Slack notifications when deals move stages, automatic enrichment from third-party data providers, or syncing HubSpot data with your data warehouse.
• Advanced course from MergeYourData: We are building proprietary methods to enforce orchestration, governance, and revenue operations strategy — paid, gated content for teams wanting production-grade automations. This goes beyond basic prompts into systematic CRM operations powered by Claude.

Key Takeaways: Claude with HubSpot Summary Checklist

Here is your quick-reference checklist for getting started and staying on track with Claude with HubSpot.

• Permissions: Confirm you have super admin or integration install rights in HubSpot before starting.
• Install: Connect the HubSpot MCP connector to Claude through HubSpot's Integrations settings.
• Verify: Test the connection by pulling a known contact record in Claude's chat interface.
• Start with quick wins: Use the four zero-code use cases — email drafts, segmentation criteria, data cleanups, and workflow blueprints — to prove value immediately.
• Save your prompts: Build a reusable prompt library so your team gets consistent results every time.
• Review everything: Never send, update, or delete based on Claude's output without human review first.
• Plan API work: Use Claude Code and the HubSpot API for deletes, bulk updates, or objects not supported by the connector.
• Level up over time: Move from chat-based prompts to Claude Code scripts as your confidence and requirements grow.

Final Take: Shift Your CRM Perspective

CRMs should not be a dead database. Treat them as fuel — data that actively drives revenue, experimentation, and predictable growth.

Claude is a force-multiplier for HubSpot when used with clear prompts, human review, and good governance. Use the chat to shortcut routine tasks and free your team to think strategically. The teams that figure this out now will have a compounding advantage over those still doing everything manually.

Want Help Implementing This?

If you want hands-on help — connectors, data cleanup, workflow builds, or a full revenue operations runbook — book a call at mergeyourdata.com/request-a-consultation. We build, test, and operationalize these methods end-to-end.

Frequently Asked Questions: Claude with HubSpot

Common questions about connecting and using Claude with HubSpot for CRM operations.

Can Claude delete records in HubSpot?

No. The HubSpot MCP connector for Claude does not support deleting records. You need to use the HubSpot API with Claude Code for deletions, bulk updates, or objects not covered by the connector. Always export a backup before performing any bulk deletes via the API.

Do I need coding skills to use Claude with HubSpot?

No coding is required for the connector-based setup described in this guide. The four quick wins — email drafting, segmentation, data cleanup, and workflow blueprinting — all work through Claude's chat interface with plain English prompts. Advanced automations using the HubSpot API and Claude Code do involve some technical setup, but Claude can help you write that code too.

What HubSpot permissions do I need to connect Claude?

You need super admin or equivalent permissions in HubSpot, specifically the ability to install and connect marketplace apps. During setup, you will review and approve tool permissions for read, write, and delete access. If you are not a super admin, ask your portal owner to either grant you the permissions or install the connector on your behalf.

How accurate is Claude when working with HubSpot data?

Claude is highly capable but not infallible. It can misidentify properties, suggest filters that do not match your specific portal configuration, or draft emails that miss important context. Treat every output as a strong first draft that requires human review. The more context you provide in your prompts — your ICP, deal stages, naming conventions — the more accurate the results will be.

Can I use Claude with HubSpot's free plan?

Yes, the MCP connector works with HubSpot's free CRM tier. However, some features Claude might reference — like workflows, custom properties, or advanced list segmentation — require paid HubSpot plans. Claude will still help you draft emails, analyze contact data, and suggest strategies regardless of which HubSpot tier you are on.