> 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.md). # Salesforce **Salesforce** is the CRM system of record for most enterprises PeakCommerce works with. The integration keeps leads, contacts, accounts, and opportunities in step with what customers actually do in your commerce flows — and lets Salesforce-native tooling, including AI agents, act on subscriptions through a governed path. ## Why the integration matters Self-service commerce tends to grow up beside the CRM rather than inside it: the storefront creates customers the sales team can't see, and the CRM holds pipeline that never reflects what was bought. Connecting the two means a signup, an upgrade, or a cancellation in a PeakCommerce journey shows up against the right CRM record, and sales-led motions and self-service motions describe the same customer. Because PeakCommerce exposes commerce as governed operations rather than raw writes, Salesforce-side automation — flows, Apex, or an Agentforce agent — can price plans, build carts, and place or change orders without each one reimplementing your pricing and policy rules. ## How the pieces fit * **Connection** — PeakCommerce authenticates to your Salesforce org through a **Connected App** using the OAuth 2.0 client-credentials flow: server-to-server, no interactive login, no refresh tokens. * **CRM sync** — journey activity maps onto CRM objects, so leads and contacts created or updated during a flow land on the right account. * **Sales-led and revenue lifecycle** — Revenue Cloud covers CPQ, billing, and revenue management for deals that close through sales, so self-service and sales-led orders land in one lifecycle. * **AI agents** — Agentforce agents reach PeakCommerce through the Agent API, giving them a governed way to quote and transact rather than free-form access to billing. ## Setting it up Integrating a CRM is one of the first steps when provisioning a PeakCommerce sandbox or production tenant. Begin with [Connecting Salesforce with a Connected App](/integrations/crm-and-revops/salesforce-integration/connecting-salesforce-with-a-connected-app.md) for the OAuth setup, then [Salesforce Sales Cloud Integration](/integrations/crm-and-revops/salesforce-integration/salesforce-sales-cloud-integration.md) for what syncs once the connection is live. ## In this section * [Salesforce Sales Cloud Integration](/integrations/crm-and-revops/salesforce-integration/salesforce-sales-cloud-integration.md) — connect Sales Cloud and keep leads, customers, and sales in sync. * [Connecting Salesforce with a Connected App](/integrations/crm-and-revops/salesforce-integration/connecting-salesforce-with-a-connected-app.md) — create the Connected App and supply the Login URL, Consumer Key, and Consumer Secret. * [Agentforce](/integrations/crm-and-revops/salesforce-integration/agentforce.md) — let Salesforce AI agents transact through the Agent API. * [Revenue Cloud](/integrations/crm-and-revops/salesforce-integration/revenue-cloud.md) — how PeakCommerce fits alongside CPQ, billing, and revenue management. * [Native Salesforce Apps](/integrations/crm-and-revops/salesforce-integration/what-salesforce-apps-does-peakcommerce-natively-integrate-with.md) — which Salesforce applications PeakCommerce integrates with natively. ## Related * [CRM & RevOps overview](/integrations/crm-and-revops/crm-and-revops.md) — the other CRM and revenue-operations integrations PeakCommerce supports. * [Integrating CRM Systems with PeakCommerce](/integrations/crm-and-revops/integrating-crm-systems-with-peakcommerce.md) — the general shape of a CRM integration, if you are not on Salesforce. --- # 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.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 `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.