Contact and Lead field mapping is a critical step to configure how RollWorks creates contacts and leads in your Salesforce Org, ensuring that data flows smoothly and accurately. Currently, field mapping customization is available for Salesforce Contacts and Salesforce Leads to support the creation of these records when you launch a Contact Discovery Workflow.
RollWorks can create new Contact and Lead records in your Salesforce Org through the following Contact Discovery Workflows:
- Acquire New Contacts: this Workflow template uncovers new contacts within accounts that exhibit buying signals. You will be able to acquire new unknown contacts that do not currently exist in your CRM and match your specified criteria.
- Discover New Engaged Contacts: this Workflow template uncovers new contacts that are engaging with your website and belong to accounts that exhibit buying signals.
The table below includes the RollWorks field mapping available for Contact and Lead creation in Salesforce:
RollWorks Contact/Lead Field | Default Salesforce Contact/Lead Field | Notes |
---|---|---|
RollWorks Sourced | RollWorks Sourced |
Field Mapping mandatory not customizable. This field identifies contacts sourced from RollWorks. This field is set to True if sourced from RollWorks, False otherwise. Learn more |
First Name | First Name | Field Mapping mandatory |
Last Name | Last Name | Field Mapping mandatory |
Business Email | Field Mapping mandatory | |
Company Name | Company Name |
Field Mapping mandatory for Leads. Field Mapping not applicable for Contacts. |
Job Title | Title | Field mapping optional |
Mobile Phone | Mobile Phone | Field mapping optional |
Direct Number | Business Phone | Field mapping optional |
Contact Street | Mailing Street | Field mapping optional |
Contact City | Mailing City | Field mapping optional |
Contact State | Mailing State/Province | Field mapping optional |
Contact Country | Mailing Country |
Field mapping optional This field captures the contact’s location, regardless where the company is located. Currently we only support the creation of contacts located in the US, the company can be located anywhere. |
Seniority Level | N/A | Field mapping optional |
Contact Street 2 | N/A | Field mapping optional |
Contact Zip Code | N/A | Field mapping optional |
Contact Zip Code + 4 Code | N/A | Field mapping optional |
Company City | N/A | Field mapping optional |
Company State | N/A | Field mapping optional |
Department | N/A | Field mapping optional |
Office Street | N/A | Field mapping optional |
Office Street 2 | N/A | Field mapping optional |
Office City | N/A | Field mapping optional |
Office State | N/A | Field mapping optional |
Office Zip Code | N/A | Field mapping optional |
Office Zip Code + 4 Code | N/A | Field mapping optional |
How to configure Contact and Lead Field Mapping
- Log in to RollWorks and Navigate to Settings
- Under Integrations click Salesforce
- Scroll down to the Field Mapping section on the page
- Click Edit next to Salesforce Contact or Salesforce Lead
Mandatory Contact & Lead field mapping
RollWorks Contact/Lead Field | Default Salesforce Contact Lead Field | Notes |
---|---|---|
First Name | First Name | Field Mapping mandatory |
Last Name | Last Name | Field Mapping mandatory |
Business Email | Field Mapping mandatory | |
RollWorks Sourced | RollWorks Sourced | Field Mapping mandatory not customizable. This field identifies contacts sourced from RollWorks. This field is set to True if sourced from RollWorks, False otherwise. Learn more |
Company Name | Company Name |
Field Mapping mandatory for Leads. Field Mapping not applicable for Contacts. |
These RollWorks fields must be mapped to your Salesforce fields as they are essential for record creation used by our Contact Discovery Workflow feature.
By default they are mapped to the default fields for First Name, Last Name, and Email in your Salesforce org, however, you can adjust as needed by selecting a different field from the dropdown under the column Salesforce Fields.
RollWorks Sourced field
This mandatory field mapping allows you to identify in Salesforce which Contacts and Leads records have been created by RollWorks through a Contact Discovery Workflow. This field can help with attribution to RollWorks or to create reports.
When you complete the installation of the RollWorks App for Salesforce, we automatically create a custom field called “RollWorks sourced” in your standard contact and lead records.
When a contact or lead is created by RollWorks through a Contact Discovery Workflow, we will update the custom field “RollWorks Sourced” to True, so that you have an indication of what records have been created by RollWorks.
Your CRM admin can use this field to create logic to assign the newly created leads/contacts to your Sales team.
Optional Contact & Lead field mapping
In addition to the three mandatory fields (First Name, Last Name, and Email) RollWorks can write additional data points to the Contacts and Leads we create in Salesforce through a Contact Discovery Workflow.
Below are the additional RollWorks contact data points available to configure field mapping:
RollWorks Contact/Lead Field | Default Salesforce Contact/Lead Field | Notes |
---|---|---|
Job Title | Title | Field mapping optional |
Mobile Phone | Mobile Phone | Field mapping optional |
Direct Number | Business Phone | Field mapping optional |
Contact Street | Mailing Street | Field mapping optional |
Contact City | Mailing City | Field mapping optional |
Contact State | Mailing State/Province | Field mapping optional |
Contact Country | Mailing Country |
Field mapping optional This field captures the contact’s location, regardless of where the company is located. Currently, we only support the creation of contacts located in the US, while the company can be located |
Seniority Level | N/A | Field mapping optional |
LinkedIn URL | N/A | Field mapping optional |
Contact Street 2 | N/A | Field mapping optional |
Contact Zip Code | N/A | Field mapping optional |
Contact Zip Code + 4 Code | N/A | Field mapping optional |
Company City | N/A | Field mapping optional |
Company State | N/A | Field mapping optional |
Department | N/A | Field mapping optional |
Office Street | N/A | Field mapping optional |
Office Street 2 | N/A | Field mapping optional |
Office City | N/A | Field mapping optional |
Office State | N/A | Field mapping optional |
Office Zip Code | N/A | Field mapping optional |
Office Zip Code + 4 Code | N/A | Field mapping optional |
Fixed Value field mapping
In addition to the RollWorks fields mentioned in this guide, you can map a static or fixed value to a contact/lead field of your choice.
This can be especially useful if you want to specify a lead status, sub-status, or use different fields for lead source or attribution.
The most common use case for this is writing to the field Lead Source denoting that the lead came from RollWorks.
Default Contact Owner & Lead Owner
The Owner for the newly created Contact and Lead records will be the unassigned alias you defined in your Salesforce instance. The default owner cannot be customized.
Click here to learn how to find your unassigned alias in Salesforce.
Managing Changes
- When you change your Contact and Lead field mapping the changes are applied immediately to your active workflows.
- If you make changes to field mappings after a Contact Discovery Workflow has started, the changes will not apply retroactively for contacts and leads created before the change. They will only take effect for any new contacts that are acquired in the next Workflow run after the field mapping changes have been saved in RollWorks.
- Since mappings are stored centrally, any changes you make will apply to contact records being created from anywhere across the RollWorks platform.
Error Handling
- If a default field or a user-selected field becomes unavailable (e.g., if the field name is changed in your Salesforce org), RollWorks will display a warning on both the workflow action slider and the edit mapping slider. This alert helps you identify fields that need attention.
- To resolve issues with unavailable fields, you can either map the field to a different Salesforce field or delete the mapping. Note that you cannot delete or change mappings for mandatory fields.