CRM Integration
Guides on how to setup every CRM Integration
86 articles
HubSpot
HubSpot
- How to Configure Your HubSpot IntegrationComplete guide to configure your HubSpot integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings & Errors in HubSpotWhen configuring Step 2: Field Mapping in your HubSpot integration, each mapped HubSpot field displays a status icon indicating whether the mapping is safe to use. Reviewing these icons before…
- Permissions & Prerequisites for HubSpotWhat you need on the HubSpot side before connecting to Enginy: plan, permissions, authentication, sandbox, and security.
- How the HubSpot integration worksBefore changing any settings, it is worth understanding what the integration does and which decisions you will need to make. If you read this article first, the rest of the…
- Configure Field Mapping and sync directionsField Mapping decides which Enginy property corresponds to each HubSpot property and which direction the data can travel in.
- Connect, reconnect, or disconnect HubSpotFollow these steps to connect HubSpot and understand what Enginy keeps when you authorize the account again.
- How Enginy identifies existing contacts and companiesBefore creating a Contact or Company, Enginy tries to find an existing record in HubSpot. A good matching configuration reduces duplicates.
- Import contacts and companies from HubSpotYou can import Contacts and Companies from HubSpot without the initial connection bringing in the entire portal.
- Owners, activities, tasks, and campaigns in HubSpotUser Mapping and Campaign Mapping control how owners and activity data are written in HubSpot. They do not change the OAuth token scopes.
- Troubleshoot HubSpot integration warnings and errorsThe most common issues during OAuth, Field Mapping, imports, and exports, and what to check for each one.
- Export and keep data synced with HubSpotEnginy can send Contacts and Companies to HubSpot through a manual export, a workflow, or automatic synchronization of already linked records.
Salesforce
Salesforce
- How to Configure Your Salesforce IntegrationComplete guide to configure your Salesforce integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings & Errors in SalesforceWhen configuring Field Mapping in your Salesforce integration, each mapped field displays a status icon indicating whether the mapping is safe to use. Review these icons before saving to avoid…
- Permissions & Prerequisites for SalesforceWhat you need on the Salesforce side before connecting to Enginy: edition, permissions, authentication, sandbox, and security.
- Configure Contact, Lead, and Account in SalesforceThis configuration defines which Salesforce object Enginy uses and how it looks for existing records before creating a new one.
- Configure Field Mapping in SalesforceField Mapping defines what information Enginy sends to Salesforce and which field it should be stored in.
- Connect, reconnect, or disconnect SalesforceThe connection uses OAuth. You sign in directly to Salesforce, authorize Enginy, and Salesforce grants the permissions belonging to the connected user.
- Export Contacts, Leads, and Accounts to SalesforceEnginy can create new records in Salesforce or update existing ones, checking first whether a match exists according to the configured identifiers.
- How Enginy identifies existing records in SalesforceBefore creating a Contact, Lead or Account, Enginy tries to find an existing record. Enginy only searches within the target object.
- Import Contacts, Leads, and Accounts from SalesforceEnginy lets you import records from Salesforce through Salesforce Search, a Salesforce List View, or a Salesforce Report.
- Owners, Campaign Mapping, and activities in SalesforceSalesforce distinguishes between the user making the API calls and the owner assigned to each record. Covers User Mapping, Campaign Mapping and Campaign member sync.
- Troubleshoot Salesforce integration warnings and errorsWarnings in Salesforce Setup flag a configuration that may fail, but not all of them block saving. Common Salesforce error codes and what to check.
Pipedrive
Pipedrive
- How to Configure Your Pipedrive IntegrationComplete guide to configure your Pipedrive integration in Enginy: sync settings, field mapping (including Leads), campaign mapping, and user mapping.
- How to Import Contacts and Companies from PipedriveSearch or use saved lists to import contacts and companies directly from Pipedrive into Enginy, without CSV exports or manual work.
- How to Fix Field Mapping Warnings and Errors in PipedriveWhen configuring Step 2: Field Mapping in your Pipedrive integration, each mapped Pipedrive field displays a status icon indicating whether the mapping is safe to use. Reviewing these icons before…
- Permissions & Prerequisites for PipedriveWhat you need on the Pipedrive side before connecting to Enginy: plan, permissions, authentication, sandbox, and security.
- Connect, reconnect, or disable PipedriveManage the Pipedrive connection from Integrations. The connected account becomes the Integration user and determines what Enginy can see and change.
- Configure Field Mapping and overwrite rules in PipedriveField Mapping tells Enginy what data to send to Pipedrive Persons and Organizations, and what happens when the destination field already has a value.
- Configure matching and associations in PipedriveMatching defines how Enginy recognizes the Persons and Organizations that already exist in Pipedrive before exporting.
- Export contacts and companies and create optional Leads in PipedriveEnginy contacts are exported as Persons and companies as Organizations. You can optionally create additional Leads.
- Import contacts and companies from PipedriveImport Persons and Organizations from Pipedrive without preparing a CSV file, using a search or a saved filter.
- Owners, Campaign Mapping, Notes, Activities, and Tasks in PipedriveThe integration can assign Owners, log messages as Notes or Activities, and write campaign information into Pipedrive fields.
- Troubleshoot Pipedrive integration warnings and errorsConfiguration warnings flag possible problems, but not all of them block saving. What each icon means and how to resolve common errors.
Dynamics
Dynamics
- How to Configure Your Dynamics IntegrationComplete guide to configure your Microsoft Dynamics 365 integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings and Errors in DynamicsWhen configuring Field Mapping in your Dynamics 365 integration, each mapped field displays a status icon indicating whether the mapping is safe to use. Review these icons before saving to…
- Permissions & Prerequisites for Dynamics 365What you need on the Dynamics 365 side before connecting to Enginy: licensing, permissions, authentication, sandbox, and security.
- Troubleshoot Microsoft Dynamics integration warnings and errorsMost Dynamics issues come down to permissions, Field Mapping, matching, or authentication. Start with the exact message and the affected entity type.
- Owners, User Mapping, and activities in Microsoft DynamicsUser mapping connects Enginy people with Dynamics users. It assigns owners and, in certain operations, writes on behalf of the corresponding user.
- Import Contacts, Leads, and Accounts from Microsoft DynamicsEnginy can import records using filters created in Enginy or from system views and personal views saved in Dynamics.
- Connect, reconnect, or disconnect Microsoft DynamicsConnect Dynamics with a user who has access to the environment and records you will use. The integration inherits that user's security limits.
- Export and update records in Microsoft DynamicsEnginy can create and update Dynamics Contacts or Leads, Accounts, and their associations, depending on entity, matching, Field mapping, and permissions.
- How Enginy identifies existing Contacts, Leads, and Accounts in DynamicsBefore creating a record, Enginy tries to find out whether it already exists in Dynamics. Accurate matching reduces duplicates.
- Configure Microsoft Dynamics: entities, associations, and Field MappingBefore configuring fields, decide which Dynamics entity will represent people. That choice affects schema, matching, imports, exports, and permissions.
Zoho
Zoho
- How to Configure Your Zoho IntegrationComplete guide to configure your Zoho CRM integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings and Errors in ZohoWhen configuring Step 2: Field Mapping in your Zoho CRM integration, each mapped Zoho field displays a status icon indicating whether the mapping is safe to use. Reviewing these icons…
- Permissions & Prerequisites for ZohoWhat you need on the Zoho side before connecting to Enginy: plan, permissions, authentication, sandbox, and security.
- Campaign Mapping, User Mapping, and activities in ZohoCampaign Mapping writes Campaign and engagement information into Zoho fields. User Mapping chooses the Owner. Neither widens permissions.
- Configure Field Mapping and resolve warnings in ZohoField Mapping connects Enginy fields with the Contacts, Leads and Accounts fields in Zoho, and controls whether Enginy can replace an existing value.
- Configure identifiers, matching, and associations in ZohoIdentifiers tell Enginy how to look for an existing record in Zoho before creating a new one. Reviewing them reduces duplicates.
- Connect, reconnect, disconnect, and revoke ZohoThe connection is made through OAuth from the Integrations page. The user who completes the authorization becomes the Integration user.
- Export Contacts, Leads, and Accounts to ZohoYou can export people as Contacts or Leads. Enginy Companies are exported as Zoho Accounts.
- Import Contacts and Accounts from ZohoImport Contacts and Accounts from Zoho without preparing a CSV file. Contacts become Enginy contacts and Accounts become Companies.
- Troubleshoot common Zoho integration issuesStart with Activity > Prospecting when an export fails. Covers permissions, expired authentication, picklists, Custom Views and API limits.
Attio
Attio
- How to Configure your Attio Integration (Beta)Configure your Attio integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings and Errors in AttioWhen configuring Step 2: Field Mapping in your Attio integration, each mapped Attio field displays a status icon indicating whether the mapping is safe to use. Reviewing these icons before…
- Permissions & Prerequisites for AttioWhat you need on the Attio side before connecting to Enginy: plan, permissions, authentication, sandbox, and security.
- Understanding People, Companies, Lists, and Entries in AttioAttio organizes data with Objects, Records, Attributes, Lists and Entries. Understanding the difference avoids many mapping mistakes.
- Troubleshoot Attio integration warnings and common issuesMost Attio problems come down to a connection that needs renewing, imprecise matching, an incompatible field, or a required List attribute.
- Import People and Companies from AttioYou can import People and Companies using filters or from an existing Attio List.
- Export People and Companies to Attio and add them to ListsAn export can create or update a Person or Company record and, if you choose, add that record to an Attio List. They are separate operations.
- Connect, reconnect, disconnect, and revoke AttioThe connection is made through OAuth. Attio handles the sign-in and the consent, so you do not enter your password in Enginy.
- Configure matching and Field Mapping in AttioMatching decides whether a Record already exists. Field Mapping decides which values are written. They serve different purposes.
- Campaign Mapping and Notes in AttioEnginy can send Campaign information into a Person's attributes and save messages as Notes in Attio. These are two different features.
TribeCRM
TribeCRM
- How to Configure Your TribeCRM IntegrationComplete guide to configure your TribeCRM integration in Enginy: sync settings, field mapping, campaign mapping, and user mapping.
- How to Fix Field Mapping Warnings and Errors in TribeCRMWhen configuring Step 2: Field Mapping in your TribeCRM integration, each mapped TribeCRM field displays a status icon indicating whether the mapping is safe to use. Reviewing these icons before…
- Permissions & Prerequisites for TribeCRMWhat you need on the TribeCRM side before connecting to Enginy: plan, permissions, authentication, sandbox, and security.
- Campaign Mapping, conversations, Activities and Owners in TribeCRMEnginy can store Campaign and conversation data in TribeCRM. Conversations are logged as Activities, not as Notes.
- Configure and sync Tasks with TribeCRMEnginy can create, update and close Tasks in TribeCRM. The sync applies to Tasks that Enginy manages.
- Configure Field Mapping, overwrite and warnings in TribeCRMField Mapping tells Enginy which Enginy field corresponds to each TribeCRM field, and what happens when TribeCRM already holds a value.
- Configure matching, types and associations in TribeCRMBefore importing or exporting, Enginy needs to know which record types to use and how to recognise a Contact or Organization that already exists.
- Connect, reconnect, disconnect and revoke TribeCRMYou start the process in Enginy, authorise access in TribeCRM, and come back to Enginy to finish the setup.
- Export Contacts and Organizations to TribeCRMEnginy can create and update TribeCRM Contacts and Organizations. A new Contact needs an associated Organization.
- Import Contacts and Organizations from TribeCRMYou can bring in Contacts and Organizations through CRM Search. The integration does not let you pick a TribeCRM List as the source.
- Troubleshoot common TribeCRM integration issuesStart by reviewing the OAuth connection, the permissions of the user who authorised it, and the report from the last operation.
- Understand Persons, Organisations, Contact Persons, Relationships and ActivitiesTribeCRM keeps the core information about a person or organisation separate from the relationship that entity has with your business.
Odoo
Odoo
- Chatter, tasks, and owners in OdooCampaign messages land in the Odoo chatter, Enginy tasks become Odoo activities, and campaign fields no longer depend on message logging.
- Configure Field Mapping in OdooTwo sync options rather than five, two tabs rather than three, and the required-fields rule that decides which records Enginy may create.
- Connect, reconnect, or disconnect OdooFill in four fields to connect. Reconnecting after a key expires keeps your whole configuration.
- Contacts, companies, and leads: what Enginy syncs in OdooOdoo keeps people and companies in one model, and your workspace commits to either contacts or leads. Understanding this answers half the questions.
- Export contacts, companies, and leads to OdooWhat gets written, how Enginy isolates a failing record so the rest still land, and what happens when the only matching lead is lost.
- How Enginy identifies existing records in OdooThe matching rules for contacts, companies and leads, why archived records count, and what to check when duplicates appear.
- Import contacts, companies, and leads from OdooImport by filters with a preview, or by tag. Lost leads come in too, and re-importing updates rather than duplicates.
- Odoo and Enginy: how the integration worksConnect Odoo to Enginy to import data from your CRM and send back the information you work on in Enginy.
- Requirements, Odoo plan, and API key for connectingWhat you need on the Odoo side before connecting: the right plan, a dedicated user, and an API key rather than a password.
- Troubleshoot common Odoo integration issuesMost Odoo issues come down to permissions or an expired key. Start with the Permissions tab, then work through connection, import and export.