Build on property settings with the Properties Schemas API

Per the panel, the Properties Schemas API brings roll-up and sync properties, field-level permissions, validation rules and richer property metadata to the API. It is in public beta for all hubs and tiers. The point of the Why text is that anything you can do in property settings you can now do programmatically, where before many settings could not be read or written through the API and validation rules lived in a separate API from the property they governed.

I raised this one because everybody gets excited about property schemas, and I wanted to know one specific thing: does it reach the documentation space of property settings, the dedicated area with data entry instructions that explains how a property should be completed by users and by agents? If it does, I have a way to create those instructions through the API, and right now I am not creating them any other way. I asked Breeze and shared my screen. Breeze said it does not explicitly cover the dedicated documentation area, but it does explicitly support property descriptions, data entry instructions and option descriptions. I read that as Breeze talking about the text of the update, whether or not the update says it, so I am calling that another win for us. That is Breeze's answer, not the panel's, so test it before you build on it.

Why I care about that space at all: if you are concerned about how your agents might be using the CRM, you can build instructions for them at the property level, saying how and when to use the property. Casey said she has been really happy with that documentation section overall and called it a big improvement. She added that if you have a dropdown, a radio or anything with options, you can give descriptions to the options too, and she has been using that helping a client with properties for the sales team, like “a deal is this type of deal if these things are true.” I said visibility indeed.

Casey also tied it to what she said on the show yesterday: an API just means asking what your AI connectors can do now, and she had been blocked on some of these exact things when building properties. Ryan called it a massive upgrade to the properties API. His version: when you are building a portal, the choice between roll-up properties, calculated properties and permissions is nuanced, and he has had to undo what he built through the API because it created plain text or simple properties that needed to be roll-ups. He said it closes that gap, the timing is kind of perfect, and good job HubSpot.

What to do: if you build properties through the API or through an AI connector, read the schema docs this week and test roll-up, validation rules and the documentation text on a sandbox object before you touch anything live. If you only build properties in the UI, you can wait; nothing changes in what you see.