Cognism Integrations Overview

This article provides an overview of the CRM and sales engagement tools that integrate with Cognism. It explains the objects Cognism can map to in each platform and the permissions required to enable data sync.

You can use this article to understand how Cognism works with each integration before configuring field mappings or exports.

Cognism’s supported integrations

Cognism integrates with the following platforms. Select an integration to view the supported objects and required permissions.

Jump to section

• Salesforce
• HubSpot
• Outreach
• Salesloft
• Pipedrive
• Bullhorn
• Microsoft Dynamics 365
• Zapier

What are objects in a CRM?

Objects are the core data records used by CRMs and sales engagement tools. They represent entities such as people, companies, and activities.

Each platform defines objects differently. Cognism maps its data to the appropriate objects in each integration so records can be created, updated, and deduplicated correctly.

Some platforms also allow exported records to be added to campaigns, sequences, or cadences during export.

Objects and permissions

To map Cognism data to objects in an integrated platform, specific permissions are required.

These permissions allow Cognism to:

• Create and update records
• Check for existing records to reduce duplicates
• Display sync status indicators in Cognism

Permissions are configured in the connected platform, not in Cognism.

Salesforce

Supported objects

• Accounts: Companies or organisations 
• Contacts: Individuals associated with accounts 
• Leads: Unqualified potential customers 

Required permissions

Admin or integration user (to connect Cognism):

• API enabled
• Manage connected apps
• View setup and configuration
• Customise application

User permissions (to export data):

• Read, create, and edit access for Leads, Contacts, and Accounts

Note

• Companies are mapped as Accounts from Cognism to Salesforce. 
• Contacts are mapped as Leads or Contacts. 
• Exported contacts can optionally be added to Salesforce Campaigns. 

HubSpot

Supported objects

• Contacts: Individuals and leads 
• Companies: Organisations associated with contacts 

Required permissions

Admin or integration user (to connect Cognism):

• App marketplace access enabled
• Edit property settings

User permissions (to export data):

• View and edit access for Contacts and Companies

Note

• Companies are mapped as Companies from Cognism to HubSpot. 
• Contacts are mapped as Contacts. 

Outreach

Supported objects

• Prospects: Individuals targeted for outreach 
• Accounts: Companies associated with prospects 

Required permissions

• Prospects: all
• Accounts: all
• Phone numbers: all
• Sequences: all
• Mailboxes: all
• Sequence states: all

Note

• Companies are mapped as Accounts from Cognism to Outreach. 
• Contacts are mapped as Prospects. 
• Exported prospects can be added to Outreach Sequences. 

Salesloft

Supported objects

• People: Individuals targeted for outreach 
• Accounts: Companies associated with people 

Required permissions

• Accounts
• Activities
• Admin
• Cadences
• Calls
• CRM
• Dialer recordings
• Emails
• External access
• External ID configuration
• Groups
• Notes
• Notifications
• People
• Signals
• Tasks
• Workflow

Note

• Companies are mapped as Accounts from Cognism to Salesloft. 
• Contacts are mapped as People. 
• Exported people can be added to Salesloft Cadences. 

Pipedrive

Supported objects

• Contacts: Individuals associated with deals or organisations 
• Organisations: Companies associated with contacts and deals 

Required permissions

• Access to basic information
• Full access to activities
• Full access to contacts
• View recent account activity
• Search all data
• Full access to call logs

Note

• Companies are mapped as Organisations from Cognism to Pipedrive. 
• Contacts are mapped as Contacts. 

Bullhorn

Supported objects

• Leads: Early-stage opportunities 
• Contacts: Individuals associated with companies 
• Candidates: Job seekers 
• Companies: Clients or suppliers 

Required permissions

• Access to leads and opportunities
• Access to contacts
• Access to candidates
• Access to companies

Note

• Companies are mapped as Accounts from Cognism to Bullhorn. 
• Contacts are mapped as Leads, Contacts, or Candidates. 

Microsoft Dynamics 365

Supported objects

• Accounts: Companies or organisations 
• Contacts: Individuals associated with accounts 
• Leads: Unqualified potential customers 

Required permissions

• Global Dynamics 365 admin approval for the Cognism Enterprise application
• Access to leads, contacts, accounts, and campaigns

Note

• Companies are mapped as Accounts from Cognism to Dynamics 365. 
• Contacts are mapped as Leads or Contacts. 

Zapier

Supported objects

The Zapier integration allows you to export Cognism data to other applications through automated workflows.

The integration supports:

• Contacts: Records exported from Cognism Lists 

These records can then be sent to other tools connected through Zapier.

Required permissions

Each Cognism user must set up the Zapier integration individually.

To connect Cognism to Zapier, you need:

• Access to Cognism Integrations settings 
• A Zapier account 
• A Cognism API key to connect your Cognism account in Zapier 

Note

• Zapier enables you to export Cognism data to tools that are not supported as native integrations.
• Contacts are exported from Cognism Lists using the Contact export trigger in Zapier. 
• The destination application and fields depend on how the Zap is configured in Zapier.

Expected results

When the correct permissions are in place:

• Cognism can create and update records in your integrated platform
• Existing records are identified to reduce duplicates
• Sync status indicators are shown in Cognism

Next steps

• Review the permissions for your chosen integration
• Configure field mappings
• Test an export with sample data