HubSpot: Update a property group
HubSpot properties.propertyGroupsUpdateProperty: arguments, response, policy and SDK examples.
← Properties operations · Get started
Operation hubspot.properties_property_groups_update_property
Provider route: PATCH /crm/properties/2026-09/{objectType}/groups/{groupName}. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/hubspot with npm, or alter-sdk-hubspot with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { HubSpotIntegration } from "@alter-ai/hubspot";
async function execute(input: Parameters<HubSpotIntegration["properties"]["propertyGroupsUpdateProperty"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new HubSpotIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.properties.propertyGroupsUpdateProperty(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_hubspot import HubSpotIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = HubSpotIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.properties.property_groups_update_property(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.groupName | string | Required within parent | |
path.objectType | string | Required within parent | |
body | Model | Required within parent | Expand Update a property group — request body — body |
Referenced models: Update a property group — request body — body
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Read a property group — response body |
Referenced models: Read a property group — response body
Schemas
Section titled “Schemas”Read a property group — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
archived | boolean | Required within parent | Indicates whether the property group is archived. |
displayOrder | JSON | Optional | |
displayOrder (anyOf 1) | integer | Alternative | Property groups are displayed in order starting with the lowest positive integer value. Values of -1 will cause the property group to be displayed after any positive values. Format: int32 |
displayOrder (anyOf 2) | string | Alternative | Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$ |
label | string | Required within parent | A human-readable label that will be shown in HubSpot. |
name | string | Required within parent | The internal property group name, which must be used when referencing the property group via the API. |
Update a property group — request body — body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
displayOrder | integer | Optional | Property groups are displayed in order starting with the lowest positive integer value. Values of -1 will cause the property group to be displayed after any positive values. Format: int32 |
label | string | Optional | A human-readable label that will be shown in HubSpot. |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: hubspot.properties_property_groups_update_property. Catalog operation: properties_property_groups_update_property. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
Required provider scopes: ["crm.objects.carts.write", "crm.objects.orders.write", "crm.objects.users.write", "crm.pipelines.orders.write", "crm.schemas.appointments.write", "crm.schemas.carts.write", "crm.schemas.commercepayments.write", "crm.schemas.companies.write", "crm.schemas.contacts.write", "crm.schemas.courses.write", "crm.schemas.custom.write", "crm.schemas.deals.write", "crm.schemas.invoices.write", "crm.schemas.listings.write", "crm.schemas.orders.write", "crm.schemas.projects.write", "crm.schemas.quotes.write", "crm.schemas.services.write", "crm.schemas.subscriptions.write", "e-commerce", "tickets", "tickets.highly_sensitive.v2", "tickets.sensitive.v2"]