July delivers improvements to the HubSpot CLI including new HubDB commands, deployment options with force flags and improved authentication flow plus changes to the public repository for CLI development. API capabilities expand with Sequences API access now available to Professional and Enterprise sales roles, in addition to a new multi-select User property feature that enables multiple team members to own individual records.
Developer Updates for July 2025:
HubSpot CLI v7.5.4
A new minor version of the HubSpot CLI has been released including:
A new hs hubdb listcommand to list available tables in an account
An update to the authentication flow to skip opening the browser
Supports a --force flag for project deployments. *This bypasses the warnings when deploys are blocked
To update your CLI to the latest version, run npm i -g @hubspot/cli@latest in your terminal.
HubSpot CLI Repository Changes
The public GitHub repository will no longer be used as our main repository for the HubSpot CLI. Moving forward, HubSpot CLI development work will be completed in a private repo with periodic updates synced to the public repo. Please direct any CLI issues to theHubSpot Developers Feedback Formand tag your submission as a "CLI issue".
Sequences API Access Expanded for Sales Enterprise and Sales Professional Roles
Users with Sales Enterprise or Sales Professional roles (including trial versions) can now use theautomation.sequences.enrollments.writeandautomation.sequences.readscopes within the Sequences API. This expands the API access, improving security and workflow for sales teams by allowing more granular permission management without requiring super admin accounts.
Create Multi-Select HubSpot User Properties
You can now create HubSpot User properties that support multi-select, enabling you to assign multiple record owners to a single property. Previously, HubSpot User properties could only store a single user as a value, limiting your data model when multiple users needed ownership permissions on a record. Now, you can create multi-select User properties to address this. Users selected for these properties are treated as record owners and have the same edit permissions for the record as a single owner. This is particularly useful in scenarios where multiple team members need to manage a single record, such as a contact record owned by several sales team members.
You can create a multi-select User property via API by sending aPOSTrequest to/crm/v3/properties/{objectType}with a request body similar to the following:
*Please note: Existing User properties cannot be configured to be multi-select. Once a User property is created, you cannot change it between multi-select and single-select. This change does not impact the default HubSpot owner property.
I notice the HubSpot changes from July 2025. In order to utilize the new HubDB list command, enhanced auth flow, and --force flag for deployments, I upgraded my CLI to version 7.5.4. Additionally, I now use the API to create multi-select User properties that allow several team members to own a single record. Sales Enterprise and Professional roles now have more access to the Sequences API.
I see the July 2025 HubSpot updates. I updated my CLI to v7.5.4 to use the new HubDB list command, improved auth flow, and --force flag for deployments. I also now create multi-select User properties via the API to let multiple team members own a single record. The Sequences API access is expanded for Sales Enterprise and Professional roles.
Great to see the HubSpot CLI getting quality-of-life updates like the new --force flag and improved auth flow. The multi-select User property feature is a big win for teams managing shared records—finally some added flexibility! While it's not directly related, this reminds me of how user roles and permissions are handled in apps likeToca World APK, where different characters (or users) can interact with the same environment in unique ways. Customization and control really do enhance the user experience across the board.
