Connect your existing tech stack to Enginy so you can synchronize data, enrich contacts, automate exports, and streamline team communication — all from a single hub.
Table of Contents
Overview
All Tab
Enabled Tab
Disabled Tab
Available Integrations
CRM
Data Enrichment
AI Enrichment
Import Sources
Communication
Configure Your CRM
Step 1: Input / Sync Mapping
Integration User
Contact Identifier
Company Identifier
General
Step 2: Export Mapping
Field Types
Mapping Options
Association Type
Step 3: Campaign Mapping (Optional)
Sequence
Email
General
Conversation Tags
Step 4: User Mapping
Identities Mapping
Users Mapping
Default CRM owner
Save Your Configuration
Troubleshooting
FAQs
Overview
The Integrations page is organized into three tabs that give you a clear view of every available connection and its current status.
All Tab
The All tab displays every integration Enginy supports, grouped by category (CRM, Data Enrichment, AI Enrichment, Import Sources, and Communication). Use this tab to browse, enable, or configure any integration.
Note: To enable any integration, please contact your Account Manager if it isn’t available to activate in your workspace in order to enable its API.
Enabled Tab
The Enabled tab shows only the integrations you have currently turned on. This is a quick way to audit your active connections at a glance.
Disabled Tab
The Disabled tab shows all integrations that are not yet enabled. It is a useful starting point when you want to expand your connected tool set.
Important: You can only have one CRM integration active at a time. If you want to enable a new CRM, you must first disable the currently active one.
Available Integrations
CRM
Connect a CRM to synchronize and export contacts and companies between Enginy and your CRM of choice.
Platform | Description |
HubSpot | Full-featured CRM with marketing, sales, and service hubs. |
Dynamics | Microsoft Dynamics 365 CRM. |
Pipedrive | Sales-focused CRM built around pipeline management. |
Salesforce | Enterprise CRM platform. |
TribeCRM | CRM designed for relationship-driven sales teams. |
Zoho | CRM suite with sales automation and analytics. |
Custom CRM (Beta) | Connect your own CRM using API key authentication. |
Note: All CRM integrations require an initial setup configuration, as explained in this article. It only varies slightly for Pipedrive: in step 2 of the configuration, you can also map Leads.
Data Enrichment
Plug in your data-enrichment tools to optimize outreach, verify data, and qualify leads.
Tool | What It Does |
Apollo | Lead enrichment, email discovery, and engagement tracking to optimize outreach. |
Cognism | Lead generation platform with global databases to identify and connect with prospects. |
Datagma | AI-based platform to enrich business insights and help qualify leads effectively. |
Dropcontact | Updates, enriches, and verifies contact and company data directly within CRMs. |
Hunter | Finds and verifies professional email addresses for B2B outreach campaigns. |
Kaspr | Retrieves contact data (emails and phone numbers) from LinkedIn for prospecting. |
Lusha | Enriches contact data with verified emails, direct dials, and company details. |
ZoomInfo | Business intelligence tool that offers comprehensive databases to find and qualify leads. |
Note: Each of these integrations can be activated by simply pasting the API key.
e.g.:
AI Enrichment
If you have an API-enabled Enterprise account with any of these AI providers, you can connect it to Enginy. This way, AI variables will use your provider tokens instead of Enginy Credits when generating data.
Tool | What It Does |
Anthropic | Powers Claude models for safe, helpful AI assistance. |
Google AI | Powers Gemini models for multimodal AI tasks. |
OpenAI | Powers GPT models for text generation, reasoning, and code tasks. |
xAI | Powers Grok models with real-time knowledge and unique personality. |
Note: If you don’t have an API key from any of these providers, Enginy can provide the AI service for you — usage will be charged in Enginy Credits.
Import Sources
Tool | What It Does |
TheirStack | Aggregates and imports company data from multiple platforms. You can connect your own TheirStack account. If you do not have one, Enginy's subscription is used and credits are deducted from your account when importing companies. |
TheirStack integration can be activated by simply pasting the API key.
Communication
Tool | What It Does |
Slack | Connect Slack to enable team communications and workflow notifications from Enginy. |
Slack integration can be activated by connecting via Oauth.
Configure Your CRM
To set up your CRM integration:
Go to Integrations and open the All tab (or the Disabled tab).
Locate the CRM card you want to connect (for example, HubSpot).
Enable the integration using the toggle switch on the card.
Click the Configure button on the CRM card.
A floating setup window opens with four sequential steps.
Step 1: Sync Configuration
This step defines how Enginy matches contacts and companies with your CRM records to prevent duplicates and ensure data integrity. A sync means Enginy compares its records against CRM 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 CRM.
Option | Matching Logic |
First name + Last name + Company name | A contact matches when all three fields are the same in both Enginy and the CRM. |
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 CRM.
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 HubSpot: If enabled, Enginy will automatically link exported contacts to their corresponding companies in HubSpot.
When exporting companies, associate them with contacts in HubSpot: If enabled, Enginy will automatically link exported companies to their related contacts in HubSpot.
Step 2: Field Mapping
This step configures which Enginy fields map to which CRM fields when exporting data. The setup is split into two tabs — Contacts 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 the Add field button to add a new mapping: select the Enginy field first, then select the corresponding CRM field. |
Fixed Value Fields | Fields that always export with the same static value. For example, create a CRM field called "Source" and set its fixed value to "Enginy" so every exported record is tagged with its origin. Click the Add field button to add a new mapping: select the Enginy field first, then select the corresponding CRM field. |
Manual Export Fields | Fields whose value you define specifically at the time of export. Click the Add field button to add a new mapping: select the CRM field which will be asked to be set when exporting. As many as you want. |
Engagement Fields | Fields that are populated when an Activity is created in the CRM (for example, an email-sent event, a LinkedIn message, or a Task log). Just select the HubSpot field and then 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 CRM 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 the CRM may be incompatible (e.g., an Enginy Text field mapped to a CRM Enumeration field). |
Red X | In these cases, the mapping can’t be applied because the types don’t match — or because the CRM field is read-only and can’t be updated (e.g., an Enginy Text field mapped to a CRM Number field, or a read-only CRM field). |
Note: Some yellow warning icons appear when the selected CRM field is an enumeration (dropdown) field. In this case, your Enginy text field can still export successfully as long as the value you send matches one of the allowed dropdown options (but internal names, not label names).
Workaround: Create an AI Variable with output type = One off, and define the output tag options to exactly match the CRM dropdown values — using the internal option names (not the labels). This ensures the exported value is accepted and the export completes successfully. Additional considerations:
If is a Fixed value field or an Engagement field just input the exact internal name in the mapped Value to export in the Field mapping integration's setting.
If is a Manual export field just input the exact internal name at the moment of the export.
Mapping Options
Here are the available mapping types between Enginy and your CRM fields:
Option | Behaviour |
Bi-directional sync | Changes sync both ways automatically. |
[CRM] overwrites Enginy | Changes in [CRM] automatically overwrite the corresponding fields in Enginy. |
Enginy overwrites [CRM] | Changes in Enginy automatically overwrite the corresponding fields in [CRM]. |
Sync if value is empty | Data only syncs automatically when the destination field is empty, either in Enginy or [CRM], preventing overwriting existing values. |
Sync deactivated | No automatic sync. You’ll need to manually export or run a sync to apply changes. |
Association Type
The Association Type setting controls the relationship between a contact and a company inside the CRM.
Option | Behavior |
Add as additional association | Adds the association without changing existing ones. |
Add association as Primary | Sets the new association as the primary relationship. |
Associate as Primary and remove previous associations | Sets the new association as primary and deletes all previous associations. |
Warning: The "Associate as Primary and remove previous associations" option is not recommended unless you are certain you want to erase all prior associations for the record. Using it can result in data loss if historical relationships exist.
When exporting manually a contact or company, you can choose the Association Type in the export modal. The integration settings define the default association type, but you can override it for each individual manual export in the export modal.
You can also: overwrite existing values for any field mapping (in either the Contacts or Companies tab), overwrite CRM owner (who register the export in CRM), optionally set Manual export field values, and enable Export associated companies (or Export associated contacts when manually exporting a company).
Step 3: Campaign Mapping (Optional)
This step lets you sync campaign-specific properties to your CRM. These are not standard list fields; they are properties tied to campaign activity.
Sequence
Properties related to the campaign 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. |
|
Properties related to the campaign email steps messages:
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
Properties under general aspects of campaigns:
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
Properties related to 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 CRM 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 CRM user.
When a campaign — which is always linked to an identity — performs a sync or export (Campaign mappings export types), the CRM activity log shows the associated CRM user as the one who executed the action.
Users Mapping
Users Mapping links an Enginy user account to a CRM 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 CRM users have different permission levels, this association respects those limits. A record exported by an Enginy user is owned by the mapped CRM user and is governed by that CRM user's permissions.
Default CRM owner
This mapping sets a default CRM 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 CRM configuration.
Troubleshooting
Symptom / Error | Cause | Resolution |
Export fails with field-mapping errors | A Company field is mapped in the Contacts tab (or vice versa). | Open Step 2: Export Mapping, verify that each tab only contains fields belonging to its own object type, and remove any misplaced mappings. |
Duplicate records appear in the CRM after export | The identifier configured in Step 1 does not uniquely match existing records. | Review and tighten the Contact or Company Identifier. Consider using the LinkedIn profile URL option for contacts or enabling Include any domain extension for companies. |
Cannot enable a second CRM | Enginy allows only one active CRM at a time. | Go to the Enabled tab, disable the current CRM, then enable and configure the new one. |
CRM activity log shows the wrong user | Identities or Users Mapping is not configured correctly in Step 4. | Open Step 4: User Mapping and verify that each Enginy identity and user is linked to the correct CRM user. |
FAQs
Q1: Can I connect more than one CRM at the same time?
No. Enginy supports only one active CRM integration at a time. If you want to switch to a different CRM, disable the current one first, then enable and configure the new one.
Q2: What happens if I do not configure Export Mapping — will my data still sync?
Step 1 (Sync Configuration) controls how records are matched, but without Step 2 (Field Mapping) Enginy will not know which fields to push to your CRM. Even not which ones to pull from CRM. You must configure at least the essential field mappings before exporting or syncing.
Q3: I do not have my own AI or TheirStack account. Can I still use those features?
Yes. For AI, Enginy provides its own credits for AI variable outputs if you do not connect a personal subscription. For TheirStack, Enginy's subscription is used by default and credits are deducted from your plan when importing companies.
Q4: What does the "Overwrite existing value" checkbox do in a manual Export to CRM?
When checked, the value in Enginy replaces whatever value currently exists in the corresponding CRM field during export. When unchecked, the existing CRM value is preserved and only empty fields are populated.
Q5: Why should I avoid the "Associate as Primary and remove previous associations" option?
This option deletes all existing associations for the record before setting the new one as primary. If you have historical relationships or multiple valid associations in your CRM, using this option can result in data loss. Use it only when you are certain the new association should be the sole relationship.