> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/integrations/salesforce.md). # Salesforce Automatically sync verified contacts and leads into Salesforce CRM Clearout natively integrates with Salesforce CRM to maintain high deliverability and improve overall contact data quality across your account. Clearout supports two contact verification solutions for Salesforce: * [Data Pulse](/integrations/salesforce.md#how-data-pulse-salesforce-two-way-sync-works): Continuous, real-time monitoring and multi-field enrichment automatically validating Name, Email, and Phone data on Leads and Contacts, as they are created and as they are updated in Salesforce. * [Email Verifier](/integrations/salesforce.md#how-email-verifier-works): On-demand bulk verification and cleaning for existing Salesforce email lists. ## Integration Architecture The Clearout Salesforce integration uses the standard OAuth 2.0 authorization flow. When you authorize the connection, Salesforce issues an access token and a refresh token, which Clearout uses to make API calls on your behalf. Clearout never stores your Salesforce credentials. All communication with the Salesforce platform happens over HTTPS.

## Before You Begin - What You Need To use the Clearout–Salesforce integration, your Salesforce Org must meet a few requirements: * **Supported Salesforce Edition** - requirements differ by product, see the table below. * **Admin permissions in Salesforce -** required for the **initial one-time setup** (installing the Clearout managed package and assigning the permission set). Standard users can run validations after setup is complete. * **A Clearout account** - sign up at [clearout.io](https://clearout.io/) if you don't have one. #### Supported Salesforce Editions

Salesforce Edition	Email Verifier	Data Pulse
Enterprise	Supported	Supported
Unlimited	Supported	Supported
Developer Edition	Supported	Supported
Professional Edition with the API Access add-on	Supported	Not supported

{% hint style="warning" %} **Data Pulse requires outbound message support** Data Pulse depends on Salesforce outbound messages to detect and sync records in real time. Professional Edition does not support outbound messages, so Data Pulse cannot run on it even with the API Access add-on. If your org is on Professional Edition, use Email Verifier for on-demand bulk cleaning of your existing lists. {% endhint %} ## How to Set Up the Clearout–Salesforce Integration The Clearout integration with Salesforce involves a one-time admin setup, followed by daily use that any team member can perform. * [One-Time Admin Setup](#one-time-admin-setup) - An one-time setup has be done by the admin of your organization * [How the Salesforce integration works](#daily-use-any-user-with-the-permission-set) - How a user can perform bulk email validation once the permission set is assigned to the user account in the organization ## One-Time Admin Setup {% hint style="warning" %} This setup must be performed by a **Salesforce administrator** in your org. {% endhint %} {% stepper %} {% step %} ### Install the Clearout Managed Package in Your Salesforce Org * Click here to install the [**Clearout managed package**](https://clearout.io/salesforce-managed-package/). * Log into your Salesforce Org. * On the installation screen, select the installation option based on your requirements.

* Click **Install**. Salesforce will process the installation, which takes a few minutes. * Once complete, you'll receive a confirmation. The package adds the following to your org: * Clearout External Client App (Handles OAuth) * Clearout Permission Set (The Clearout Permission Set gives users access to the Clearout-specific fields on your Contact and Lead records) * Clearout Custom fields on Contact and Lead objects (These are [Clearout's standard fields](/email-verifier/overview.md#result_file_header), that will be used for storing the validated results) {% endstep %} {% step %} ### Assign the Clearout Permission Set to the Desired Users * In the Home page, click on the **Gear** icon and select the option **Setup**.

* Search for **Permission Sets** in Quick Find and select it. * After entering the Permission Sets page, search for the **"Clearout"** permission set in the list.

* Drill down on the Clearout permission set, and click on **Manage Assignments**. * After entering Manage Assignments, click on **Add Assignment** and select the users you want to assign the permission set to. * Once the desired users have been selected, click on the **Next** button and click **Assign**. * To make sure the permission set is assigned, you can check the **Manage Assignments** page to see the permission set is assigned to the intended users. {% endstep %} {% step %} ### Connect Your Salesforce Account with Clearout * **Log in** to your Clearout account. * Go to the [**Integrations**](https://app.clearout.io/integrations/connect-account) section. * Select **Salesforce**. * Click **Add Account**. * Log in to your Salesforce Org.

* Once authorized, your Salesforce Campaign lists (Contacts/Leads) will be available to verify. {% endstep %} {% endstepper %} ## How Data Pulse Salesforce Two-Way-Sync Works Data Pulse is the real-time CRM contact verification tool that validates every email, phone, and name the moment a Lead or Contact is created or updated - and writes the clean record back automatically. [Know more.](/data-pulse/overview.md) {% stepper %} {% step %} ### Enable Account Go to the Data Pulse [dashboard](https://app.clearout.io/data-pulse), find your linked Salesforce account, and click **Enable**.

{% hint style="info" %} At any given point realtime pulsing can only be enabled on one clearout account for a given salesforce account. {% endhint %} {% endstep %} {% step %} ### Choose what to enrich Choose the fields you want to enrich. You can select one or more enrichment options based on your requirements.

{% hint style="warning" %} At least one field must be selected to continue. {% endhint %} {% endstep %} {% step %} ### Configuring Data Field Mapping Decide which fields require validation and define output metadata fields for appending. #### Input Field Mappings Map incoming fields from your data source to Data Pulse input fields to ensure accurate validation and enrichment. You can configure mappings using either a **preset** or by selecting **custom fields**. Available presets: * **Auto Map** - Automatically detects and maps fields based on the source structure.

**Data Pulse Input Fields Reference**

Field Name	Description
First Name	Given name associated with the contact
Last Name	Surname associated with the contact
Full Name	Combined name field (if available in source)
Email	Primary email address for validation and enrichment
Phone	Contact number for validation and formatting
Country	Geographic identifier used to determine the country dialling code during phone validation if the dialling code is not present in the number

#### Output Field Mappings Choose which fields should be returned and synced back after enrichment. You can configure mappings using either a **preset** or by selecting **custom fields**. Available presets: * **All** - Selects every available output field. * **Mandatory Fields** - Selects only the required fields.

**Output Fields Reference** {% tabs %} {% tab title="Email" %}

Clearout Field Name	Description
Status (Mandatory)	Validation status of the email
Safe to Send (Mandatory)	Indicates if the email is safe for outreach
Reason	Reason associated with the validation result
SMTP Provider	Identified email service provider
Free Domain	Indicates if the email uses a free/public email provider
Role Email	Indicates if the email is a role-based address (e.g., info@, support@, admin@)
Disposable Email	Indicates if the email uses a temporary/disposable domain
Gibberish Email	Indicates if the email's local part appears to be random or meaningless characters

{% endtab %} {% tab title="Phone" %} | Clearout Field Name | Description | | --------------------------- | ------------------------------------------- | | **Status** *(Mandatory)* | Validation status of the phone number | | **Carrier** | Telecom carrier information | | **Country Name** | Country associated with the number | | **Country Timezone** | Timezone of the detected country | | **E164 Format** | Standardized international format | | **Line Type** *(Mandatory)* | Type of phone line (mobile, landline, etc.) | | **Location** | Geographic location metadata | | **DST Observed Hrs** | Hours adjusted for daylight saving time | | {% endtab %} | | {% tab title="Name" %} | Clearout Field Name | Description | | --------------------------------- | ----------------------------------------------- | | **Normalized Name** *(Mandatory)* | The cleaned/standardized version of the name | | **Gibberish** *(Mandatory)* | Indicates if the name appears invalid or random | | **Status** | Validation result for the name | | {% endtab %} | | {% tab title="Miscellaneous" %} | Clearout Field Name | Description | | ----------------------------- | --------------------------------------- | | **Enriched On** *(Mandatory)* | Timestamp when enrichment was performed | | {% endtab %} | | | {% endtabs %} | | {% hint style="info" %} You can save custom field mappings as a new preset. Saved presets can be reused for the same data source in future configurations. This applies to both import and output field mappings. {% endhint %} {% endstep %} {% step %} ### Choose Pulse Trigger Choose which CRM events Data Pulse should react to: new contacts being created, existing ones being updated, or both.


Trigger	When Data Pulse runs
Created Only	Pulses a contact or lead once, when it is first created in your CRM. Later edits are not pulsed.
Updated Only	Pulses an existing contact or lead only when its name, email or phone changes. Newly created records and edits to other properties are not pulsed.
Created And Updated	Pulses new contacts and leads as they are created, and again whenever their name, email or phone changes.

{% endstep %} {% step %} ### Activate Data Pulse

Complete the setup wizard to activate real-time validation and enrichment.\ Weekly data quality report is **enabled by default**. You can opt-in or opt-out of the report here. {% endstep %} {% endstepper %} ### What to expect once it is enabled Data Pulse monitors both **Leads** and **Contacts** from the moment it is enabled. A record is validated when it is created, and again whenever its first name, last name, email, or phone is updated. Salesforce outbound messages do not indicate which field changed, so on an update Data Pulse validates every enabled field on the record rather than only the changed one. The 24-hour dedupe still applies, so values that have not changed are not charged again.\ \ Results are returned in real time within seconds, and Data Pulse appends its own set of [Clearout result properties](/data-pulse/supported-data-sources.md#fields-data-pulse-updates) to the record. A weekly data quality digest is delivered every Monday. ### Bulk Importing Leads with the Data Import Wizard Data Pulse validates a record when Salesforce sends Clearout an outbound message about it. That message is fired by a record-triggered Flow installed with the managed package. The Data Import Wizard does not run your org's automation by default. Left at its default setting, a bulk import through the wizard can land thousands of leads in Salesforce without a single one reaching Data Pulse. The import will report success, so the gap is easy to miss. {% hint style="warning" %} **Tick the automation checkbox before importing** The wizard leaves **Trigger workflow rules and processes?** unticked by default. Tick it, or none of your imported leads will be sent to Clearout for validation. {% endhint %} #### Opening the Data Import Wizard Where you launch the wizard from depends on your Salesforce Edition. Both routes open the same wizard, and every step after this point is identical. {% tabs %} {% tab title="Unlimited" %} 1. Log in to your Salesforce Org and go to the **Leads** object. 2. Scroll down to the **Tools** section. 3. Select **Import Leads**.

{% endtab %} {% tab title="Enterprise" %} 1. From the Home page, click the **Gear** icon in the top right and select **Setup**. 2. Search for **Data Import Wizard** in Quick Find and select it. 3. Scroll down and click **Launch Wizard**.

{% endtab %} {% tab title="Developer" %} 1. Log in to your Salesforce Org and go to the **Leads** object. 2. Select **Import**.

{% endtab %} {% endtabs %} #### Running the Import {% stepper %} {% step %} #### Select the object Under **Standard Objects**, select **Leads**. {% endstep %} {% step %} #### Choose "Add new records" and tick the automation checkbox Click **Add new records**, then tick the checkbox under **Trigger workflow rules and processes?** This is the step that matters. With the box unticked, your leads import successfully but Data Pulse never sees them.

{% endstep %} {% step %} #### Upload your file Select the file you want to import and click **Next** at the bottom right. {% endstep %} {% step %} #### Verify the field mapping Check that your columns are mapped to the correct Salesforce fields, then click **Next** at the bottom right. {% endstep %} {% step %} #### Start the import Click **Start Import**. Your leads are created in Salesforce, the Flow fires, and Data Pulse enrichment appears on each record within seconds. {% endstep %} {% endstepper %} {% hint style="info" %} **Recovering leads imported without the checkbox** Leads imported with the checkbox unticked never reach Clearout, because no automation runs during the import itself. Data Pulse also monitors updates, so you have three ways to recover them: * Update one of the watched standard fields (first name, last name, email, or phone) on the affected leads. This fires the Flow and sends them to Clearout Data Pulse. * Delete the imported leads and re-import them with the checkbox ticked, or * Run Email Verifier over the affected list. This cleans the email addresses but does not enrich phone or name data. {% endhint %} ## How Email Verifier Works {% stepper %} {% step %} ### Import Your Campaign (Contact/Lead) Lists * Once connected, you can choose from your Salesforce Campaign Lists. * **Select the list(s)** you wish to clean and click **Add to My List**.

{% endstep %} {% step %} ### Start the Verification * After importing, hit **Start verification**. * Clearout performs **20+ advanced checks**, ensuring 99% accuracy. * Disposable, spam trap, catch-all, syntax errors, and inactive emails are all flagged.

{% endstep %} {% step %} ### Export the Clean List After the validation is complete, the user can download the results in CSV format or export them directly to their Salesforce Org. The user can export the results by selecting **unsubscribe**, **append**, or **both**. * **Unsubscribe**: Select this option to remove all the non-deliverable (invalid) email addresses on the Salesforce Org automatically. * **Append**: Select this option to append the Clearout standard columns to Salesforce Org. This ensures your email list remains accurate, your reputation intact, and your Salesforce Org is clean.

{% endstep %} {% step %} ### Verify the exported validated results After the exporting is complete, the contact and lead records will be updated with the validated results in the custom fields from Clearout.

#### How to add clearout custom fields to the contacts list view table: * In the App Launcher, search for "Contacts" and click it for entering into the contacts object.

* Open the **List view controls** (Gear Icon) in the Contacts tab and click on the "Select fields to display" option.

* Select and move the fields to the "Visible Fields" column that are required to be displayed on the list view for verification and click on save. {% endstep %} {% endstepper %} ## Choosing the Right Solution Both products use the same validation engine. The difference is when and how they run. ### **When to Use Data Pulse** * You want always-on, hands-off validation of every Lead and Contact as it enters Salesforce and as its details change. * You want results to live natively on the Salesforce record with no exports or re-imports. * Bad data enters continuously through forms, imports, and integrations, and you want to catch it at the source rather than in periodic cleanups. ### **When to Use Email Verifier** * You need a one-time clean of an existing list, for example pre-campaign list hygiene. * The list lives outside Salesforce (a CSV, XLSX, or Google Sheet). * You are validating your existing Salesforce database before turning Data Pulse on. A common pattern: run a one-time Bulk Verification to clean the contacts already in Salesforce, then enable Data Pulse to keep everything clean from that point forward. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.clearout.io/integrations/salesforce.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.