Pipedrive Custom Fields
This article describes working with Pipedrive custom fields in LightLead.
Custom field discovery
Custom fields are loaded from /api/v1/dealFields, /api/v1/personFields, /api/v1/organizationFields. Pipedrive supports three separate custom field endpoints: /api/v1/dealFields (for deals), /api/v1/personFields (for contacts), /api/v1/organizationFields (for companies). There are 17 base deal fields in total. When a custom field is renamed, its key does not change.
Field matching
LightLead uses the field identifier (field_id or field_code) for matching. This provides:
Resilience to renaming: matching is preserved when a field's name changes in the CRM
Uniqueness: each field is identified unambiguously
Cross-account independence: 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 custom fields change:
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 with this field will show an error, and the field is marked as unavailable
Adding a field: the new field becomes available after discovery is run again
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 easy searching in the interface