Kommo Custom Fields
This article describes working with Kommo custom fields in LightLead.
Custom Field Discovery
Custom fields are loaded from cf_{field_id}. The field_code field is matched in uppercase, and field_name is matched in lowercase. When a custom field is renamed in Kommo, its identifier (field_id) does not change, so the matching is preserved.
Field Matching
LightLead uses the field identifier (field_id or field_code) for matching. This ensures:
Rename resilience: matching is preserved when a field's name changes in the CRM
Uniqueness: each field is identified unambiguously
Cross-account isolation: fields from different accounts don't overlap
Custom Field Types
| Field Type | Support | Usage |
|---|---|---|
| Text | Full | Grouping, filtering |
| Number | Full | Metrics, range filtering |
| Date | Full | Period filtering |
| Select | Full | Grouping, filtering |
| Multi-select | Partial | Filtering by inclusion |
| Checkbox | Full | Filtering (yes/no) |
| Phone | Full | Grouping, filtering |
| Full | Grouping, filtering | |
| File | Not supported | — |
| Image | Not supported | — |
Impact on Saved Reports
Important aspects when changing custom fields:
Renaming a field: reports continue to work, the name updates automatically
Changing a field's type: may cause errors in reports that use this field as a metric
Deleting a field: reports using this field will show an error, and the field is marked unavailable
Adding a field: the new field becomes available after re-running discovery
Recommendations
Plan your custom field structure in advance
Don't change the type of an existing field unless necessary
Before deleting a field, check which reports use it
Use meaningful field names for easier searching in the interface