> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/advanced-logic/visual-rule-builder/connect-to-api-action/salesforce-api-connector.md).

# Salesforce API Connector

If you have Feathery's [Salesforce integration](https://www.feathery.io/integrations/salesforce) enabled on a form, you can build custom Salesforce API connectors that leverages your integration connection.

<figure><img src="/files/rLnKA09P1UVtaZXXZRlK" alt="" width="375"><figcaption></figcaption></figure>

The Salesforce API connector allows you to configure a custom SOQL query to prefill data from your Salesforce instance into your Feathery form. The SOQL query can leverage data from your existing Feathery fields, and the data that is returned can also be used to populate various fields.

<figure><img src="/files/kKEwNL1fXaj2AqbABrtj" alt=""><figcaption></figcaption></figure>

Similar to other API connectors, Salesforce API connectors can be used in any logic rule, at any point in your form flow. You can also switch to **Advanced Configuration** mode at any point to have full control of the API request being sent to 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 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.feathery.io/platform/build-forms/advanced-logic/visual-rule-builder/connect-to-api-action/salesforce-api-connector.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.