Supported types
Every entity that supports properties supports the same data types:- STRING (text) — e.g. phone, job title, department, notes.
- NUMBER — e.g. revenue, employee count, ARR.
- BOOLEAN — toggles.
- DATE — e.g. last contacted, contract/renewal date.
- SELECT_STRING — single/multi-select with string options (custom option colors/icons).
- SELECT_NUMBER — single/multi-select with numeric options.
- ENTITY — a reference to another entity (User, Company, Contact, Document, Project, Channel, Chat, Task, Thread).
- LINK — URLs (website, LinkedIn, etc.).
System vs. custom
A property is either system (built-in and non-removable — like a task’s Status) or custom (something you add). Properties can also be flagged as metadata, which keeps them out of the main views. Editors come in three forms: inline (click-to-edit in a list or pill), popover (a focused dialog), and modal (batch editing across several fields).Pinned properties
Pinning a property promotes it so its value renders as a pill — under a document or task title, for example — for quick scanning and editing. Defaults are per block type: tasks pin Status, Priority, and Assignees out of the box.Built-in fields by block
Some blocks ship with their own system properties:- Tasks — Status, Priority, Assignees, Due Date, Parent Task / Subtasks, Depends On, Effort, Story Points, and Relevant Documents. See Tasks.
- CRM contacts & companies — Email, Name, Company, interaction timestamps, Domains, Email Sync, and more.
Agent access
Agents read and write properties through the MCP entity tools —GetEntityProperties to read, SetEntityProperty to update (status, assignee, dates, custom fields), and ListEntities to browse. See the tool reference.