Most marketers use an AI assistant at work, but constantly switching between Claude, a CRM, and other apps breaks focus. That is where Claude integrations come in.

Connect HubSpot to Claude For Personalized Insights [Free Connector]

Claude integrations link external tools and services directly to Claude, Anthropic’s AI assistant. The connectors allow Claude to read data and take action on behalf of a user without switching tabs or copying information between apps. Go-to-market (GTM) teams benefit from customer context that enriches responses with specific details rather than generic answers, while governance settings restrict connectors to read-only, approval-required, or blocked actions.

The HubSpot Connector for Claude allows Claude to access HubSpot context, surface opportunities, and take action without switching tools. This article covers how to use Claude connectors, what data Claude can access through connectors, and a roundup of Claude integrations by GTM use case.

Table of Contents

• What are Claude connectors and how do they work?
• How Claude Connects to CRM Data Securely
• Best Claude Integrations by GTM Use Case
• What Data Claude Can Access Through Connectors
• How to Evaluate a Claude Integration
• Where the HubSpot Connector For Claude Fits
• Frequently Asked Questions About Claude Integrations
• Doing More With Claude Integrations

What are Claude connectors and how do they work?

Claude connectors bridge Claude and the tools that marketers, RevOps teams, and GTM leaders already use. Common examples include CRMs, project trackers, and calendars. When a connector is active, Claude can read data from those tools and take action inside them without the user leaving the Claude interface.

Developers build Claude connectors on the Model Context Protocol (MCP), a standard that lets Claude discover and call tools the way a browser calls an API. No code or endpoint configuration is required on the user’s side. Claude identifies available connectors, selects the right one for the task, and automatically passes the request through.

Once a user connects an app, Claude can read from it, write to it, or both, depending on what that app exposes. The key design principle is that Claude inherits the user’s existing permissions. If a user can see a deal and engagement records in HubSpot, Claude can see them too. If a user cannot access a particular ticket queue in Zendesk, Claude cannot either. Claude integrations have no separate elevated-access or privilege-escalation path.

Every action Claude takes is logged and can be audited against the user’s account. The practical result is that users eliminate manual copy-pasting between tools.

For example, marketing teams don’t need to pull a call transcript from an app, open a CRM, draft an email, and then update the deal stage. Instead, team members can describe the outcome they want, and Claude handles the multi-step sequence using the context it has access to.

Pro tip: For a comprehensive guide to using connectors to extend Claude’s capabilities, check out our connector best practices.

How Claude Connects to CRM Data Securely

Claude connectors securely connect to CRM data through three distinct processes:

• Permission inheritance. When users connect a CRM like HubSpot to Claude, the connector uses per-user delegated OAuth. Claude integrations do not have their own login or a service account with broad access. The connectors operate through an existing session, inheriting exactly the permissions the user already has in that CRM. If a user cannot see a particular account or field due to pre-existing permission sets, field-level security, or sharing rules, Claude cannot either.
• Org enablement. Organizations on Enterprise plans can enable Claude connectors directly from Settings. As of August 2026, Anthropic’s Enterprise-managed authorization allows admins to centrally provide connector access through the organization’s identity provider. Once admins enable connectors and map them to existing groups and roles, employees inherit the connection automatically on first login — no individual consent screens or per-user OAuth prompts required.
• Action restrictions. Beyond authentication, admins can control what Claude integrations do with the data. Per-tool permissions let users grant read-only access to one object while blocking writes to another. Admins can also disable specific tool calls from the same settings panel where connectors are enabled. Enterprise-managed auth supports an identity provider-only authentication requirement, which prevents employees from accidentally linking personal accounts to work-related CRM instances.

In addition to permission-based accessibility, organizational-level tool enabling, and task-specific restrictions, CRM contexts provide the specific data Claude needs to generate useful answers.

For example, a sales rep can ask “what’s the last thing this specific account said before their renewal?” The rep will get correct answers only if Claude integrations can pull the relevant call notes, ticket history, and deal stage in one pass.

Without context, Claude either guesses or asks users to paste data manually. Manual data handling defeats the purpose of using connectors and creates data integration problems. Claude’s security model makes CRM context available without compromising sensitive customer data. The same guardrails the CRM already enforces govern what Claude can see and do on a user’s behalf.

Best Claude Integrations by GTM Use Case

Best for Marketing and Campaign Work

1. The HubSpot Connector for Claude

The HubSpot Connector for Claude helps marketing teams with end-to-end campaign workflows. The connector creates and updates landing pages, drafts marketing emails, checks webpage performance, builds marketing campaigns, and sets up customer registration tracking.

Source

A marketer can ask Claude to find contacts who opened a recent email campaign but didn’t click through, and generate a segmentation chart to inform follow-up targeting. Moreover, marketing teams can also use Claude connectors with relevant customer context to help generate meaningful content that speaks directly to consumers.

How Experts Use the HubSpot Connector in Marketing

Kipp Bodnar, chief marketing officer at HubSpot, has earlier said, “One of the things we love about Claude is that it has really good taste, and marketing’s all about taste.” Bodnar believes that the Claude models are highly capable at writing prose. Consequently, marketing teams have reported a 40% increase in productivity across web development and content creation workflows while using Claude integrations.

2. Canva

Canva lets Claude integrations generate, edit, and export on-brand designs directly from chat to create social posts, presentations, infographics, and ad creatives. With Canva’s Claude connectors, teams can automatically apply a brand kit (colors, fonts, logos) via a natural language prompt, ensuring every asset looks consistent without manual formatting.

For example, a brand marketer can ask Claude to “create a 3-slide Canva presentation for our Q3 product launch.” Claude pulls the brand kit, generates all three slides, and returns a downloadable file without any Canva login or manual template hunting.

How Experts Use Canva’s Claude Integrations

Mejba Ahmed, who builds AI applications and has 10+ years of experience shipping production software in Laravel, Python, and AWS, often uses Canva’s Anthropic connectors. He writes, “Where Claude clearly beats Canva’s built-in Magic Write is the content layer itself. Ask Canva’s AI for a carousel on AI tools and every tool is ‘revolutionary.’ Claude writes copy with actual comparisons and trade-offs in it, because it knows the subject matter. That content gap, more than the visual generation, is why this pairing is worth configuring.”

3. Zapier

Zapier helps marketing teams to orchestrate multi-app workflows with Claude integrations. Teams can send an email, post on social media, update a CRM record, and notify Slack, all from a single prompt in Claude. Team members don’t need to build separate workflows or Zaps for each task.

A content marketer can ask Claude: “For every new blog post published in WordPress, generate a 120-character X post, then schedule the post via Buffer.” Claude queries WordPress for new posts, drafts a format, and calls Buffer to schedule. Everything happens with one prompt without involving any manual copy-paste between tabs.

How Experts Use Zapier’s Claude Integrations

Zapier’s own employees use Claude with an 89% adoption rate and 10x year-over-year growth in Anthropic’s app usage. Reid Robinson, Lead Product Manager of AI at Zapier, said, “Zapier, at its core, is about enabling non-technical people to build things they didn’t think possible.”

With Zapier’s Claude integrations, product marketing teams can create customer-facing content, and design teams can use Claude to prototype, showing design concepts that would otherwise take weeks.

Best for Sales and Pipeline Workflows

4. The HubSpot Connector for Claude

The HubSpot connector for Claude gives sales teams pipeline visibility without opening the CRM. Team members can use the connector to get pipeline summaries, pre-call briefs from engagement history, and alerts on stale deals. Post-call, Claude can update lead status, log notes, and create or manage quotes.

A sales team member can ask Claude for a summary of active deals organized by name, amount, stage, and closing date to prioritize the week’s outreach. Claude will access HubSpot context to fetch deal and engagement records and provide the information to the team member.

How Experts Use the HubSpot Connector in Sales

Sarah Caruthers, senior customer success manager at HubSpot, explained how the lack of good Claude connectors can be a problem for the sales team. Sarah said, “I could be the best CSM … but without that handholding or accountability, I never saw the follow-through … Claude gives me the support and time to be a more strategic partner for my customers”.

5. Apollo.io

Apollo helps sales teams search for B2B contacts, create or update contacts, and manage sequences through its Claude integrations.

For example, an account executive preparing for a call can ask Claude to summarize what Apollo knows about the company, headcount changes, funding history, technologies in use, and cross-reference it against the contacts already in the deal record.

6. Zendesk

Sales teams use Zendesk’s Claude integrations to create, update, and manage support tickets without leaving Claude. The connector also supports posting replies, assigning tickets, and querying user and organization records.

For sales teams, the value of Anthropic connectors lies in support ticket data. Churn signals, product escalations, and deal-blocking issues surface directly in Claude without asking support to pull up a thread.

Best for Customer Success and Support Context

7. The HubSpot Connector for Claude

The HubSpot Connector for Claude helps customer success teams surface stale accounts and map engagement history for top accounts. The connector surfaces contacts with overdue invoices, provides pre-call interaction summaries, and opens tickets by priority. Teams can also access full conversation history across connected channels and analyze resolution patterns without leaving Claude.

Support reps can ask Claude to compare resolution approaches across channels to identify gaps in consistency, or pull all open tickets, sorted by priority and creation date, without navigating the help desk interface.

How Experts Use the HubSpot Connector

Chris Rule, vice president of customer experience at Turno, one of the largest short-term rental cleaning marketplaces, mentioned how the company extensively uses the HubSpot Connector for Claude. Chris said, “We were spending a lot of human time getting in front of people who were not the right people to be talking to at the right times.”

However, by connecting Claude with HubSpot, Chris’ team could ask questions about CRM records and get personalized insights. The Claude connectors helped with reading sentiment in NPS text, identifying revenue segments, and surfacing customers whose combined picture warranted attention.

With the adoption of Claude integrations, Turno’s net revenue retention for mid-market and enterprise hosts climbed by 30%. Simultaneously, conversion rates jumped 5 percentage points.

Source

8. Intercom

Intercom gives Claude access to customer profiles, support conversations, and Help Center articles via integrations. However, Intercom’s Claude connectors are read-only, which means Claude can pull and analyze threads but cannot reply, reassign, tag, or close conversations.

For customer success and support teams, the value of Intercom’s Anthropic connectors is turning an Intercom queue into a queryable intelligence layer. The connectors surface churn signals, recurring product issues, and account health patterns that would otherwise require manually scrolling through hundreds of threads.

How Experts Use Intercom’s Claude Integrations

Fergal Reid, vice president of AI at Intercom, explained, “Customer support is very expensive to deliver … Support reps spend a lot of time searching for authoritative answers, even for questions they’ve seen before.” Claude consistently outperformed other AI models for customer answers.

Reid said, “We switched to Anthropic because its Claude models are the best at providing high-quality answers to our customers at scale.” Intercom’s Fin achieves a 51% resolution rate out of the box, before any customization or tuning.

9. Salesforce

Claude integrations allow Salesforce data to work within Claude, governed by existing permissions. Claude can query across open cases, past interactions, renewal dates, support tiers, and linked opportunities in a single prompt. Claude’s ability to surface account-level context with a single prompt removes the need to navigate multiple tabs in the CRM.

How Experts Use Salesforce’s Claude Integrations

Danny Teng, co-founder and CEO of Modelit, connected Claude to his own production Salesforce org. He finds the integration helpful for publishing case studies.

Writing a case study used to mean opening Google Drive for project briefs, Jira for delivery history, Notion for customer voice, and Salesforce to update the account record. Claude can now pull from all of them in a single conversation. It can also write structured updates back to Salesforce custom fields, including case study URL, outcome summary, and key metrics.

Best for Cross-Functional Productivity

10. The HubSpot Connector for Claude

The HubSpot connector for Claude audits CRM data quality, logs activity from email and calendar, and creates reminder tasks, helping with overall team productivity.

Customer-facing teams can ask Claude to keep records up to date, log a call, or update a deal. The Connector ensures secure, permission-based access for all actions, so that team members and Claude can see only what they’re authorized to view across the platforms.

How Experts Use the Connector’s Claude Integrations

Elaine Zelby, co-founder of Tofu and former marketer, built an agent that pulls data from HubSpot Smart CRM and identifies ten lookalike companies based on deal attributes and ICP definition. For each company, Clay surfaces three to five contacts. Claude then drafts email sequences and sends them to Slack for team review, replacing a workflow that previously required switching between four separate tools.

Source

11. Slack

Claude integrations with Slack help teams search channels and threads, read messages and files, post and schedule messages, and create or update Canvas documents. Slack is where decisions actually happen, but important information gets lost across multiple channels and threads.

Slack’s Claude AI integrations pull context from any channel, synthesize it, and post output. Cross-functional customer-facing teams can thus turn Slack into a queryable, summarizable knowledge base with inherited workspace permissions.

Source

A RevOps lead can ask Claude to, “Read the last 7 days of messages in #deal-desk, #product-escalations, and #marketing-ops, then create a Slack Canvas.” Claude will read all three channels, extract and categorize items, write the Canvas, and drop the link.

Source

How Experts Use Slack’s Claude Integrations

Angelina Popovic, content and SEO manager at HeyReach, said Slack is one of the top three Claude connectors her company runs for daily work. Popovic said, “We mostly use Slack for competitor analysis. We’ve got channels tracking what competitors are shipping and saying, and it’s faster to have Claude dig through that than to scroll Slack channels manually.”

12. Notion

Notion’s Claude integrations allow marketing and customer-facing teams to search, read, create, and update pages and databases across the workspace. Teams use Notion as a shared resource for product notes, briefs, and roadmaps, and Claude can pull context from any of those sources and write structured outputs back.

A GTM lead can ask Claude to read a product launch brief and an ICP update from separate workspaces, then create a new campaign brief in the marketing workspace. Claude reads both pages, synthesizes the overlap, and writes the structured brief without the user switching tools.

How I use Notion’s Claude integrations

As a marketer, I often work with influencers. At first, I focused on only one platform: X. However, when the pilot campaign was successful, the client wanted to expand to other platforms, such as Instagram and TikTok.

Manually checking whether our existing creators were on other platforms would have taken hours. So, I gave it to Claude.

Claude checked each name across platforms, then wrote the results back into our Notion database as structured records through the integration.

What Data Claude Can Access Through Connectors

Claude can only access data that connected apps expose, users permit it to see, or organizations allow access to.

• Connected apps: Connectors can expose tools with a specific set of read and write instructions. If connectors don’t expose the data, Claude can’t access it.

For example, CRM Claude connectors might expose “get deal,” “update stage,” and “create task,” but not “export all contacts.” Similarly, help-desk connectors might return ticket summaries and CSAT scores but not raw PII fields.

• User permissions: Claude connectors use per-user delegated OAuth, meaning Claude operates through users’ existing sessions and inherits access to the source system.

If a user can’t see a particular account in Salesforce or a private Slack channel, Claude can’t either. For customer-facing teams, a sales rep and VP of Sales connecting to the same CRM will get different answers from the same question.

• Org-level restrictions: Organizations with Enterprise plans can control which Claude connectors are available to the org and disable specific tool calls.

For example, Enterprise-managed auth maps connectors to specific roles. So a new hire inherits only what their role entitles them to, and a deprovisioned employee automatically loses access. Similarly, organizations can block write actions while keeping reads open, depending on their requirements.

How to Evaluate a Claude Integration

Before adding Claude integrations to the tech stack, six questions help separate useful tools from ones that add complexity without value.

• Workflow fit: Does the integration replace a specific task the team already does manually? If the team cannot name what Claude connectors replace, the tool is a nice-to-have rather than a critical workflow component.
• Permissions: Do the integrations inherit existing role-based access, or do they require a shared service account? Shared accounts create permission blind spots that surface in the first audit.
• Approval controls: Can write actions be gated with human-in-the-loop approval, or restricted to read-only? Automatic actions with no review step trade speed for governance risk.
• Reporting value: Do the connectors produce a measurable output — saved steps per rep, faster cycle times, or cleaner audit trails? Without a number that moves, the value is difficult to defend.
• Setup effort: How long does it take from connecting the integration to a teammate using it in their daily workflow? Integrations that require a custom MCP server or significant technical knowledge tend to cost more in adoption than they save in time.
• Day-to-day usefulness: Do reps stop thinking about “asking Claude” and simply get the answer where they are already working? The best integrations disappear into the workflow and get used voluntarily after the pilot stage

Where the HubSpot Connector For Claude Fits

The HubSpot Connector for Claude brings each team’s HubSpot context directly into Claude. Contacts and history, deal and engagement records, and company information are all accessible in plain language without switching tools. Users can ask questions, generate visualizations like charts and graphs, and act on insights without leaving their workflow.

When Claude is connected to HubSpot Smart CRM, it surfaces real-time records including contacts, deals, companies, and tickets. Answers are grounded in actual business context rather than generic AI responses. Claude can also use HubSpot’s Reporting Dashboards to generate on-demand pipeline summaries, deal stage breakdowns, and campaign performance data directly in a conversation.

The connector works in Claude’s desktop and web interfaces but not on mobile. A paid Claude subscription (Pro, Max, Team, or Enterprise) and an active HubSpot account at any edition are required.

Claude respects HubSpot’s existing user permissions — a sales rep only sees pipeline data for deals they have permission to view. CRM access controls automatically carry over to Claude. Claude can create and update records through supported connectors but cannot delete HubSpot records. Anthropic does not use data shared through HubSpot to train its models unless the user opts in.

Frequently Asked Questions About Claude Integrations

Can I connect Claude to HubSpot securely?

Yes, customer-facing teams can securely connect Claude to HubSpot. Claude receives only the access a user explicitly authorizes, and it can’t see or act on data users themselves don’t have permission to view. Moreover, all actions taken through the HubSpot Connector are logged in HubSpot’s audit log, with attribution to both the user and the Claude connector.

What can Claude create or update through a connector?

Claude can create and update CRM records (contacts, companies, and deals) and log activities (notes, calls, tasks, and follow-ups) through a connector. Claude can also move deals through pipeline stages, retrieve and search records, pull pipeline summaries, and generate insights from engagement history (emails, calls, meetings). Users simply need to integrate the Claude connectors and access the information through natural language queries.

How should teams handle sensitive workflows with connectors?

Teams should handle sensitive workflows with connectors through role-based access control to grant access only to the roles that need it. Teams must maintain an admin-managed allowlist to disable unapproved Anthropic connectors. Claude integrations inherit whatever each user can already access in the source system. So users must fix oversharing in their CRM or other tools before enabling the connector.

When does a custom connector make sense?

A custom connector makes sense when no official Claude connector covers that use case. Connecting Claude to a proprietary internal tool or a niche SaaS that hasn’t shipped an MCP server requires custom connectors. Customizations become necessary for finer controls that directory connectors don’t offer, such as scoping access to specific boards or data subsets, and custom response formatting.

Doing More With Claude Integrations

Claude connectors give marketing and RevOps teams a natural-language layer on top of their existing stack. The result is faster access to customer context without switching tabs or copying data between tools.

The HubSpot connector for Claude surfaces contacts, deals, companies, and tickets from Smart CRM inside a Claude conversation, so pipeline questions get answered against real records.