Attio is a modern CRM built around flexible data structures and relationship intelligence. This article walks you through how to connect Attio to Enginy and configure the integration so you can synchronize contacts and companies, map fields, and track campaign activity.
Note: The Attio integration is currently in Beta. Some features may change as the integration evolves. If you experience any issues, contact your Account Manager.
To set up your Attio integration:
Go to Integrations and open the All tab (or the Disabled tab).
Locate the Attio (Beta) card and enable it using the toggle switch.
Click the Configure button on the Attio 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 Attio records to prevent duplicates and ensure data integrity. A sync means Enginy compares its records against Attio 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 Attio.
Option | Matching Logic |
First name + Last name + Company name | A contact matches when all three fields are the same in both Enginy and Attio. |
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
The Company Identifier setting lets you choose how Enginy determines whether a company already exists in your Attio.
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 the General section, you will find two toggles that control how associations are handled during export:
When exporting contacts, associate them with companies in Attio: If enabled, Enginy will automatically link exported contacts to their corresponding companies in Attio.
When exporting companies, associate them with contacts in Attio: If enabled, Enginy will automatically link exported companies to their related contacts in Attio.
Step 2: Field Mapping
This step configures which Enginy fields map to which Attio 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 Attio field. |
Fixed Value Fields | Fields that always export with the same static value. For example, create an Attio 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 Attio 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 Attio (for example, an email-sent event, a LinkedIn message, or a Task log). Just select the Attio field and then set the Value to export. Only one can be set. |
Warning: Do not 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 is mapped the same in both places.
In each Attio field mapping dropdown, you will 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 and has no potential problems. |
Yellow exclamation | The field types in Enginy and Attio may be incompatible (e.g., an Enginy Text field mapped to an Attio Enumeration field). |
Red X | The mapping cannot be applied because the types do not match — or because the Attio field is read-only and cannot be updated. |
Note: Some yellow warning icons appear when the selected Attio 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 Attio 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 Attio fields:
Option | Behaviour |
Enginy overwrites Attio | Changes in Enginy automatically overwrite the corresponding fields in Attio. |
Sync with Attio | Data only syncs automatically when the destination field is empty, either in Enginy or Attio, preventing overwriting existing values. |
Step 3: Campaign Mapping (Optional)
This step lets you sync campaign-specific properties to Attio. 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 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
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 Attio 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). The Identities Mapping section links each Enginy identity to an Attio user.
When a campaign — which is always linked to an identity — performs a sync or export, the Attio activity log shows the associated Attio user as the one who executed the action.
Users Mapping
The Users Mapping section links an Enginy user account to an Attio 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 Attio users have different permission levels, this association respects those limits. A record exported by an Enginy user is owned by the mapped Attio user and is governed by that user's permissions in Attio.
Default CRM Owner
This mapping sets a default Attio owner (contact or company owner) for exports performed by an Enginy user who is not mapped in User Mapping.
Save Your Configuration
After completing all four steps, click Update to save your Attio configuration.