> 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/what-salesforce-apps-does-peakcommerce-natively-integrate-with.md).

# Native Salesforce Apps

### Overview

PeakCommerce offers robust integration capabilities with several Salesforce applications, enhancing the functionality and efficiency of e-commerce operations. This integration allows for a seamless connection between PeakCommerce and Salesforce, providing a unified customer experience across various touchpoints.

### Salesforce Revenue Cloud Integration

Functionality: PeakCommerce integrates fully with Revenue Lifecycle Management (RLM), including CPQ (Configure, Price, Quote) & Billing. This integration ensures that e-commerce experiences are harmonious and streamlined, facilitating effective sales operations and financial management within PeakCommerce.

### Salesforce Sales Cloud Integration

E-commerce Journey: During the online shopping experience, several key interactions occur with Salesforce:

* Lead Creation: When a visitor enters their email address on the website, a lead is automatically created in Salesforce.
* Conversion to Account: If the visitor makes a purchase, the lead is converted into an account, and the user’s ID is entered into Zuora on the customer account record.
* In-App Customer Creation: When a sales representative or customer service representative creates a new customer account in-app, the account is immediately created in Salesforce after the order is submitted. Similar to the e-commerce journey, the user’s ID is recorded in Zuora.

### Salesforce Service Cloud Integration

Case Management: PeakCommerce is fully integrated with Salesforce Service Cloud, enabling:

* Case Operations: Users can create, edit, comment on, and view their cases directly within PeakCommerce.
* 360 View of Case History: Both users and Customer Support Representatives can access a complete view of case histories, enhancing customer support and service management.

### Salesforce Communities Integration

Knowledge Base and Single Sign-On: PeakCommerce customers can utilize Salesforce Communities as a knowledge base platform. Key features include:

* Content Delivery: Deliver content effectively to customers through Salesforce Communities.
* Single Sign-On: Customers logged into Communities can automatically access PeakCommerce without re-authenticating, providing a seamless user experience.

### Integration with Other Salesforce Apps

Data Synchronization: PeakCommerce sends data to Zuora and Salesforce in real-time. This real-time data flow enables:

* App Interoperability: Any Salesforce app with access to these data records and objects can utilize the data provided by PeakCommerce, enhancing cross-app functionality and data utilization.

Integrating PeakCommerce with Salesforce applications streamlines various aspects of e-commerce operations from sales and customer service to billing and data management. By leveraging these integrations, businesses can enhance their operational efficiency and provide a more cohesive and satisfying customer experience.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/integrations/crm-and-revops/salesforce-integration/what-salesforce-apps-does-peakcommerce-natively-integrate-with.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.