Hubspot Developers Release Notes

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

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

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

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

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

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

CPQ Quote Expiration Logic Change

October has come to an end, so happy Halloween to all who celebrate 🎃. We've got a packed rollup for you, including logic change to CPQ quotes, a bugfix for product delete permissions, a new batch endpoint for the v3 Lists API, back-to-back minor releases for the HubSLot CLI, and new workflow action insights in connected apps. In public beta land, we have app churn analysis now available in our dev MCP, a new way to share reports with your app, and a new system for importing users int HubSpot from your app. Make sure to read on to find out more about each of these updates.

Previously, CPQ quotes expired once the expiration date passed—regardless of whether buyers had already signed. Now, CPQ quotes will only expire if the buyer has not signed by the expiration date. Once all buyers sign, the quote remains active for payment setup and countersignature without any time limit. This update removes unnecessary delays and rework, allowing buyers to sign before the deadline and complete payment later, while you can countersign without worrying about expirations.

Bugfix: Product delete permissions and app installation

We've updated the permissions required to install apps requesting the e-commerce or crm.objects.products.write scopes. Previously, these scopes did not require that the user had permission to delete product records, but would still allow products to be deleted through the CRM APIs. Going forward, users installing apps requesting either of these two scopes will need to have permission to delete products in order to complete the installation.
This update will only affect new app installations going forward, and existing installations with these two scopes will continue to function as expected without requiring the app to be reinstalled.

New Batch List Membership Endpoint Added to V3 Lists API

A new endpoint, /crm/v3/lists/records/memberships/batch/read, allows you to fetch list membership for multiple contact records in a single request. This feature supports migrations from the legacy Contact Lists API (sunsetting April 30, 2026) by enabling batch lookups of list memberships, ensuring smoother transitions and feature parity. Learn more in the Lists API migration documentation.

HubSpot CLI Version Updates: CMS command reorganization, automatic dependency management, MCP tools, and logging overhaul

A pair of back‑to‑back minor releases bring notable improvements to the HubSpot CLI: CMS commands are now grouped under the hs cms namespace, local development is faster and clearer, and we’ve added automatic dependency management, new MCP application‑info tools, and a comprehensive logging migration for more consistent output.

Highlights

• Command reorganization:
  • All CMS‑related commands have moved under the hs cms namespace for better discoverability and logical grouping.
  • Legacy commands (e.g., hs upload, hs fetch, hs watch, hs list, hs remove, hs lint, hs mv, hs logs, hs function, hs module, hs theme) continue to work but are deprecated and display guidance directing you to the new locations.
  • New structure includes: hs cms upload, hs cms fetch, hs cms watch, hs cms list, hs cms delete, hs cms lint, hs cms mv, hs cms function, hs cms theme, hs cms module, etc.
  • Custom object schema commands are reorganized under hs custom-object (moved from hs custom-object schema) for consistency.
• Automatic dependency management:
  • hs project dev now checks for and installs required dependencies automatically to reduce setup friction.
• Improved local development:
  • The local development process now includes better handling to fail earlier if other instances are already running.
  • You now have the ability to identify whether your OAuth backend is running.
• MCP tools:
  • New application‑info tools surface API usage patterns and application information to aid diagnostics and optimization.
• Logging overhaul:
  • Comprehensive migration from custom loggers to uiLogger across commands and libraries for consistent, readable output.
• Bug fixes:
  • Fixed auto-update behavior in the hs config set command so updates no longer trigger during config set.
  • Updated the UI extensions dev server version to fix compatibility issues.
    If you need to update your local CLI, run: npm install -g @hubspot/cli.

Introducing Workflow Action Insights in Connected Apps

Earlier this month, in October, we added workflow action insights to each app’s settings page in Connected Apps. This update gives integration managers and admins visibility into how workflow actions from their installed apps are being used within their portal.
By surfacing these insights directly in Connected Apps, customers can better understand how their integrations drive automation and uncover opportunities to increase adoption and value.
For app developers, this feature helps your omtehrations stand out, making it easier for customers to see, use, and expand the app workflow actions within HubSpot.

What's changing?

For any app that provides workflow actions, a new workflow action insights section now appears in its Connected Apps settings page. This panel surfaces real-time usage data and configuration details for that app’s workflow actions.
Customers of your apps can now see:

• Configured Workflow Actions: Each workflow action that is currently in use, including workflow names, status (on/off), creator, last updated by, and enrollment metrics (total and past 7 days).
• Unconfigured Workflow Actions: Actions available but not yet used, with a direct link to Automation to build a new workflow.
• Adoption Metrics: Enrollment data to gauge adoption and activity trends within the portal.
  This update empowers customers to measure the impact of their integrations and helps developers drive deeper automation adoption across their installs.

Public Betas

Public Beta: App Churn Analysis Data Available via HubSpot Local MCP Server

We are excited to announce the release of app churn analysis data for the HubSpot development MCP server via the CLI. This new capability is designed to help developers and app partners gain clear, actionable insights into app usage patterns and user engagement—directly from their development workflow.

What's changing?

The new app churn analysis feature for the HubSpot development MCP server, available via the CLI, provides developers with actionable insights into app usage and engagement, helping them identify churn risk and respond quickly to trends.
With this new capability, developers can:

• View Usage & Trends: Access detailed data for up to 6 months to track patterns, understand the impact of releases, and see how different segments of your user base are engaging with your app.
• Predict & Assess Churn: Identify churn-prone segments with calculated scores and AI-generated usage summaries over the last 3 months, enabling preemptive action.
• Segment & Diagnose: Analyze your user base by categories—Stable, Increasing, Decreasing, or Insufficient Data. At-risk segments are further broken down by industry and grouped by portal count (specific portalIDs are not shown).
• Receive Recommendations: Get summarized insights and practical suggestions to reduce churn and improve retention, with more detailed recommendations in future updates.
  This feature delivers the fast, accessible feedback and user insights that HubSpot app partners and developers need to optimize app performance and boost adoption.
  To get started, join the MCP server public beta. Then, follow the instructions in the Developer Documentation. Once your MCP setup is complete, you can test the feature by asking questions such as:
• "Please predict churn for (appID or appName) based on the app API usage for the last 3 months."
• "Please analyze the API usage for my (appID or appName) for the last 3 months."
  You can also ask “list all my apps” to view all of your apps in your Developer portal if you’re unsure of the specific app ID or app name you would like a churn analysis for.

Public Beta: Share HubSpot reports with your app

App developers can use a new, streamlined framework to quickly add report-sharing functionality to their apps with minimal development time. This allows users of your app to schedule and automate HubSpot reports to be shared on a chosen cadence. See the documentation for more details.

Public Beta: Import users into HubSpot from your app

We're introducing a new system to make it easier to add user-importing functionality to your app. This new system allows your users to bulk import users from your app into their HubSpot accounts. This new system works from within the HubSpot user management settings pages, making it easy for HubSpot account admins to add new users to their account in one place.
See the documentation for more details and setup instructions.

Original source Report a problem

In September 2025, HubSpot rolled out a series of impactful developer updates, alongside those already announced during Inbound for the Developer Platform and API updates. Additional changes this month include a new Tooltip component and the addition of textTransform options, which improve UI consistency and guidance. Developers gained powerful new app card hooks—useCrmProperties and useAssociations—for streamlined access to CRM data. HubSpot CLI v7.7.0 shipped with multi-config support, enhanced account management, and key bug fixes, while the Global Content Editor now supports in-context navigation editing. Other highlights include unsubscribe surveys to gather feedback, a new Marketplace collection for Breeze Assistant apps, a bug fix for the v3 Marketing APIs, and reminders about critical deprecations: Classic CRM Cards (sunset in October 2026) and Node.js v18 (support ending in October 2025). Together, these changes enhance developer productivity, streamline workflows, and prepare teams for the next phase of HubSpot’s platform evolution.

See additional details below.

New Tooltip Component & Text Transform Options for Text
A new Tooltip component can now be added via the overlay prop on Button, Image, Link, LoadingButton, and Tag, making it easy to provide hover help and inline guidance. See more on the Tooltip docs.
The Text component also supports new textTransform values—uppercase, lowercase, capitalize, and sentenceCase—so you can standardize casing without custom logic. Learn more on the Text docs.

React Hooks to Fetch Properties & Associations for App Cards
We’re introducing two experimental data-fetching hooks for app cards:

• useCrmProperties
• useAssociations
  These hooks make it easy for you to access and format CRM record data and associations directly within app cards.
• useCrmProperties fetches specified properties from the current CRM record, with optional formatting for dates, currencies, and more.
• useAssociations retrieves associated objects (such as contacts, companies, deals, etc.) with support for pagination and property selection.
  Both hooks also automatically optimize for performance and cleanup. Additionally, the data returned through these hooks respect authenticated user's permissions. You can view examples of these hooks on the dev docs.

HubSpot CLI Release v7.7.0
HubSpot CLI V7.7.0 is a minor release focused on improving the developer experience through enhanced prompts, warnings, and critical bug fixes for local development and test account management workflows.
New Features:

• Multi-config support: Added support for multiple configuration values with: hs config set command
• Enhanced account management: Introduced interactive account selection prompts when running: hs test-account delete
• Legacy project warnings: Added log warnings when legacy files are detected in v2025.2 projects.
  Bug Fixes:
• Local development stability: Fixed a bug where project validation errors caused local processes to exit unexpectedly.
• Test account creation: Resolved issue where the hs test-account create default option now correctly sets all hub tiers to Enterprise level.
• Authentication messaging: Fixed allowlist messages to only display for static authentication apps.
• Local development compatibility: Fixed a bug that caused the local development panel to experience compatibility issues with certain hublets.
  How to Update:
• New installation: npm install -g @hubspot/cli
• Existing users: npm update -g @hubspot/cli@latest

Navigation Editing in Global Content Editor
You can now access advanced menus and navigation settings directly within the Global Content Editor. No need to go to Settings—edit menus in context while building your site.
How It Works:

• A new convenient modal opens within the editor, giving you quick access to advanced menu and navigation settings instead of switching tools.
  This update streamlines header and footer creation, reduces context switching, and enhances website-building efficiency for all hubs and tiers.

Collect Feedback with Unsubscribe Surveys
You can now trigger an optional survey on your site’s email preference page to collect feedback about why a contact is unsubscribing from all emails. Use this feedback to gain valuable insights into your marketing email strategy, reduce churn, and improve content relevance without adding friction to the unsubscribe process. Review it in case you want to add CSS styles to your theme for this feature.
Within the Settings > Marketing > Email > Subscriptions tab, you can now enable an unsubscribe survey. Once enabled, any contact who unsubscribes from all email communications will see a short, optional questionnaire on the confirmation page.
Survey options (presets):

• I'm no longer interested
• I didn't sign up for your mailing list
• I receive too many emails
• Your emails are not relevant to me
• Other (includes a 50-character open text field)
  Where to see results:
• Contact record: The unsubscribe reason will appear in the contact's activity timeline.
• Custom report builder: (Professional and Enterprise tiers only) You can build custom reports using the "Marketing email activities" data source and the "Gave reason for unsubscribe" property. Please note that new data may take 10-15 minutes to appear in reports.
• Marketing Email Performance Page: A chart summarizing unsubscribe reasons will be added to the performance tab of sent emails.
  Styling & CCS standardization
  Unsubscribe Surveys inherit the Global Form Events styling surface used in HubSpot forms. This means you can theme the survey using the same CSS variables and patterns already documented under Global Form events. For a comprehensive list of supported variables and usage patterns, refer to the Forms reference documentation.
  Important Details
• Available for all Marketing Hub tiers: Free, Starter, Professional, Enterprise.
• Default state: Enabled by default for new Free & Starter portals and new Marketing Hub customers; disabled by default for existing Professional & Enterprise portals (opt-in).
• API: Not currently supported; results are available only in the HubSpot UI.
• Customization: Survey questions aren’t customizable.
• We’re flagging this for developers so you can update your theme CSS and leverage Global Form Events variables to style the survey.

Apps for Breeze Assistant Collection
During Inbound, we launched a new Marketplace collection that extends Breeze Assistant with powerful third-party integrations. With these apps installed, critical actions from tools like Google Workspace and Microsoft 365 flow directly into Breeze Studio, enabling you to build and customize Breeze Agents easily. This unifies your tech stack with Breeze, making your Assistant smarter, more extensible, and a productivity multiplier.
To get started, refer to the Marketplace in your HubSpot account or the Marketplace site > Collections > Apps for Breeze Assistant. Then, install the app, connect it to Breeze, and head to Breeze Studio. You’ll see new critical actions ready to be incorporated into your custom agents. The collection features both HubSpot-built and partner-built Agents. And now, Breeze Agents can be seamlessly discovered and installed directly from within the HubSpot Marketplace—streamlining the process of connecting and putting their capabilities to work.

Bugfix: New A/B Email Publishing Support for Marketing Email API
Until now, customers have been unable to publish A/B emails through the v3 Marketing Public APIs. With this change, customers no longer face this limitation, enabling API-driven workflows to include A/B email publishing for those with Marketing Hub Pro and Enterprise subscription tiers.
This was accomplished by updating the content scope to include access to the A/B email type. Developers are not required to add a new scope to their authentication settings, and users should not need to re-authorize your app if they have already approved the content scope. However, if an integration experiences any unusual behavior, please submit a support ticket.

Reminder: Deprecating Support for Classic/Legacy CRM Cards
Announced: May 15, 2025
Deprecation Initiated: June 16, 2025
Sunset Date: October 31, 2026
Support for Classic CRM Cards was deprecated on June 16, 2025. New apps submitted to the App Marketplace can no longer include these legacy cards. Existing apps may continue to use Classic CRM Cards until October 31, 2026, when full support will end.
We encourage developers to migrate to app cards built with React, which offers more flexible capabilities. Additional migration support and resources will be available as we approach the sunset in 2026, but you can begin planning your migration now.
Resources:

• Get started with the developer platform quickstart guide
• Migrate an existing public app to the developer platform
• Learn more about creating app cards

Reminder: Deprecation of Node.js v18
Announced: April 1, 2025
Sunset Date: October 1, 2025
Support for Node.js v18 in HubSpot Serverless functions and CLI ends October 1st, 2025. Existing v18 functions will still run, but you won’t be able to deploy changes without upgrading. New functions must use Node.js v20 or higher. Please update your project framework from v2023.2 to v2025.1 or v2025.2 and CLI (v7.7.0+) before this date to ensure compatibility.
Resources:

• Developer Platform versioning
• HubSpot CLI
• Migrating existing public app to the projects framework
• Migrate an existing private app to the projects framework

Questions or concerns?
Join us in the Developer Community Forum for a peer-to-peer discussion.

Original source Report a problem

On September 3rd, 2025, HubSpot launched the new Developer Platform, version 2025.2, which introduced new customer install limits for marketplace distribution apps that are specifically created or migrated to the latest Developer Platform.
Starting on September 22nd, 2025, apps that are created or migrated to version 2025.2 are capped at 25 installs until they are listed on the HubSpot Marketplace. Alternatively, app partners can distribute apps privately via OAuth to up to 10 customers or 100 for Solution Partners.

What's changing?

• Marketplace Distribution Apps

  • New apps created with the “marketplace” distribution type on the Developer Platform (or public apps migrated to it) are capped at 25 installs until they receive approval for the Marketplace listing.

• Private Distribution Apps

  • Partners may distribute apps privately with the “private” distribution type using OAuth.
  • Limits:
    • 10 customers for app partners
    • 100 customers for Solution Partners

Important Note: When migrating existing legacy public apps with more than 25 installs to the new Developer Platform, the install limit will be automatically enforced. Therefore, careful strategizing and planning of the migration timing, as well as completion of necessary listing requirements, are advised if you choose to proceed.

Additional documentation is provided to help manage the distribution configuration for your app and the Marketplace listing process and requirements for your review.

When is this happening?

• This new limit will be enforced on new or migrated apps with the Developer platform on September 22nd, 2025.
• If you have an existing legacy public app with over 25 installs that has migrated to the new Developer Platform and are encountering errors, please submit a support request for appropriate follow-up.
• For other questions or comments, join us in the developer forums.

Original source Report a problem

Developer Role and seat

• We added a Developer Role and seat - ensuring developers get the permissions they need.

Developer Projects

• Developer Projects are even more powerful and serve as the basis for everything you build on HubSpot.

Unified apps

• Developer Projects are the basis for unified apps - one way to build apps regardless of if it's just for one HubSpot account or many.

New developer project components you can build

• Custom Workflow Actions - Now built right into your project.
• Agent Tools - built on the Custom Actions framework powering workflow actions, you can enable Breeze Agents to interact with your app.
• App Objects - Custom Objects that your app owns and can connect to HubSpot's other CRM objects.
• App Events - the next evolution of HubSpot's timeline events.
• Webhooks using the new Webhooks Journal.

UI Extensions enhancements

• Your app's settings screen is now powered by UI Extensions enabling you to provide thoughtful UIs and controls to admins connecting your app to their account.
• Your UI extension is no longer confined to individual record pages, your app can have its own dedicated App Home page that you can use to display dashboards, and other interfaces that need more screen real estate.

New ways to interact with HubSpot and the developer documentation

• Ask the docs questions powered by AI.
• Ask Breeze Copilot questions about building on HubSpot.
• Our docs are AI optimized.
• New organization of the developer documentation.
• New design.
• Use ChatGPT, Claude, Gemini, and our remote MCP server to directly interact with HubSpot.

Updated developer experience for Developer Projects and Apps

• Log tracing improvements
• Local development UI overview
• Sandbox UI improvements
• CI/CD Pipeline improvements
• Build and deploy logs
• Domain Verification
• Telemetry integration supporting Sentry and Honeycomb
• New tool testing agent to help you improve your agent tools.

Updated CLI

• New hs get-started command.
• New app migration commands to help you get your app ready.
• Your Agentic IDEs can now do more, smarter, and more efficiently with the new CLI-based Developer MCP server — now in public beta.

Original source Report a problem