Creating custom properties
Custom properties let you extend Katalyz's data model with fields that match how your business actually operates — deal amounts, close dates, prospect scores, industries, or anything else you want to track per-room.
Once defined, custom properties can be:
- Displayed in rooms via the Field widget
- Referenced as variables (type
$in a text widget) to personalize content per-room - Mapped to HubSpot (or other CRM) fields for bidirectional sync
⚠️ Requires org role Admin. Go to Data settings.
The four object types
Katalyz groups properties by the object they belong to:
Object type | What it represents | Example properties |
|---|---|---|
Rooms | Deal-level data on a room | Deal amount, Deal stage, Close date, Prospect score |
Contacts | People in your CRM who interact with rooms | Email, Phone, Job title, Company domain |
Participants | People you've invited to a specific room | Role, Last login, Industry segment |
Actions | Tasks and steps inside rooms | Priority, Due date, Status, Assignee |
Each object has its own tab in the Data settings.

Property types
The Property type picker offers eighteen types, in five groups:
Group | Types |
|---|---|
Categorization | Pipelines · Tags |
Text input | Single-line text · Multi-line text · Rich text |
Values | Phone · Number · Percentage · Currency |
Choose options | Checkbox · Multiple checkboxes · Dropdown select · Multiselect · Radio select · Datepicker |
Other | User · Upload file |
A Search box at the top of the list filters them all.
Creating a property
- Go to Settings → Data → Custom objects.
- Pick the tab for the object: Rooms, Participants or Actions.
- Click Add property, top right.
- The Add property dialog offers two paths:
- Import from HubSpot, badged Recommended — "Import a property directly from HubSpot. Its options and details will stay automatically synchronized over time."
- Create new property — "Create a new property that will exist only within Katalyz. You'll be able to map it to fields from external apps, but the options and details will not stay automatically synchronized over time."
- The second path opens a form:
Field | What it does |
|---|---|
Name (required) | The human-readable label |
Property type | See the list above; defaults to Single-line text |
Object | Echoes the tab you came from |
Visibility | Who sees the property; defaults to All users |
Description | Optional |
Extraction hint | Recommended — see below |
Mapping (optional) | An Integration picker, to point the property at a CRM field straight away |
The extraction hint is the field that puts the AI to work. Its own help text spells out why it matters: "Recommended — helps AI auto-fill this field from recordings and room data. Required at the moment someone triggers an AI update in a room."
Cancel on the left, Add on the right.
Extraction hint — teaching AI how to fill the property
Every property has an Extraction hint field (marked with the AI sparkle). It's one line that tells the assistant when and how to fill this field from a call recording or the room's data — the placeholder reads "Tell AI when and how to fill this field — from a call recording or the room's data…".
- It's recommended at creation: "helps AI auto-fill this field from recordings and room data."
- It becomes required the first time someone triggers an AI update on that field in a room. The room's Data panel stops with "Add extraction hints to continue" and lets the user write the missing hint in place — but it's cleaner to set it here, once, for every room.
Good hints say what and how: "The annual contract value in euros, as stated by the prospect" beats "Amount". See Auto-filling room fields from recordings.
Origin column
Each property shows an origin:
- Katalyz — created in Katalyz directly
- Imported from HubSpot — originally a HubSpot property, now available in Katalyz via integration
- Imported from Salesforce — same, from Salesforce
Properties imported from CRM come pre-linked to their source field.
Mapping to CRM fields
Any Katalyz property can be mapped to an external integration field (HubSpot, Salesforce).
The Mapped with column in the properties table shows the current mapping:
- Empty (not mapped) — property exists in Katalyz only
HubSpot / deal_amount— mapped to thedeal_amountfield in HubSpot
To map or change a mapping, click the row → Edit property → select an integration and a field.
Some fields have canEditMapping: false — typically properties that were imported from HubSpot and should stay linked to their origin. Editing these would break the sync.
Usage tracking
The Used in column shows how many rooms actively use each property. This helps you:
- See which properties your team actually reaches for
- Identify candidates for cleanup (properties with 0 uses)
- Gauge the impact of deletion (a property used in 57 rooms is a big commitment to remove)
Using custom properties in rooms
Once a property is defined, it can power:
Field widget
Add a Field block to a room. Bind it to a custom property. The widget displays the current value.
Variables in text widgets
Type $ in a text widget to insert a property as a variable. The variable is replaced with the actual value when the room renders.
Room creation — fill custom fields up front
When someone creates a room, the details step has a Custom fields section. + Add field opens a picker over your org catalog (the Rooms properties defined here — Priority, Deal amount, Account tier, Region, Renewal date, and so on). Each added field renders the right input for its type — text, number, currency, date or select — so the value is set before the room even exists. When every catalog field has been added the button reads All fields added.
Each added field has a grip handle: drag to reorder, or click it for a menu with Always show on new rooms and Delete. A pinned field shows a filled bookmark ("Shown on every room") and pre-appears on every new room that user creates; Stop showing on every room unpins it. Pins are remembered per browser — a personal shortcut, not an org setting.

Rooms list — custom fields as columns
On the Rooms page, the columns button (gear icon) opens a two-panel menu:
- Panel 1 — Native fields (a checkbox per built-in column, with a Reset link once anything is customized) and Custom fields (the org fields already added as columns, each with a type badge — Text, Number, Amount, Date or Select). The footer button + Add custom field opens panel 2 and reminds you how many fields are defined in Settings → Custom objects.
- Panel 2 — a searchable picker over the whole catalog (Search custom fields, checkbox list, footer count N selected).
Column choices are remembered per browser.

Editing and deleting
- Edit — change the property's label, description, extraction hint, or mapping. The field type generally can't be changed (would corrupt existing values).
- Delete — removes the property from every room and every template that uses it. Widgets and placeholders referencing it break.
Before deleting, check the Used in count. A property in use across dozens of rooms should be phased out carefully — update the affected rooms first.
Related articles
Updated on: 04/10/2026
Thank you!
