Hubspot Release Notes

All Hubspot Release Notes (64)

• Jan 20, 2026

  • Parsed from source:
    Jan 20, 2026
  • Detected by Releasebot:
    Jan 21, 2026
  

  Hubspot Developers by Hubspot

  Public Beta: Self-Service MCP Auth Apps for the HubSpot Remote MCP Server

  HubSpot unveils a self‑service MCP Auth Apps UI that lets partners and customers build, manage, and authorize AI connectors to the HubSpot Remote MCP Server. The beta enables full connector lifecycle control and OAuth 2.1 credentials with automatic end‑user permissions.

  Ecosystem partners and customers can now build and manage their own AI connectors to the (Beta) HubSpot Remote MCP (Model Context Protocol) Server through a streamlined self-service interface. This public beta builds on the initial release of the HubSpot Remote MCP Server and simplifies the experience of creating and managing AI connectors directly.

  What’s Changing?

  A new MCP Auth Apps UI has been added to the HubSpot Developer Platform to allow ecosystem partners and customers to build and manage their own AI connectors to the HubSpot Remote MCP Server through a streamlined and fully self-service experience.

  An earlier public beta, released on September 1, 2025, introduced the HubSpot Remote MCP Server available across all hubs and tiers. However, connector creation and management still relied on other platform developer tools intended for apps providing more functionality in HubSpot.

  With this update, partners and customers can independently manage the full connector lifecycle using the new UI, including:

  • A dedicated MCP Auth Apps section in the HubSpot Developer Platform
  • Creating new MCP connectors through a self-service interface
  • Modifying and maintaining connector settings through the UI
  • Securely access their OAuth 2.1 credentials for integrating external systems with the HubSpot Remote MCP Server

  End-user installation permissions for these apps are now managed automatically, giving customers full control over what HubSpot data they share via the MCP server connection without requiring partners to manually configure or manage permissions.

  For implementation details, see the developer documentation.

  When is it happening?

  • The initial public beta for the HubSpot Remote MCP Server went live on September 1, 2025.
  • A new public beta for self-service connector creation and management using the MCP Auth Apps UI for ecosystem partners and customers went live on January 13, 2026.

  Questions or comments? Join us in the developer forums.

  Original source Report a problem

  Show more
• Jan 8, 2026

  • Parsed from source:
    Jan 8, 2026
  • Detected by Releasebot:
    Jan 9, 2026
  

  Hubspot

  New HubSpot App Updates: AI, Automation & CRM Sync (Q4 2025)

  HubSpot Marketplace closes Q4 with 76+ new apps and a wave of updates that slash silos and boost productivity. New AI tools and CRM integrations with Claude and ChatGPT unlock faster prospecting, dynamic docs, and richer dashboards for smarter, faster selling.

  App Theme #1: Choose Connection Over Silos

  Perhaps the strongest move you can make in 2026 is to insist on a single source of truth. The unnecessary friction caused by disconnected platforms, ends here.

  Check out these notable new or recently updated apps:

  • [NEW] HubSpot Connector for Claude now creates and updates CRM records and log activities (engagements) directly from Claude’s chat window, including new contact and deal creation, and log notes or tasks - now available in public beta.
  • [NEW] HubSpot Connector for ChatGPT is now available in the HubSpot Marketplace. Use chat to ask everyday questions like “List deals closing this month by deal size” or switch to deep research for multi-step analyses that synthesize trends, segment cohorts, and return source-backed insights with citations that link directly to HubSpot records.
  • Descript is now bidirectional for fewer silos. Export edited videos from Descript to HubSpot video libraries, and send HubSpot videos to Descript for editing workflows.
  • Google Meet now has a redesigned global advanced settings page, providing admins with centralized control over syncing meeting recordings and transcriptions for relevant users and teams across the organization, ensuring that critical meeting intelligence is automatically synced to HubSpot.
  • Salesforce now automatically syncs owner data for activities, tickets, and custom objects. When a record changes hands in one system, the ownership is reflected in the other automatically.
  • NetSuite now automatically associates HubSpot deals with their corresponding NetSuite sales orders upon creation, providing teams with a more reliable source of truth.
  • Clear Sync has expanded app access to more plans and customers. This update allows teams to sync Stripe MRR data directly into HubSpot to track product performance, run upsell campaigns, drive sales rep commissions, see MRR over time per customer, and more.
  • Webflow has rebuilt their app and introduced flexible new form integration options, including native form mapping, iframe embeds, and developer code embeds (note that advanced styling requires a HubSpot Marketing Professional or Enterprise plan). You can also enable HubSpot chatbots and site tracking to monitor visitor behavior.

  App Theme #2: Let Go of the Manual Grind

  Creating space for deeper, more meaningful work that fuels creativity, strategy, and connection starts with the courage to let go of the “heavy lifting” that keeps us small: the list syncing, document chasing, and tab juggling that no longer serve us.

  Check out these notable new or recently updated apps:

  • [NEW] Vidyard Video Agent is a new app that auto-generates AI videos for prospecting, meeting reminders, onboarding and more with HubSpot workflow triggers. Create personalized video messages using CRM data and send them automatically based on prospect actions, meeting schedules, or pipeline stage changes.
  • event hapily has a new event builder that reduces the time to launch an event from days to minutes, while preventing erroneous data entry through automation. Instantly generate lists (registered, attended, event leads, cancellations, and No Shows), create a landing page, registration form, confirmation email, HubSpot campaign, and Zoom meeting/webinar - all from a single form.
  • Livestorm Webinars now syncs webinar registration and attendance data into HubSpot using native Marketing Events. Trigger workflows based on engagement data and analyze webinar performance directly in your CRM so you can qualify leads and report on webinar ROI more efficiently.
  • Create Google Docs/PDF + eSign now supports custom app objects (“Portant Documents”) and Microsoft 365, enabling teams to generate dynamic proposals and manage the full contract lifecycle directly within HubSpot. The update allows for automated e-signatures, real-time engagement tracking via UI extension cards, and the ability to trigger workflows using document metadata like views or signatures.
  • CloudFiles now offers a new plan for linking files and folders from Google Drive, SharePoint, OneDrive, and AWS to HubSpot records. Manage documents directly in HubSpot including renaming, moving, deleting, and replacing files without leaving HubSpot.
  • S-Docs now generates documents using data from Google Sheets, Airtable, and other external sources. Create documents directly from more data sources within HubSpot workflows so you can work with fewer silos.
  • Box Connector now integrates Box AI functions into HubSpot workflows, enabling automatic file naming and the extraction of structured and unstructured metadata into HubSpot properties and Box metadata reducing manual data entry and file organization efforts. A new HubSpot CMS module has also been introduced to allow for secure document sharing through Box.
  • Zapier has added 16 additional supported CRM objects including invoices, subscriptions, leads, projects, and more. This update allows teams to use Zapier actions across a much broader data set, including commerce and service-specific records.

  App Theme #3: Show Up with Deeper Presence

  True velocity in 2026 comes not only from moving with urgency, but from finding clarity in the moment. When the ecosystem meets us where we work, teams gain the context to lead with both heart and data.

  Check out these notable new or recently updated apps:

  • Slack now has context-rich record unfurling, transforming links to HubSpot records into interactive, structured previews. Key metadata (such as deal stages, ticket priorities, or contact details) is automatically displayed directly in Slack.
  • Arrows now supports HubSpot's project object to link customer onboarding plans with native tasks and Gantt charts. Trigger HubSpot workflows, reports, and journeys from Arrows activity including workspace views and task completions. View Arrows sales room engagement with new UIE cards in the HubSpot middle pane across Deals, Tickets, Services, and Custom Objects.
  • Salesmsg SMS Texting & Calling has extended the functionality of the Salesmsg app card. With this update, reps can now send 1:1 SMS messages from any inbox, enroll contacts into automation, access AI-suggested messages, and take Power Dialer actions directly from HubSpot contact records. New calling insight cards enable real-time note-taking and call categorization within the HubSpot interface, while enhanced workflow tracking provides more visibility into engagement so you can refine your messaging.
  • Sinch Engage SMS now offers sending Rich Communication Services (RCS) messages from HubSpot workflows with verified sender profiles, read receipts, and rich media including interactive carousels, videos, and smart buttons. Track message opens, clicks, and replies in HubSpot contact records and use engagement data to trigger follow-up workflows.
  • Supered now supports HubSpot’s object library and has introduced new process boards with shareable analytics that embed directly into HubSpot reports. Embedded cards within text areas and input fields can be triggered when rule requirements are not met, ensuring process guidance appears naturally where reps enter data. These updates provide real-time visibility into process compliance so teams can move faster and with more confidence.
  • Microsoft Teams has launched a new guided onboarding experience, accessible directly from the integration settings page. This update features a grouped checklist and an interactive activation tour to help admins configure, verify, and maximize the value of their app with less guesswork.
  • Zendesk now syncs back-and-forth ticket conversation history from Zendesk to HubSpot so agents have more context.

  The Takeaway: From Hustle to Velocity

  The updates shipped last quarter collectively invite us to pursue more meaningful execution. Install new apps that integrate seamlessly with HubSpot to handle the how, so you can refocus on the why. Make this the year you expand your capacity, elevate your impact, and lead with clarity in every action.

  Ready to Transform?

  1. Navigate to the HubSpot Marketplace from your account.
  2. Explore the featured apps and review their compatibility.
  3. Install and configure your selected tools (requires Super Admin or App Marketplace permissions).

  Which of these updates are you most excited about? Let us know in the comments below.

  Original source Report a problem

  Show more
• Jan 6, 2026

  • Parsed from source:
    Jan 6, 2026
  • Detected by Releasebot:
    Jan 7, 2026
  

  Hubspot Developers by Hubspot

  December 2025 Developer Rollup

  HubSpot rolls out a wave of developer and security updates including GA for the App Uninstallation API, a dynamic IP Ranges API, CPQ template control, migration insights, and a refreshed Standard Sandbox with new limits and deploys. Plus new migration tools and event data queries enhance platform leverage.

  This month’s updates focus on enhancing developer workflows and platform security, featuring a new IP Ranges API for firewall management and the general availability of the App Uninstallation API. We’ve also introduced several quality-of-life improvements, including a Legacy CRM Card Converter to assist in your migration to modern App Cards, setting a custom template for CPQ quotes, actionable migration insights directly within your HubSpot Account, and expanded Breeze Assistant capabilities for custom website and app event data. Finally, wer'e making significant updates to the standard sandbox experience that bring predictable record limits and new deployment capabilities.

  New Resource: Legacy CRM Card Converter

  To support developers migrating from Classic CRM Cards to the new App Cards, we’ve released the Legacy CRM Card Converter, a lightweight tool and example designed to simplify the transition process. The resource provides:

  • Sample mappings that demonstrate how Classic CRM Card patterns translate to modern App Cards.
  • Reference implementation to help you quickly understand equivalent React-based structures.
  • Guidance and best practices for updating legacy cards to transition to new UI Extension capabilities.

  The card converter is intended to accelerate planning and development as you prepare for the October 31st, 2026, sunset of Classic CRM Cards. Explore the tool here: https://github.com/HubSpot/ui-extensions-examples/tree/main/legacy-card-converter

  Developer Tasks and App Migration Paths

  Now the Developer Platform surfaces actionable insights directly on the Developer Overview for all HubSpot Accounts. Developers can view task cards highlighting whether any of their apps are eligible for migration to the new Developer Platform, with clear guidance on which apps can and cannot be migrated.

  • Task Cards: A task card lists action items for developers, focusing on highlighting eligible apps for migration. A task card can be found on the Developer Overview page within the HubSpot Account.
  • Migration Eligibility Labels: Each app is now labeled as ‘Yes’ (can be migrated) or ‘No’ (should not be migrated). When migration steps are available, developers will be directed to the Legacy Apps page within your HubSpot Account.

  Previously, the Developer Overview lacked actionable next steps, leaving users uncertain how to maintain or upgrade their apps. These new insights enable clear, actionable guidance, reducing mistakes and improving the migration experience. For additional guidance, refer to the Developer Platform documentation on app migration guides.

  HubSpot IP Ranges API

  You can now dynamically access HubSpot's public IP ranges for your projects and firewalls. With this API, you can automatically update your firewall rules and enhance your security monitoring. You can retrieve the set of IP ranges using this endpoint:
  https://api.hubapi.com/meta/network-origins/2025-09/ip-ranges
  This API does not require authorization. The response will include a list of IP ranges and the HubSpot services using those IPs. See the documentation for full details.

  New Filter by Object Type ID for v3 Lists API

  The /crm/v3/lists/search endpoint in the v3 Lists API now supports filtering lists by object type using the objectTypeId parameter in the POST request body. See additional details on what specifically changed, below:

  • New Filter Option: Developers can now include the objectTypeId property in the POST request body when querying the /crm/v3/lists/search API endpoint.
  • Supported Values: Common values include object type IDs, such as "0-1", or a string, such as "CONTACT".
  • Request Body Example:

  {
    "query": "HubSpot",
    "processingTypes": ["MANUAL"],
    "objectTypeId": "0-1"  // "CONTACT" also works
  }
  

  This new feature enhances list segmentation by allowing filtering of lists by HubSpot CRM object type. Applicable to CRM segments (part of Lists), especially for Marketing Hub and Main Hub products. Additionally, this change enables tighter integration for custom reporting and workflow automation with more granular access when programmatically dealing with lists for marketing and CRM operations.

  Template Selection for CPQ Quotes via API

  You can now specify a custom template when creating CPQ quotes through the Quotes API, rather than relying on the default content template. This unlocks full control over quote design and structure for any workflow that programmatically generates quotes. During creation, the API will associate the quote to the selected template and pull in any additional template data, while still prioritizing values explicitly set on the quote. Note that templates can only be chosen at creation time and cannot be changed after the quote is generated. Learn more in the Quotes API documentation.

  Standard Sandbox Updates: New Limits, New Capabilities, and Legacy Sunset

  HubSpot is rolling out a more powerful Standard Sandbox experience, alongside clearer data limits and a planned sunset of Legacy Standard Sandboxes.

  • All sandboxes will now enforce a consistent limit of 200,000 records per major CRM object type (including contacts, companies, deals, tickets, custom objects, and more), ensuring predictable performance and stable testing environments.
  • In parallel, a new Standard Sandbox version introduces an enhanced copy of supported production metadata and a Deploy to Production feature for eligible assets, enabling teams to safely test and then natively deploy schema changes, workflows, lists, forms, and automated emails.
  • To support this upgrade, Legacy Standard Sandboxes will be sunset on March 16, 2026, fully replaced by the new Standard Sandbox. Super Admins can create the new sandbox now, with temporary sandbox limit increases available to ease migration; no action is required until the sunset date, but customers with connected apps or complex automations should plan ahead. Learn more in the Sandbox FAQ and documentation. Read more regarding the sunset on the dedicated changelog post which includes helpful FAQs.

  Public API for Uninstalling an app released to GA

  The previously announced API for uninstalling an app from a HubSpot Account has been released from beta into general availability. This endpoint allows app builders to remove their app from a HubSpot Account, which removes any app features set up for the app, including removing any configured app cards, as well as unsubscribing any configured webhooks for that account. See the documentation for more details.

  Updates to associations to the Cart object

  You can now create associations between carts and custom objects, and configure custom association labels and limits for the cart object. This improvement allows you to tailor the cart object to your specific business needs and workflows. This update allows integrations to update associations using the Associations API, as well as allowing super admin users to update associations by editing the data model in their account. Additionally, users can associate carts to deals directly from record pages in HubSpot.

  Breeze Assistant can now query your Custom event and App event data

  Breeze Assistant can now query the custom website events and app events you've configured in your HubSpot Account. You can now get answers about these events directly from Breeze Assistant, helping you:

  • Gain deeper insights into user behavior on your website and through your apps.
  • Make data-driven decisions based on specific actions your customers are taking.
  • Streamline your ability to answer important questions about your business using these additional data sources.
    This enhancement brings you closer to having a comprehensive view of all your HubSpot data through Breeze Assistant. No additional setup is required to enable this functionality. Once you've configured these events in your HubSpot Account, you can ask Breeze Assistant questions about your custom website or app events.

  Questions or comments?

  Please join us in our developer forums.

  Original source Report a problem

  Show more
• Dec 19, 2025

  • Parsed from source:
    Dec 19, 2025
  • Detected by Releasebot:
    Dec 20, 2025
  

  Hubspot Developers by Hubspot

  Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

  Introducing the enhanced Standard Sandbox with Deploy to Production for safer, production-like testing. Legacy sandboxes sunset March 16, 2026, with a guided migration and governance framework to reconnect apps and ensure a smooth transition.

  What This Means for You

  To support this change, your sandbox limit will be temporarily increased so you can create and configure a new standard sandbox while still accessing your legacy sandbox.

  • Most customers will experience minimal impact.
  • Teams with connected apps that orchestrates data flow across systems may need to review and reconnect certain elements in the new sandbox.

  The new standard sandbox includes:

  • A more accurate representation of the most requested supported asset types
  • A new Deploy to Production feature for supported asset types

  FAQ — What You Need to Do Before March 16, 2026

  Who can make these changes

  Any Super Admin can create a new standard sandbox and delete the legacy one. We recommend coordinating with the Super Admins who actively use sandboxes and maintain integrations to assess the requirements.
  If you have questions not answered in this FAQ please reach out to your Customer Success Manager or visit the HubSpot Help Center.

  How to assess your migration needs

  1. Create your new Standard Sandbox
     Your temporary sandbox limit allows you to create it without deleting your legacy sandbox.

  2. Review whats in your Legacy Sandbox
     Identify any integrations, apps, or automations your tech stack depends on, for example:

  • Connected private or public apps
  • Workflows that send data externally through webhooks
  • Custom-coded workflow actions

  1. Recreate or reconnect what you need
     If you use integrations or apps, you may need to:

  • Reconnect private and public apps
  • Update authentication or secrets in integrations settings and workflows with webhooks

  1. Validate your setup in the new sandbox
     Ensure integrations, authentication, and any data-flow-related logic are functioning correctly by comparing them against your legacy sandbox or requirement documentation.

  2. Delete your Legacy Sandbox
     Once your new sandbox is fully operational, delete the legacy sandbox. Your temporary sandbox limit increase will be removed.

  What happens to legacy sandboxes on March 16, 2026

  If you don’t migrate before March 16, you will lose access to your legacy sandboxes. After that date, only the new Standard Sandbox will be supported.

  Who Is Impacted

  Most Customers (Simple Testing Use Cases)

  Most teams will experience minimal impact and can simply:

  1. Create a new standard sandbox
  2. Confirm no migration needs exist
  3. Delete their legacy sandbox

  Customers Using Private/Public Apps

  If your sandbox connects to external systems, expect a deeper review. You may need to:

  • Assess and reconnect private or public apps
  • Refresh authentication tokens, secrets, scopes
  • Update references to your new sandbox’s account ID
  • Review workflows that contain webhooks or custom-coded actions
  • Once validated, you can delete your legacy sandbox

  Why We’re Making This Change

  Legacy sandboxes were foundational, but they had key limitations, especially around tracking changes critical for supporting safe, predictable deployments to production.
  The new Standard Sandbox addresses these challenges with:

  A production-like environment for supported assets

  • A more accurate representation of supported assets, allowing you to test confidently without disrupting live systems or your end users in production.

  A native Deploy to Production experience for supported assets

  • You no longer need to rebuild supported assets manually once testing is complete. The new deployment technology provides:
    • Predictable, safer deployments
    • Visibility into eligible assets and required connected assets
    • Conflict warnings
    • Deployment logs for transparency and troubleshooting

  Why the legacy resync feature is removed

  Although the resync feature felt useful, it introduced major instability in sandbox development. It could overwrite in-progress work, break change tracking, disrupt reliable development practices, and increase the risk of errors when deploying changes to production. Removing resync eliminates these risks and ensures sandboxes remain clean, consistent environments you can trust.

  How to get a fresh copy of production

  To maintain a reliable development environment, your sandbox should be recreated, not resynced, whenever you need a fresh copy of production. Recreating your sandbox eliminates drift, restores a clean baseline, and ensures that what you test behaves the same way in production.
  This change makes deployments more predictable and aligns our process with industry standards for managing development environments and deploying tested changes to production safely.

  How to Manage Your Sandboxes Going Forward

  To get you started adopting this new way of working with the delete and create model consider implementing lightweight governance practices such as:

  • Defining when a sandbox should be recreated
  • Assigning clear ownership and access
  • Keeping sandboxes purpose-driven and uncluttered
  • Deploying changes intentionally, not reactively

  Together, these practices support safer deployments, reduce operational risk, and clarify how sandboxes should be managed across your organization. Here’s a framework to help you get started.

  Checklist for Customers with Connected Apps

  If your legacy sandbox has connected apps, review the following when assessing configuration requirements in your new standard sandbox:

  Account IDs

  • Each sandbox has a unique ID. Update any systems that reference your legacy sandbox’s ID.

  API calls, authentication, and secrets

  • Generate new credentials in your new sandbox and update external systems if needed.

  Private & Public Apps

  • Private apps: reconnect and generate new tokens (Developer docs here)
  • Public apps: reauthorize following developer documentation here

  Workflows with Webhooks or Custom-Coded Actions

  • Review and update webhook and custom-coded actions
    • Update authentication types (KB article here)
    • Re-enter endpoint details

  CRM Data Imports

  If you test data flow across systems, you may need to reimport CRM records.
  Because record IDs differ between production and sandbox, consider using a consistent identifier:

  1. In Production: Create a custom property (e.g., “external ID”)
  2. In Production: Use a workflow to copy record IDs into this property
  3. In Sandbox: Use this external ID to upsert records

  Next Steps

  If you haven’t already, the best next step is to create your new Standard Sandbox and review what may need to migrate. Most of the work will be straightforward, and if you have integrations, a bit of early review ensures a smooth transition.

  Final Thoughts

  We know this change represents a shift in how you’ve used sandboxes in the past. We’re sharing it early to give you clarity and confidence throughout this transition.
  The improved Standard Sandbox, with its production-like environment and Deploy to Production, helps you build, test, and deploy changes the way modern teams should: safer, more predictable, and more efficient.

  Questions or concerns?

  Join us in the Developer Community Forum for a peer-to-peer discussion.

  Original source Report a problem

  Show more
• Dec 15, 2025

  • Parsed from source:
    Dec 15, 2025
  • Detected by Releasebot:
    Dec 16, 2025
  

  Hubspot

  Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

  RevOps and Marketing Ops get a safer, production-like Standard Sandbox with Deploy to Production, plus an official sunset of Legacy Sandboxes on March 16 2026. The update guides teams through migration with temporary limits to test safely before going live.

  Key Dates

  • December 15, 2025: New Standard Sandboxes launch
  • March 16, 2026: Legacy Standard Sandboxes sunset

  What This Means for You

  To support this change, your sandbox limit will be temporarily increased so you can create and configure a new standard sandbox while still accessing your legacy sandbox.

  • Most customers will experience minimal impact.
  • Teams with connected apps that orchestrates data flow across systems may need to review and reconnect certain elements in the new sandbox.

  The new standard sandbox includes:

  • A more accurate representation of the most requested supported asset types
  • A new Deploy to Production feature for supported asset types

  FAQ — What You Need to Do Before March 16, 2026

  Who can make these changes

  Any Super Admin can create a new standard sandbox and delete the legacy one. We recommend coordinating with the Super Admins who actively use sandboxes and maintain integrations to assess the requirements.

  If you have questions not answered in this FAQ please reach out to your Customer Success Manager or visit the HubSpot Help Center.

  How to assess your migration needs

  1. Create your new Standard Sandbox
     Your temporary sandbox limit allows you to create it without deleting your legacy sandbox.

  2. Review what’s in your legacy sandbox
     Identify any integrations, apps, or automation your tech stack depends on, for example:

  • Connected private or public apps
  • Workflows that send data externally through webhooks
  • Custom-coded workflow actions

  1. Recreate or reconnect what you need
     If you use integrations or apps, you may need to:

  • Reconnect private and public apps
  • Update authentication or secrets in integration settings and workflows with webhooks

  1. Validate your setup in the new sandbox
     Ensure integrations, authentication, and any data-flow-related logic are functioning correctly by comparing them against your legacy sandbox or requirement documentation.

  2. Delete your legacy sandbox
     Once your new sandbox is fully operational, delete the legacy sandbox. Your temporary sandbox limit increase will be removed.

  What happens to legacy sandboxes on March 16, 2026

  If you don’t migrate before March 16, you will lose access to your legacy sandboxes. After that date, only the new Standard Sandbox will be supported.

  Who Is Impacted

  Most Customers (Simple Testing Use Cases)

  Most teams will experience minimal impact and can simply:

  1. Create a new standard sandbox
  2. Confirm no migration needs exist
  3. Delete their legacy sandbox

  Customers Using Private/Public Apps

  If your sandbox connects to external systems, expect a deeper review. You may need to:

  • Assess and reconnect private or public apps
  • Refresh authentication tokens, secrets, scopes
  • Update references to your new sandbox’s account ID
  • Review workflows that contain webhooks or custom-coded actions
  • Once validated, you can delete your legacy sandbox

  Why We’re Making This Change

  Legacy sandboxes were foundational, but they had key limitations, especially around tracking changes critical for supporting safe, predictable deployments to production.

  The new Standard Sandbox addresses these challenges with:

  A production-like environment for supported assets

  A more accurate representation of supported assets, allowing you to test confidently without disrupting live systems or your end users in production.

  A native Deploy to Production experience for supported assets
  A native Deploy to Production experience for supported assets

  You no longer need to rebuild supported assets manually once testing is complete. The new deployment technology provides:

  • Predictable, safer deployments
  • Visibility into eligible assets and required connected assets
  • Conflict warnings
  • Deployment logs for transparency and troubleshooting

  Why the legacy resync feature is removed

  Although the resync feature felt useful, it introduced major instability in sandbox development. It could overwrite in-progress work, break change tracking, disrupt reliable development practices, and increase the risk of errors when deploying changes to production. Removing resync eliminates these risks and ensures sandboxes remain clean, consistent environments you can trust.

  How to get a fresh copy of production

  To maintain a reliable development environment, your sandbox should be recreated, not resynced, whenever you need a fresh copy of production. Recreating your sandbox eliminates drift, restores a clean baseline, and ensures that what you test behaves the same way in production.

  This change makes deployments more predictable and aligns our process with industry standards for managing development environments and deploying tested changes to production safely.

  How to Manage Your Sandboxes Going Forward

  To get you started adopting this new way of working with the delete and create model consider implementing lightweight governance practices such as:

  • Defining when a sandbox should be recreated
  • Assigning clear ownership and access
  • Keeping sandboxes purpose-driven and uncluttered
  • Deploying changes intentionally, not reactively

  Together, these practices support safer deployments, reduce operational risk, and clarify how sandboxes should be managed across your organization. Here’s a framework to help you get started.

  Checklist for Customers with Connected Apps

  If your legacy sandbox has connected apps, review the following when assessing configuration requirements in your new standard sandbox:

  Account IDs

  • Each sandbox has a unique ID. Update any systems that reference your legacy sandbox’s ID.

  API calls, authentication, and secrets

  • Generate new credentials in your new sandbox and update external systems if needed.

  Private & Public Apps

  • Private apps: reconnect and generate new tokens (Developer docs here)
  • Public apps: reauthorize following developer documentation here

  Workflows with Webhooks or Custom-Coded Actions

  • Review and update webhook and custom-coded actions
    • Update authentication types (KB article here)
    • Re-enter endpoint details

  CRM Data Imports
  If you test data flow across systems, you may need to reimport CRM records.
  Because record IDs differ between production and sandbox, consider using a consistent identifier:

  1. In Production: Create a custom property (e.g., “external ID”)
  2. In Production: Use a workflow to copy record IDs into this property
  3. In Sandbox: Use this external ID to upsert records

  Next Steps

  If you haven’t already, the best next step is to create your new Standard Sandbox and review what may need to migrate. Most of the work will be straightforward, and if you have integrations, a bit of early review ensures a smooth transition.

  Final Thoughts

  We know this change represents a shift in how you’ve used sandboxes in the past. We’re sharing it early to give you clarity and confidence throughout this transition.

  The improved Standard Sandbox, with its production-like environment and Deploy to Production, helps you build, test, and deploy changes the way modern teams should: safer, more predictable, and more efficient.

  Original source Report a problem

  Show more
• Dec 2, 2025

  • Parsed from source:
    Dec 2, 2025
  • Detected by Releasebot:
    Dec 3, 2025
  

  Hubspot Developers by Hubspot

  November 2025 Developer Rollup

  HubSpot rolls out a broad platform update with higher Orders and Carts limits, a new Projects API, and property validations via the public CRM API. The release also boosts developer tooling with HubSpot CLI 7.10.0, per-page CMS headers and footers, and governance changes.

  November updates overview

  November brings a rollup with several updates across the platform. We've expanded record limits for Orders and Carts objects, increased association limits fivefold to 250,000 per object type, and launched the new Projects API for programmatic project management. We're also introducing property validation rules via the public CRM API, releasing HubSpot CLI 7.10.0 with dependency updates and enhanced MCP tooling, and rolling out flexible header and footer switching in the CMS. On the governance front, we're sharing the Platform Lifecycle Management schedule for proactive planning, implementing new user-level permissions requirements for AI connectors on the Marketplace, and enhancing our documentation with required scopes, object definitions, and searchable changelog entries. We've also got important reminders about upcoming API sunsets for Clearbit Logos and Contact Lists v1. Make sure to read on to find out more about each of these updates.

  New Record Limits for Orders and Carts Objects

  We are excited to announce that the Orders and Carts objects have new record limits:

  • Free tier customers: 1 million records
  • Paid tier customers: 15 million records

  These thresholds have been automatically enabled for all customers, no action is required.

  Reminder: Sunset of Clearbit Logos API on Dec. 8, 2025

  A reminder that the deprecated Clearbit Logo API (logo.clearbit.com) will be shut down on Dec. 8, 2025.
  If you are still using this service, we recommend that you use another alternative, such as logo.dev, a free and high-quality logo-fetching service based on domain names. Learn more about migrating to a different service on our Clearbit Logos API sunset announcement.

  Sunsetting Contact Lists API

  The v1 Contacts List API is slated for sunset on April 30th, 2026. Please refer to this announcement for more details on the sunset and migration options.

  Create Property Validations via Public API

  You can now create, update, and retrieve property validation rules through the public CRM API. This allows developers to enforce data consistency and integrity programmatically—for example, requiring specific formats, minimum lengths, or character types for property values. Use the new endpoint

  crm/v3/property-validations/{objectTypeId}/{propertyName}/rule-type/{ruleType}
  

  to define or fetch validation configurations. Learn more in the Property Validations API documentation.

  HubSpot CLI 7.10.0 Now Supports Dependency Updates, Beta Platform Versions & Enhanced MCP Tooling

  HubSpot CLI 7.10.0 delivers a substantial upgrade to the developer experience with the introduction of hs project update-deps, a new command that streamlines updating npm dependencies across project components. This provides a clearer, safer workflow for keeping project libraries current without reinstalling from scratch. The release also adds support for beta platform versions, enabling developers to experiment with upcoming HubSpot platform capabilities before they reach general availability.
  This version includes notable improvements to MCP tooling, including codex integration for setup, message and profile support for MCP project uploads, and enriched debugging output that now surfaces network request context to make troubleshooting smoother. File handling has also been refined—particularly around markdown file collisions—to ensure documentation remains intact during renames.
  On top of these enhancements, developers will find numerous quality-of-life and reliability fixes, from resolving require.resolve() issues in CMS theme previews to improving dependency-related error messages, flag handling, and package-installation utilities. These updates maintain complete backward compatibility while meaningfully modernizing core workflows.
  Watch the new test account creation walkthrough video and check out the full set of changes on GitHub.

  Association Limits Increased to 250,000 per Object Type

  HubSpot has raised association limits for all paid accounts, allowing individual records to be linked with up to 250,000 records of a given object type (for example, 250,000 contacts with a single company). This fivefold increase expands your ability to model large and complex data relationships directly in HubSpot, including via API and imports. Some object-specific limits still apply—for instance, 10,000 associated deals per contact and 1,000 associated records per engagement. Learn more in the Associations API documentation and review the HubSpot Product & Services Catalog for full details on technical limits.

  New in the HubSpot CMS: Switch Out Headers and Footers for Individual Pages

  You can now choose a separate header or footer module per page in the HubSpot CMS. Previously, headers and footers were universal across templates, meaning you had to switch out the template to use a different header or footer per page. This meant that you had duplicate templates with different headers or footers.
  Now, you can switch out the header or footer directly from the page editor. When you hover over a header or footer, you'll be able to open up a modal to replace the current page's header or footer. This will not affect other pages using this same template, only the page you're currently editing.
  This update allows you to have individual headers on footers on pages while re-using the same templates, giving you flexibility across your website, including across different brands.

  The Platform Lifecycle Management Schedule

  HubSpot launched the Platform Lifecycle Management with the Developer Platform, providing a public schedule for project platform version release, support, and deprecation timelines in the developer documentation. This transparency allows developers to proactively plan updates, avoid breaking changes, ensure app stability, and improve end-user reliability. Developers will also receive proactive release and deprecation notifications via the HubSpot CLI, UI, and email. See the developer documentation for the complete schedule.

  New User-Level Permissions Requirement for AI Connectors on the HubSpot Marketplace

  AI connectors are defined as apps that primarily connect HubSpot directly to general-purpose generative AI assistants or agents. Due to the importance of user-level permissions to customer data security and privacy in AI systems, we require all new AI connectors on the Marketplace to support user-level permissions via the HubSpot Developer Platform.
  To list an AI connector on the HubSpot Marketplace, developers must rebuild their app using the official HubSpot MCP server (BETA), which enforces user-level permissions. Only CRM read operations are currently available.
  AI connector apps that do not wish to rebuild using the official HubSpot MCP server can continue to distribute their app and drive installs outside the Marketplace. For this alternative, it is important to be aware of the new active install limits for unlisted apps using the HubSpot Developer Platform as outlined in this Developer Changelog post.
  No additional action is required for customers beyond installing compliant apps; enforcement is applied by Ecosystem Quality via the App Listing Requirements.
  These requirements maintain the same user-level access guardrails implemented in our own connectors. When HubSpot designed and built its own connectors, such as the HubSpot connector for ChatGPT, we built them to enforce user-level access from the beginning (learn more in this blog post). This model ensures that any action taken by an AI assistant or agent on a user's behalf is strictly limited to that specific user's existing permissions within HubSpot, preventing unauthorized data access and maintaining compliance.

  Projects API

  The Projects API is now available in support of HubSpot's new recently launched project object. With this new API, customers and partners can programmatically create, read, update, and associate projects to related records. The Projects API will be available through HubSpot's CRM Objects API framework. See the documentation for more details.

  Documentation Enhancements: Required Scopes, Data Definitions, and Searchable Changelog Entries

  There are several documentation improvements to streamline how you discover and use information in HubSpot's developer documentation:

  • Required Scopes in API Reference Docs: A new, dedicated component now lists the application scopes needed for each API endpoint. This helps you quickly confirm permissions and avoid authentication issues when building or updating integrations.
  • [In beta] Object definition pages for key CRM objects: Selected APIs now include "Object definition" pages to make it easier to understand object structure, find available default properties, and troubleshoot data sync issues. Highlights include:
    • Object attributes: object IDs and fully qualified names, required and searchable properties, and feature support listings.
    • Default properties: searchable lists of default properties per object, which includes the property name and label, data type information, definition, and expandable JSON code for full reference.
      Object definition pages will be rolled out over the next month, starting with the contact, company, deal, and ticket objects.
  • Changelog Entries Shown in Docs Assistant: You can now see recent developer changelog entries directly in documentation assistant results. This means you'll instantly spot any updates affecting the endpoint you're exploring, helping you adapt to changes faster and with greater confidence.
    Collectively, these enhancements are designed to reduce friction—helping you identify needed scopes, understand object models, and monitor relevant updates with less guesswork.

  Third-Party Call Events: Call Started and Call Ended

  HubSpot now enables publishing Call Started and Call Ended events for third-party calls. These events are not only logged but can also be leveraged in Journey Analytics and Workflows, making call data actionable across the platform.
  To ensure these events are published correctly, integrators need to send the following SDK events: incomingCall, callEnded, and finalizeEngagement. For full implementation details, refer to the API documentation.

  Questions or concerns?

  Join us in the Developer Community Forum for a peer-to-peer discussion.

  Original source Report a problem

  Show more
• Dec 1, 2025

  • Parsed from source:
    Dec 1, 2025
  • Detected by Releasebot:
    Jan 7, 2026
  

  Hubspot

  Top Product Updates for December 2025

  HubSpot's December 2025 updates boost automation across tickets, sequences, and buyer signals. New reopen workflows and flexible sequence unenrollment sharpen support and outreach. Public beta adds bulk restore, agent chat via workflows, snoozed tickets, custom report views, and Breeze quotes.

  Top Product Updates for December 2025

  December brought a wave of updates focused on helping teams automate more of their day-to-day. Let's dig into the highlights.

  1. Ticket Re-Opening Management in Help Desk

  Support teams finally have control over what happens when customers reply to closed tickets. Previously, any reply would automatically reopen the original ticket—even months later—wreaking havoc on reporting and SLAs. Now, you can use workflows to define exactly when tickets should reopen versus when a new ticket should be created instead.

  The new workflow template uses properties like "Last closed date" to set your preferred window (say, three days), and automatically creates a fresh ticket for replies that come in after that threshold. The latest message even copies over to the new ticket so reps have full context without flipping between records.

  Availability:
  Service Hub Professional and Enterprise

  2. Customizable Sequence Unenrollment Triggers

  Sequences no longer have to end the moment a contact replies or books a meeting. You can now toggle off these default unenrollment triggers in the sequence builder's Automate tab, giving you flexibility to continue outreach flows when it makes sense—like nurture campaigns where a reply doesn't mean the conversation is over.

  You can also separately control whether replies or meetings should unenroll all contacts at that company, not just the individual. These settings remain on by default to preserve existing prospecting workflows, and engagement badges still appear in the enrollments table regardless of your settings.

  Availability:
  Sales Hub Professional and Enterprise, Service Hub Professional and Enterprise

  3. New Company News Signals for Buyer Intent

  Five new Buyer Intent signals help you spot when target accounts are growing or making moves. You'll now see alerts when tracked companies hire C-level executives, launch products, announce strategic partnerships, complete mergers and acquisitions, or report growth metrics like revenue increases.

  These signals appear on company record timelines and work in workflows, list filters, and scoring models—just like your existing intent signals. They're enabled by default at no extra cost.

  Availability:
  Now live for accounts with HubSpot Credits

  4. Help Desk Search Experience Updates

  Finding tickets in high-volume queues just got easier. The updated search experience includes a new popover with pre-search filters (like limiting results to closed tickets), an improved results page that reflects your filters, and smoother overall interactions.

  Availability:
  Service Hub Professional and Enterprise

  5. Payments in the New Forms Editor

  You can now collect payments directly through forms built in the new editor. Add a payment link as a redirect destination after form submission—either for all visitors or conditionally based on their responses. Both form data and payment details stay connected in HubSpot for easy tracking.

  Availability:
  Rolling out gradually for all products and tiers; conditional logic requires Marketing Hub or Content Hub Professional or Enterprise

  6. Create Contacts from the Chrome Extension

  While researching a company's website, you can now create contacts directly in the HubSpot Chrome extension without switching tabs. The contact is automatically associated with the company you're viewing, keeping your prospecting momentum going.

  Availability:
  Now live for all HubSpot products and tiers

  Now in Public Beta

  Check out our top features that are now available in public beta to all eligible customers.

  1) Restore Property Edits for Bulk Changes

  Made a mistake with a workflow or import that changed data you didn't mean to touch? Restore Property Edits lets you bulk restore recent property changes within the last seven days.

  Navigate to CRM > Actions > Restore Property Edits, filter by source, property type, and date, preview what you're about to restore, and click to apply. Restored records won't re-enroll in workflows or lists.

  Availability:
  Public beta for Enterprise customers with super admin permissions

  2) Deploy Customer Agent Through Workflows and Chatflows

  You can now trigger Customer Agent responses as part of your automated workflows or existing bot logic—no additional setup required. Use workflow branches based on contact, ticket, or conversation properties to control exactly when the agent engages, whether that's routing billing inquiries to AI first or deploying the agent only for specific customer segments.

  Availability:
  Public beta for Professional and Enterprise tiers across all hubs

  3) Snooze Tickets in Help Desk

  Temporarily hide tickets from your views to stay focused on what needs attention now. Tickets automatically unsnooze when customers reply, the snooze time expires, or you manually bring them back.

  Availability:
  Public beta for seated Service Hub Professional and Enterprise users

  4) Custom Views on Reports and Dashboards Lists

  Create personalized filtered views of your reports and dashboards with pinned tabs. Filter by owner, shared status, date created, last viewed, or tags—then save your view as private, team-shared, or available to everyone.

  Availability:
  Public beta for all Professional and Enterprise subscriptions

  5) Create Quotes Through Breeze Assistant

  Generate quotes from anywhere in HubSpot by asking Breeze. The assistant intelligently selects templates and lets you preview the quote outline before creation. The more details you provide—like template or line items—the better the result.

  Availability:
  Public beta for Commerce Hub Professional and Enterprise

  This month's updates center on giving teams more control over ticket lifecycles, sequence behavior, AI agents, and more. Whether you're managing high-volume support queues or fine-tuning your sales automation, these updates help improve how your team works.

  Want to catch up on all the latest product updates? Log into your HubSpot account, click your account dropdown in the top right, and select "Product Updates" to see what's new.

  Original source Report a problem

  Show more
• Nov 24, 2025

  • Parsed from source:
    Nov 24, 2025
  • Detected by Releasebot:
    Nov 24, 2025
  

  Hubspot Developers by Hubspot

  Custom Actions Support for Enrolled & Non-Enrolled Records

  HubSpot enhances workflows with event-based support, adding a requiresObject flag and per-action object targeting. Custom actions can run without an enrolled object and will show a target object selector, defaulting to the workflow’s enrolled object. The change rolls out on November 24, 2025.

  HubSpot custom actions in event-based workflows

  HubSpot workflows are becoming more flexible with expanded support for event-based processes. Traditionally, workflows and their custom actions have relied on a specific “enrolled object” (contact, company, deal, ticket, etc.) to execute logic, which limits their usage when no object enrollment occurs. With the introduction of new workflow types that aren’t tied to a single enrolled object (such as event-based workflows), there is a need for custom actions to adapt accordingly.

  To support these workflows, we’re introducing a new requiresObject boolean flag to extend support for "target objects" in custom actions on November 24th, 2025. This update addresses a long-standing limitation in HubSpot's custom action framework by allowing actions to function in workflows even when no object is enrolled. Additionally, the objectTypes field will now apply at the action level rather than the workflow level. This means each action within a workflow can independently specify which object type it targets. Actions will interpret the data according to the object type selected or, by default, the workflow’s enrolled object.

  With these changes, custom actions will now present customers with a dropdown to select a “target object”. By default, this will be set to the workflow’s enrolled object, preserving existing behavior for current workflows.

  How things worked before:

  • Action definition: The objectTypes field determines which workflow object type the action is available for.
  • Execution payload: An object field is included in the payload (with object type and ID)
  • Fetch options: The workflow’s objectTypeId is included in the request payloads

  Because these elements always depended on the enrolled object, custom actions could not function in workflows that weren’t tied to an object type.

  What's changing?

  As mentioned above, we’re introducing a requiresObject boolean flag (defaulting to true) on all custom actions. When this flag is set to true, a target object will automatically be added to the action, allowing it to work with any object, not just the enrolled one. The workflow runtime will populate the object in the execution payload.

  What does this mean for developers?

  This change affects all custom actions built using the Custom Workflow Actions API or Developer Projects that include custom actions.

  • By default, all actions will have requiredObject: true, meaning the target object selector will appear in workflows. See example below:

  {
    "actionUrl": "https://webhook.site/94d09471-6f4c-4a7f-bae2-c9a585dd41e0",
    "requiresObject": true,
    "objectTypes": ["CONTACT"],
    "inputFields": [
      {
        "typeDefinition": {
          "name": "staticInput",
          "type": "string",
          "fieldType": "text"
        },
        "supportedValueTypes": ["STATIC_VALUE"],
        "isRequired": true
      }
  

  Note: In the example of the custom action definition above, because the action includes objectTypes: [“CONTACT”], it cannot set requiresObject: false, as defining required objectTypes means the action depends on an object.

  If your action does not need to receive a target object and you don’t want end users to see the object selector dropdown, you can set requiresObject: false in your custom action definition.

  When is it happening?

  This change goes into effect in 30 days on Monday, November 24th, 2025.

  Questions or comments?

  Join us in the developer forums for a peer-to-peer discussion.

  Original source Report a problem

  Show more
• Nov 20, 2025

  • Parsed from source:
    Nov 20, 2025
  • Detected by Releasebot:
    Nov 21, 2025
  

  Hubspot

  Release Notes - 25.11 Product Community Release

  November Product Community Release Notes highlight SEO improvements and an Ideas Forum homepage update. Visible changes include thread titles rising above the search bar; backend tweaks boost accessibility and search visibility. Feedback welcome.

  Welcome to the November Product Community’s Release Notes!

  Enhancements & Fixes:

  • Enhancement: SEO
    We are continuing to improve our SEO. These changes will mostly be visible in the back end, improving site accessibility & search engine visibility, but you will notice one visible change in the community: the threads' title will move higher on the page, above the search bar.

  • Enhancement: Ideas Forum Homepage Update
    We have updated our Ideas Statuses for a better organization, and also to improve communication from our Product Team. You will see these changes reflected in the Ideas Homepage.

  We Value Your Feedback

  We value your feedback and use it to improve our platform. Please take a few minutes to submit your ideas and help us make our platform even better.

  Thank you for your continued support!
  The HubSpot Community Team

  Original source Report a problem

  Show more
• Nov 20, 2025

  • Parsed from source:
    Nov 20, 2025
  • Detected by Releasebot:
    Nov 21, 2025
  

  Hubspot Developers by Hubspot

  Take Action With Claude: Update CRM Records and Access Engagement History

  Claude’s HubSpot connector now lets you create and update CRM records, log activities, and act on full engagement history—directly from chat. With public beta for updates and GA for engagement access, this rollout enables faster, context-aware workflows and bulk actions.

  You can now ask Claude to create and update your CRM records, such as contacts and deals, and log activities like notes or tasks. Claude will also have access to your complete engagement history, including emails, calls, and meetings.

  What’s Changing

  The HubSpot Connector for Claude is gaining two new capabilities:

  • [Public Beta] Update CRM records: The HubSpot connector for Claude can now create and update CRM records and log activities directly from Claude’s chat window – including new contact and deal creation, and logging notes or tasks.
  • [Live in GA] Access engagement history: Claude can also generate and take action on powerful insights based on your complete engagement history (emails, calls, meetings, tasks, and notes).

  Please note:

  • If your HubSpot account has sensitive data enabled, the HubSpot connector for Claude will not have access to any engagement data for added security.
  • When using create and update actions in the HubSpot connector for Claude, attribution will be recorded in your HubSpot account’s Audit Log to the user and the Claude connector.
  • The HubSpot connector for Claude supports bulk Create and Update actions for a maximum of 10 records in a single request.

  Why Does It Matter?

  With expanded write access and engagement visibility, the HubSpot connector for Claude allows you to update your HubSpot context directly without leaving Claude. Ask Claude to log a discovery call, create follow-up tasks, update deal stages, or analyze months of customer emails using natural language.
  By accessing engagement history such as emails, tasks, and notes, Claude can surface meaningful insights and let you take action on them instantly, right from the chat window. This unlocks faster, more intelligent use cases, like:

  • Faster workflows: Create a task to follow up with a prospect who had questions on pricing.
  • Smarter insights: Claude can now access your email threads and call notes to provide context-aware recommendations.
  • Less manual work: No more copying insights from Claude into HubSpot properties manually – update directly from Claude’s chat window.
  • Better decisions: Analyze real customer conversations, not just CRM snapshots.

  How Does It Work?

  To access write access and engagement visibility in the HubSpot connector for Claude, you’ll need to disconnect and reauthenticate your HubSpot account.
  Please note: to allow the connector to access engagements, and to create and edit records, a Super Admin must opt your account into this product update.

  Example prompts

  Updating CRM context (write access): The HubSpot connector for Claude can update your CRM directly.

  • “Create a new contact for [X] at with their email [insert email address]”
  • “Update the deal ‘Enterprise Package Q4’ to Closed Won.”
  • “Log a note on this ticket summarizing our resolution approach.”
  • “Create a task for me to follow up with [X] next Tuesday about contract renewal.”

  Engagement visibility: The HubSpot connector for Claude can now access your communication history to provide richer context.

  • Sales: “Summarize all my emails with [X] from the last month and list any issues that might affect deal closure.”
  • Marketing: “Create Follow-Up Tasks from Recent Email Opens”
  • Service: “Show me all open tasks assigned to me this week, sorted by priority.”

  For more prompts, please visit our prompt library.

  Additional Best Practices

  • Start small by updating a single record before making bulk changes.
  • Always review the proposed changes that Claude shows before execution and take a moment to confirm them.
  • For the best results, use the latest models and turn on “Extended Thinking” mode.

  Please note: A Super Admin or a user with App Marketplace permissions in your HubSpot account must connect the connector for the first time and select the allowed permissions for it. Once this is done, they can give access to other users to connect it. Learn more about how you can manage access to the connector.

  The HubSpot connector for Claude respects user permissions, users will only see the CRM context they’re allowed to access in HubSpot. For example, individual sales reps will only see pipeline data for deals they have permission to view or update.

  The HubSpot connector for Claude responds in the language used by the user, if supported. For the full list of supported languages, please refer to Anthropic’s multilingual documentation & supported countries and regions.

  Who Gets It?

  The HubSpot connector for Claude is available to all HubSpot customers across all tiers who have a paid Anthropic subscription (Pro, Max, Team, or Enterprise).
  To access the connector, individuals must have:

  • An active HubSpot user account
  • A paid Claude subscription (Pro, Max, Team, & Enterprise)

  For detailed guidance on using these new capabilities, visit the documentation for HubSpot Connector for Claude.

  When is this happening?

  This update goes into effect on November 20, 2025.

  Questions or comments? Join us in the developer forums.

  Original source Report a problem

  Show more