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

# Salesforce

![Salesforce Logo](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/9k9yAuWVDfaqGQktm9gg/67VH4QbKMRmTaWETnPtIf_logo%20text%200e046bbc0a6d2815a94bbbe255b136d1.png)

Salesforce is a leading customer relationship management (CRM) platform that empowers businesses to streamline and enhance their interactions with customers, prospects, and partners.

Renowned for its cloud-based architecture, Salesforce offers a comprehensive suite of tools and features, including sales automation, marketing automation, customer service, analytics, and more.

By centralizing crucial customer data and automating various processes, Salesforce enables organizations to improve efficiency, boost productivity, and deliver more personalized and effective customer experiences.

With its user-friendly interface and scalability, Salesforce has become a cornerstone for businesses aiming to optimize their operations and cultivate lasting customer relationships.

Leveraging our inherent integration with Salesforce, you can seamlessly synchronize your Salesforce account and LicenseSpring platform, effectively bridging these two systems together.


---

# 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.licensespring.com/integrations/salesforce.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 `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.