> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/scout/connections/salesforce.md). # Salesforce Scout reads your Salesforce with your own login, and updates leads, contacts, opportunities and activity as you when you ask. Scout reads your Salesforce to understand your pipeline, and updates it as you when you ask. ## Connect Connect your own Salesforce login from Scout's card, or from your [**Scout**](https://app.spara.co/scout) page under **Accounts**. Your sign-in stands on its own: it doesn't depend on whether your company has connected Salesforce to Spara for its inbound CRM sync. Scout acts under your own Salesforce permissions. What you can't see or change in Salesforce, Scout can't either. ## What Scout does with it * **Reads your pipeline**: leads, contacts, accounts, opportunities and activity. * **Updates records when you ask**: logs activity, updates a lead, contact or opportunity, as you. Say what you want changed in conversation, and Scout does it. * **Brings you changes from jobs.** A job that runs on its own doesn't write to Salesforce. When it would, it delivers the change for you to apply. {% hint style="info" %} Spara's CRM sync for your inbound leads is a separate, team-wide connection. See [Salesforce](https://docs.spara.com/integrations/crm-integrations/salesforce) for how that works. {% endhint %} --- # 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.spara.com/scout/connections/salesforce.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.