For Salesforce, HubSpot, Pipedrive, Zoho, or Dynamics integrations, you can fully customize which information Leadfeeder will send to your CRM when creating various entities.
Step 1: Access Your CRM Integration Settings
Go to your Account Settings by clicking the ⚙️ icon at the bottom left of the app.
Select your connected CRM under the Integrations heading.
Step 2: Configure Language and Sync Settings
In the Configuration tab of your CRM integration settings, you’ll find:
The Export Language Configuration option, which allows you to choose the language in which data will be sent.
Language options:
English (default)
German
Users can select the language that determines how the data will be set on the following fields when it is sent from Leadfeeder to the CRM.
This is an account-level setting, meaning it applies to all users within the same Leadfeeder account and not to individual user preferences.
When exporting Companies to the CRM, the following fields will get their values in the selected language:
Country
City
Region
Industry
Description
When exporting Contacts to the CRM, the following fields will get their values in the selected language:
Job Title
Department
Hierarchy
Salutation
Gender
Once selected, all newly exported or synced data from Leadfeeder will follow this language preference.
Step 3: Customize Field Mappings
Open the Field Mappings tab to see the different CRM objects listed.
When you expand one, you’ll see a table showing the default Leadfeeder fields mapped to your CRM fields.
By default, the table includes standard fields (some entities may start empty).
You can add custom fields by selecting a Leadfeeder field and a Destination field, then clicking the ➕ button. (The ➕ button won't appear until you select the fields)
If a field is required in your CRM but Leadfeeder has no data for it, you can set a default value to ensure successful creation.
You can also send hard-coded values by typing a custom value and selecting a destination field.
If a new CRM field was added recently and isn’t showing, you can manually trigger a field sync in your CRM integration settings.
To stop sending a field, either click the 🗑️ icon or toggle it off.
When you configure how Dealfront fields map to CRM fields, you are also defining how enrichment will work for existing CRM records. This field mapping influences which Dealfront data is used when enriching records — for example, which outbound fields are eligible to be updated and how (overwrite vs only if empty). Enrichment behavior follows these mapping rules when triggered manually or automatically.
Supported Destination Field Types
Leadfeeder can only send data to compatible CRM field types:
Salesforce
string (text)
integer (whole number)
double (decimal)
HubSpot
string (text)
number (whole number)
System fields starting with hs_ are not listed.
Dynamics
string (text)
integer (whole number)
Pipedrive
varchar
text (single or multiline)
integer (whole number)
double (decimal)
monetary
phone
Zoho
text (single or multiline)
email
phone
website
picklist
integer
textarea
currency
Important Notes
Customization applies to how Dealfront maps and synchronizes field data when creating new records in your CRM and during later enrichment.
Existing CRM entities can be enriched or updated according to the field mapping and enrichment settings you choose.
For Dynamics, Leadfeeder does not receive error messages if a required CRM field is empty. The object will still be created.
Still unsure how to move forward? Check our Academy Videos, contact us via support@leadfeeder.com or use the live chat. We're happy to guide you.
RELATED: