List custom field mappings
Returns the team’s custom field mappings: one record for each source (a CRM, or csv for CSV uploads) whose field mapping was saved in the dashboard’s integration settings. Each entry in fields (contacts) and lead_fields (leads) ties a field in that source (external_key, external_name) to the name Salesfinity shows for it (internal_name). When contacts are imported from a CRM, each mapped field becomes a custom field on the contact whose label is the internal_name.
The custom_fields you send to POST /v1/contact-lists and POST /v1/contact-lists/{id} are free text and are not checked against these mappings. Reuse an internal_name as the label to give an API-created contact the same field a CRM-imported one has.
Not paginated. The array is empty when nothing is mapped. Records for some CRMs also carry deal_fields, account_fields, deal_field_mapping and account_field_mapping.
hubspot, salesforce or csv. The response is a plain array, not paginated, and empty when nothing is mapped.
What a mapping does
Each entry infields (contacts) or lead_fields (leads) ties a field in the source to the name Salesfinity shows for it:
label set to internal_name. Records for some CRMs also carry deal_fields, account_fields, deal_field_mapping and account_field_mapping, which set the deal and account fields shown for that CRM.
Using mappings with contact lists
Thecustom_fields on contacts you send to Create a contact list and Add a contact to a list are free text: nothing checks them against these mappings. To give an API-created contact the same field a CRM import creates, use the mapping’s internal_name as the label:
Example
Authorizations
Response
Every custom field mapping record for the team.