HubSpot is a full-featured CRM with marketing, sales, and service hubs. Follow the steps below to connect HubSpot to Enginy and configure the integration.
To set up your HubSpot integration:
Go to Integrations and open the All tab (or the Disabled tab).
Locate the HubSpot card and enable it using the toggle switch.
Click the Configure button on the HubSpot 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 HubSpot records to prevent duplicates and ensure data integrity. A sync means Enginy compares its records against HubSpot 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 HubSpot.
Option | Matching Logic |
First name + Last name + Company name | A contact matches when all three fields are the same in both Enginy and HubSpot. |
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 HubSpot.
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 HubSpot 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 HubSpot field. |
Fixed Value Fields | Fields that always export with the same static value. For example, create a HubSpot field called "Source" and set its fixed value to "Enginy" so every exported record is tagged with its origin. |
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 HubSpot 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 HubSpot (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 HubSpot 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 HubSpot may be incompatible (e.g., an Enginy Text field mapped to a HubSpot Enumeration field). |
Red X | The mapping can't be applied because the types don't match — or because the HubSpot field is read-only and can't be updated. |
Note: Some yellow warning icons appear when the selected HubSpot 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 (using 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 HubSpot dropdown values — using the internal option names (not the labels).
If it is a Fixed value field or an Engagement field, input the exact internal name in the mapped Value to export in the Field mapping integration's setting.
If it is a Manual export field, input the exact internal name at the moment of the export.
Mapping Options
Here are the available mapping types between Enginy and your HubSpot fields:
Option | Behaviour |
Bi-directional sync | Changes sync both ways automatically. |
HubSpot overwrites Enginy | Changes in HubSpot automatically overwrite the corresponding fields in Enginy. |
Enginy overwrites HubSpot | Changes in Enginy automatically overwrite the corresponding fields in HubSpot. |
Sync if value is empty | Data only syncs automatically when the destination field is empty, either in Enginy or HubSpot, 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 HubSpot.
| 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.
You can also: overwrite existing values for any field mapping (in either the Contacts or Companies tab), overwrite CRM owner, 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 HubSpot. 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. |
|
Email
Properties related to the campaign email step 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
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 HubSpot 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 HubSpot user.
When a campaign — which is always linked to an identity — performs a sync or export, the HubSpot activity log shows the associated HubSpot user as the one who executed the action.
Users Mapping
Users Mapping links an Enginy user account to a HubSpot 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 HubSpot users have different permission levels, this association respects those limits. A record exported by an Enginy user is owned by the mapped HubSpot user and is governed by that user's permissions in HubSpot.
Default CRM owner
This mapping sets a default HubSpot 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 HubSpot configuration.