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

# Salesforce

You can connect to your Salesforce instance to explore data, combine them with other data sources and build apps on top of them as a data foundation.

## Connecting to your Salesforce instance

To connect your Salesforce instance, follow the steps below:

1. Go to **Data Management** and click on "**New source**" to create a new data source. 
2. Select **Salesforce** from the list of available data sources.
3. Click on "**Connect to Salesforce**" and confirm the access request to your instance when redirected to Salesforce. After (potentially logging in and) clicking "**Allow**" you will be redirected back to the configuration page.
4. Save your Salesforce connection with "**Connect**".

Note that, additionally, we allow you to connect to a sandbox instance if you don't want your production database to be linked to Uify. This is especially advisable for the staging environment if you decide to setup a staging and a production environment. You can find more information [here](broken://pages/FM88Izx8RDNtGtuF6cvH) about how the different environments work. 


---

# 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.uify.io/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 `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.