> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/crm-and-revops/salesforce-integration/salesforce-sales-cloud-integration.md).

# Salesforce Sales Cloud

### **Overview**

To begin setting up your Sandbox or Production tenants of PeakCommerce, one of the initial steps is to integrate with a CRM system. This integration is necessary if you want to keep track of leads, customers, and sales in a CRM system. PeakCommerce offers integration with Salesforce, among other CRM systems.

To access the CRM Integrations page, go to Integrations > CRM. You can manage these settings by clicking the edit button at the bottom of the page.

### Connecting

PeakCommerce connects to Salesforce through a **Connected App** using the OAuth 2.0 **client-credentials flow**. You create the Connected App in Salesforce, choose the **Run As** user whose identity the integration acts under, and enter three values into **Integrations → CRM** in PeakCommerce: the **Login URL**, the **Consumer Key**, and the **Consumer Secret**.

For the full, step-by-step setup — including how to choose the Run As user, and what the upcoming move from Connected Apps to **External Client Apps** means for you — see [Connecting Salesforce with a Connected App](/integrations/crm-and-revops/salesforce-integration/connecting-salesforce-with-a-connected-app.md).

### What happens during the e-commerce journey

Once connected, PeakCommerce keeps Salesforce in step with the commerce lifecycle:

* **Lead creation:** when a visitor enters their details during a signup journey, a **Lead** is created in Salesforce.
* **Conversion to account:** when that visitor completes checkout, the Lead is **converted** into an Account (and Contact). The resulting Salesforce account ID can be recorded on the customer's billing account so the two systems stay linked.
* **In-app account creation:** when a sales rep or customer service rep creates a new customer account in-app, the Account is created in Salesforce once the order is submitted.

All of these writes are performed as the Connected App's **Run As** user and are recorded in **API Call Stats**, so any rejected or failed Salesforce call stays visible for diagnosis rather than being hidden.

### Related

* [Connecting Salesforce with a Connected App](/integrations/crm-and-revops/salesforce-integration/connecting-salesforce-with-a-connected-app.md)
* [What Salesforce apps does PeakCommerce natively integrate with?](/integrations/crm-and-revops/salesforce-integration/what-salesforce-apps-does-peakcommerce-natively-integrate-with.md)
* [Agentforce](/integrations/crm-and-revops/salesforce-integration/agentforce.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/integrations/crm-and-revops/salesforce-integration/salesforce-sales-cloud-integration.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.