> ## Documentation Index
> Fetch the complete documentation index at: https://testdocs.clodura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce CRM Integration Setup Guide for Clodura.AI

> Connect Salesforce Sales Cloud to Clodura.AI via OAuth 2.0, map fields, then export prospects as Contacts or Leads with associated Account records.

Clodura.AI's Salesforce integration connects to your Salesforce Sales Cloud environment using the industry-standard OAuth 2.0 protocol. This means you never share API keys or passwords — Clodura.AI requests only the permissions it needs to create and update Contacts, Leads, and Accounts. Once connected, you can export selected prospects from Clodura.AI's People Search directly into Salesforce, choosing at export time whether each record becomes a **Contact** or a **Lead**. The complete setup requires three sequential steps: **Authorization**, **Field Mapping**, and **Activation**.

## Prerequisites

Before you begin, ensure you have:

* An active Clodura.AI account with CRM integration access.
* A Salesforce account (Sales Cloud). Any edition that supports the Contacts, Leads, and Accounts objects will work.
* Sufficient Salesforce permissions to authorize third-party OAuth applications and to create/update Contact, Lead, and Account records.

## Step 1 — Authorize Salesforce in Clodura.AI

Salesforce uses a secure OAuth 2.0 workflow. You do not need to copy any API keys — authorization happens through Salesforce's own login and permissions pages.

<Steps>
  <Step title="Open CRM Integration settings">
    In Clodura.AI, navigate to **Settings → CRM Integration**. Each supported CRM is displayed as a card showing its current status.
  </Step>

  <Step title="Click Authorize on the Salesforce card">
    Locate the **Salesforce** card, which initially shows a **Disconnected** status. Click the **Authorize** button.
  </Step>

  <Step title="Log in to Salesforce">
    Your browser redirects to the Salesforce login screen. Enter your Salesforce username and password. If you are already logged into Salesforce in the same browser session, this step is skipped automatically.
  </Step>

  <Step title="Grant permissions">
    Salesforce displays a permissions-grant page listing the modules Clodura.AI requires access to (Contacts, Accounts, Leads, etc.). Click **Allow** or **Grant Access** to proceed.
  </Step>

  <Step title="Return to Clodura.AI">
    After granting access, Salesforce redirects you back to Clodura.AI. The Salesforce card now shows a green **Connected** status tag, confirming the authorization was successful. Proceed immediately to Field Mapping.
  </Step>
</Steps>

<Note>
  If your Salesforce organization has IP restrictions or enforces multi-factor authentication, you may need to complete additional verification steps before the OAuth redirect succeeds. Contact your Salesforce administrator if you encounter an authorization error.
</Note>

## Step 2 — Map Fields

Field mapping defines how Clodura.AI source data is written into Salesforce objects. Salesforce supports three mapping tabs: **Company Fields** (Salesforce Accounts), **Contact Fields** (Salesforce Contacts), and **Lead Fields** (Salesforce Leads).

Click the **Mapping** button on the Salesforce card to open the Field Mapping modal.

### Company Fields → Salesforce Accounts

The **Company Fields** tab maps organization-level data from Clodura.AI to Salesforce Account records:

| Clodura.AI Field    | Salesforce Account Field |
| ------------------- | ------------------------ |
| Company Name        | Account Name             |
| LinkedIn URL        | LinkedIn Company Page    |
| Company Description | Description              |
| Number of Employees | Number of Employees      |
| Industry            | Industry                 |
| Website             | Website URL              |
| Founded             | Year Founded             |
| City                | Billing City             |
| State               | Billing State/Region     |
| Country             | Billing Country/Region   |

### Contact Fields → Salesforce Contacts

Click **Next** to move to the **Contact Fields** tab. These fields populate Salesforce Contact records:

| Clodura.AI Field    | Salesforce Contact Field |
| ------------------- | ------------------------ |
| First Name          | First Name               |
| Last Name           | Last Name                |
| Job Title           | Title                    |
| Email               | Email                    |
| LinkedIn Profile    | Select One               |
| Mobile Phone Number | Mobile Phone             |
| City                | Mailing City             |
| State               | Mailing State/Region     |
| Country             | Mailing Country/Region   |

### Lead Fields → Salesforce Leads

Click **Next** again to reach the **Lead Fields** tab. These fields populate Salesforce Lead records when you choose the Lead record type at export time:

| Clodura.AI Field    | Salesforce Lead Field  |
| ------------------- | ---------------------- |
| First Name          | First Name             |
| Last Name           | Last Name              |
| Job Title           | Title                  |
| Email               | Email                  |
| LinkedIn Profile    | Select One             |
| Mobile Phone Number | Mobile Phone           |
| City                | Mailing City           |
| State               | Mailing State/Region   |
| Country             | Mailing Country/Region |

<Warning>
  No two Clodura.AI fields may be mapped to the same Salesforce destination field within a single tab. Custom field mapping — adding Salesforce fields that are not available in the dropdown lists — is not supported.
</Warning>

Use the modal controls to navigate and finalize your mapping:

* **Next** — advance to the next tab (Company → Contact → Lead).
* **Back** — return to the previous tab.
* **Reset** — restore all fields in the current tab to their default mapping values.
* **Save** — save your full mapping configuration and close the modal.
* **Close** — discard unsaved changes and exit the modal.

## Step 3 — Enable the Integration

After saving your field mapping, return to the Salesforce card in **Settings → CRM Integration** and switch the **Enable** toggle to **ON**. This activates the integration and makes the **Export To CRM** button available in your Clodura.AI search results. Switch the toggle **OFF** at any time to pause the integration without deleting your mapping configuration.

The Salesforce card displays three status indicators:

* **Connected** (green checkmark) or **Disconnected** — the current authorization state.
* **Authorize** button — re-run the OAuth flow if needed.
* **Mapping** button — update your field mapping at any time.

## Pushing Contacts to Salesforce

Once the integration is enabled, you can export prospects from Clodura.AI's People Search results directly into Salesforce.

<Steps>
  <Step title="Search for contacts">
    Run a people search in Clodura.AI using your desired filters and review the results grid.
  </Step>

  <Step title="Select contacts">
    Check the boxes next to one or more contacts you want to export.
  </Step>

  <Step title="Click Export To CRM">
    Click the **Export To CRM** button. The **Export To Salesforce CRM** modal appears, confirming the number of selected contacts and noting that each contact's associated company will also be added.
  </Step>

  <Step title="Select the record type">
    Use the **Record Type** dropdown to choose whether each selected contact should be created as a **Contact** or a **Lead** in Salesforce. This choice also determines which field mapping tab (Contact Fields or Lead Fields) is used for the transfer.
  </Step>

  <Step title="Assign an owner">
    Use the **Assign To** dropdown to select the Salesforce user who will be set as the owner of the newly created records.
  </Step>

  <Step title="Confirm the export">
    Click **Ok** to initiate the transfer. Click **Close** to cancel without exporting.
  </Step>
</Steps>

<Tip>
  Choosing **Contact** creates the record under Salesforce's Contacts object and links it to an Account. Choosing **Lead** creates the record under the Leads object, where it can later be converted to a Contact and Account through Salesforce's standard lead-conversion workflow.
</Tip>

## Export Confirmation and Verification

After the export completes, Clodura.AI notifies you in two ways:

<CardGroup cols={2}>
  <Card title="In-App Notification" icon="bell" href="/docs/integrations/salesforce#export-confirmation-and-verification">
    A notification appears inside Clodura.AI confirming the records were transferred successfully.
  </Card>

  <Card title="Email Notification" icon="envelope" href="/docs/integrations/salesforce#export-confirmation-and-verification">
    An email is sent to your registered address once the Salesforce import finishes.
  </Card>
</CardGroup>

Log in to your Salesforce account and check the **Accounts** and **Contacts** (or **Leads**) objects to verify the newly created records appear with the correct field values.

<Info>
  Exporting the same contact to Salesforce multiple times counts as only a **single download-credit usage** in Clodura.AI. To prevent re-exporting records that are already in Salesforce, enable the **Exclude Exported Contacts** filter in Clodura.AI's advanced search before running additional exports.
</Info>
