Legacy: Clearbit Platform - Why is my Salesforce Account Being Disconnected?
🔍 Please note: This article is for customers on Standard Bundle, Enrichment, or Clearbit Platform plans. If you signed up in 2024, you are on a Sales Intelligence for HubSpot plan: Free, Growth, or Business.
Last updated: 10/6/2023
This guide outlines initial troubleshooting steps if your Salesforce account consistently getting disconnected from Clearbit Platform. If these steps do not fix the issue, please reach out to support@clearbit.com.
Skip Ahead to:
- Integration User & Permissions
- Salesforce Authentication Failure
- REST API is Not Enabled
- Error authenticating due to security policies taking too long to evaluate
Integration User & Permissions
We recommend creating an integration user to connect to Clearbit. That way, when a team member leaves your organization, the connection between Salesforce and Clearbit won’t break.
📝 Please note: Ensure that the user making that authentication has the box API Enabled in the Administrative Permissions checked. Otherwise, the sync with Clearbit will fail.
📝 Please note: Enrichment customers need Read/Write access. Ads & Alerts use cases only need Read access
Ensure Clearbit has the correct object and field-level permissions in Salesforce.
-
Sync all Objects, Records, and Fields
- Make sure your Integration User has read permissions for all of the following objects (and fields on those objects):
- Leads
- Contacts
- Accounts
- Opportunities
- Users
- Make sure your Integration User has read permissions for all of the following objects (and fields on those objects):
-
Sync Selective Data
- Clearbit will only sync objects, records, and fields that the authenticated user has permission to read. To restrict specific data from being synced and displayed in Clearbit, define your Salesforce profiles and permission sets to restrict the authenticated user's read access to those objects, records, and/or fields. Here is how you restrict permissions to certain records.
Salesforce Authentication Failure
This Salesforce OAuth error can happen for several reasons. Here are a couple of common causes:
- Salesforce OAuth error can happen because a particular user may not be allowed to self-authorize
- The base URL is incorrect (test.salesforce.com for sandbox or login.salesforce.com for production)
To resolve the authentication error:
- First, check your base URL, if your base URL is correct and you are still getting the authentication failure error, you can try allowing all users to self-authorize:
- In your Salesforce account, go to: Apps → Connected Apps → Manage Connected Apps → {{YOUR APP}} → Edit Policies to go to your Connected App’s Edit page
- Under Permitted Users, select All users may self-authorize and hit save
Articles in this section
- Legacy: Clearbit Platform - Why is my Salesforce Account Being Disconnected?
- Legacy: What are the Best Practices for using Tech Tags in Salesforce?
- Legacy: Can I Leverage Clearbit for a Salesforce Sandboxes for Testing Purposes?
- Legacy: What Triggers a Salesforce Record to be Enriched by Clearbit?
- Legacy: Does Clearbit Enrich Existing Records in Salesforce in Addition to New Records?
- Legacy: How Frequently is Data Enriched in Salesforce by Clearbit?
- Legacy: What are the Differences between Salesforce Managed Package and Salesforce on Platform?
- Legacy: Set Up Clearbit for Salesforce
- Legacy: Set Up Clearbit Enrichment Field Mapping for Salesforce
- Legacy: What are Salesforce Enrichment Logs?