Salesforce is an enterprise CRM platform. Follow the steps below to connect Salesforce to Enginy and configure the integration.
To set up your Salesforce integration:
Go to Integrations and open the All tab (or the Disabled tab).
Locate the Salesforce card and enable it using the toggle switch.
Click the Configure button on the Salesforce card.
A floating setup window opens with four sequential steps.
Important: You can only have one CRM integration active at a time. If another CRM is already active, disable it first.
Step 1: Sync Configuration
This step defines how Enginy matches contacts and companies with your Salesforce records to prevent duplicates and ensure data integrity. A sync means Enginy compares its records against Salesforce records using the identifiers you configure here.
Integration User
It shows whose email address is the API integration user.
Contact Identifier
Choose how Enginy determines whether a contact already exists in your Salesforce.
Option | Matching Logic |
First name + Last name + Company name | A contact matches when all three fields are the same in both Enginy and Salesforce. |
LinkedIn profile URL OR First name + Last name + Company name | A contact matches if the LinkedIn profile URL is the same or all three name/company fields match. |
Custom Mapping | Opens a pop-up where you define custom conditions using AND/OR logic (for example, match by First Name AND Last Name, OR by Professional Email). |
Company Identifier
Choose how Enginy determines whether a company already exists in your Salesforce.
Option | Matching Logic |
Domain | Matches on the company domain (e.g., |
Domain or Company Name | Matches if either the domain or the company name is the same. |
Custom Mapping | Opens a pop-up where you define custom conditions (for example, match by Domain OR Company LinkedIn URL). |
General
Under General, you'll find two toggles that control how associations are handled during export:
When exporting contacts, associate them with companies in Salesforce: If enabled, Enginy will automatically link exported contacts to their corresponding companies in Salesforce.
When exporting companies, associate them with contacts in Salesforce: If enabled, Enginy will automatically link exported companies to their related contacts in Salesforce.
Salesforce specific configuration
Important: This toggle is labeled "Not recommended". Enabling it can create duplicate records in your Salesforce org if the same contact is exported more than once. Leave it off unless you have a specific reason to bypass Salesforce's duplicate detection.
When configuring Salesforce as your CRM, you will see an additional section called Salesforce specific configuration at the bottom of the setup. This section contains the following option:
Create/Update records on duplicate warnings — This toggle is labeled "Not recommended". Contact your Enginy workspace admin or the Enginy support team before enabling this option.
Step 2: Field Mapping
This step configures which Enginy fields map to which Salesforce fields when exporting data. The setup is split into three tabs — Contacts, Leads and Companies — and the mapping configuration works the same way in both.
Field Types
Field Type | Description |
Enginy Fields | Standard fields from your contact or company lists (e.g., Phone Number, Job Title). Click Add field to add a new mapping: select the Enginy field first, then the corresponding Salesforce field. |
Fixed Value Fields | Fields that always export with the same static value. For example, create a field called "Source" with fixed value "Enginy" so every exported record is tagged with its origin. |
Manual Export Fields | Fields whose value you define at the time of export. Click Add field, select the Salesforce field to be set when exporting. As many as you want. |
Engagement Fields | Fields populated when an Activity is created in Salesforce (e.g., an email sent, a LinkedIn message, or a Task log). Select the Salesforce field and set the Value to export. Only one can be set. |
Warning: Don't map a Company field in the Contacts tab (or a Contact field in the Companies tab). This can cause export errors. If you must map the same field in both tabs, make sure it's mapped the same in both places.
In each Salesforce field mapping dropdown, you'll see small status icons indicating whether the mapping is supported, not supported, or supported with limitations / a workaround.
Icon | Meaning |
Blue check | The mapping is okay, has no potential problems. |
Yellow exclamation | The field types in Enginy and Salesforce may be incompatible (e.g., an Enginy Text field mapped to a Salesforce Enumeration field). |
Red X | The mapping can't be applied because the types don't match — or because the Salesforce field is read-only and can't be updated. |
Note: Some yellow warning icons appear when the selected Salesforce field is an enumeration (dropdown) field. Your Enginy text field can still export successfully as long as the value matches one of the allowed dropdown options (using internal names, not label names).
Workaround: Create an AI Variable with output type = One off and define output tag options to exactly match the Salesforce dropdown values — using internal option names (not labels).
Mapping Options
Option | Behaviour |
Enginy overwrites Salesforce | Changes in Enginy automatically overwrite the corresponding fields in Salesforce. |
Sync with Salesforce | Data only syncs automatically when the destination field is empty, preventing overwriting existing values. |
Export Options
You can export both contacts and companies from Enginy to Salesforce. To export records:
Select the records you want to export in your list (from the Contacts or Companies tab).
Click Export in the bottom bar, then select Export to CRM.
The Export to CRM modal opens with the following options:
Lead / Contact toggle (contacts only) — In the top-right corner of the modal, you can switch between exporting the selected records as a Lead or as a Contact in Salesforce. This toggle is not available when exporting companies, as companies are always exported as Account records.
Owner — Select a Salesforce user as the owner of the exported records. This field is optional — if left empty, the default owner from your User Mapping configuration will be used. You can also check Overwrite existing value to replace the current owner in Salesforce.
Review Mapping — Click this button to review your field mapping configuration before confirming the export.
Click Export to confirm.
Note: When you export both a contact and its associated company, Enginy automatically links the Contact to its Account in Salesforce.
Step 3: Campaign Mapping (Optional)
This step lets you sync campaign-specific properties to Salesforce. These are not standard list fields; they are properties tied to campaign activity.
Sequence
Property | What It Contains | Example Value |
Campaign Sequence Details | The steps included in the campaign. |
|
Campaign Engagement Status | The current status of each lead in the campaign. |
|
Sequence Status | The overall status of the campaign sequence for the lead. |
|
Campaign Reply Analysis | Indicates per-message whether the lead replied to each automated message. |
|
Email
Property | What it Contains | Example Value |
Campaign Opens | Total number of times a lead has opened one or more emails in the campaign. |
|
Campaign Clicks | Total number of times a lead has clicked a link in campaign emails. |
|
Campaign Open Analysis | Indicates per-message whether the contact opened that specific email. |
|
Campaign Click Analysis | Indicates per-message whether the contact clicked a link in that specific email. |
|
General
Property | What it Contains | Example Value |
Campaign | All Campaign names the contact has been added to. |
|
Senders | All sender names that have contacted the contact. |
|
Activities | All activities that have occurred with the contact. |
|
Conversation Tags
Property | What it Contains | Example Value |
Conversation Tags | All conversation tags applied to the contact (comma-separated). |
|
Conversation Tags Categories | Categories of conversation tags: POSITIVE, NEUTRAL, NEGATIVE (comma-separated). |
|
Step 4: User Mapping
This final step defines the associations between Enginy users/identities and Salesforce users so that exports and activity logs are attributed to the correct people.
Identities Mapping
An Identity in Enginy is the profile that runs a campaign (for example, a LinkedIn profile or an email sender). Identities Mapping links each Enginy identity to a Salesforce user.
When a campaign performs a sync or export, the Salesforce activity log shows the associated Salesforce user as the one who executed the action.
Users Mapping
Users Mapping links an Enginy user account to a Salesforce user. This sets the default owner for any record exported by that user — even for automatic exports via field mappings, not just manual exports.
If Salesforce users have different permission levels, this association respects those limits. A record exported by an Enginy user is owned by the mapped Salesforce user and governed by that user's permissions.
Default CRM owner
This mapping sets a default Salesforce owner (contact or company owner) for exports performed by an Enginy user who isn't mapped in User Mapping.
Save Your Configuration
After completing all four steps, click Update to save your Salesforce configuration.