> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/connectivity/connectors/connect-salesforce-for-auto-updates.md).

# Connect Salesforce for auto-updates

The Salesforce connector lets a Key Result or Initiative update itself from your CRM — a figure from a Salesforce report, pipeline by stage, closed-won revenue, win rate, lead or case counts, or a value from any standard or custom object. The setup flow (Update mode › Set up auto update, then a short chat) is the same for every connector and is described in [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md). This article covers only what is specific to Salesforce.

## Before you connect Salesforce

* A Rhythms Admin has enabled **Salesforce** under **Settings › Workspace › Connectors**. There is no workspace-level Salesforce sign-in; each person connects their own Salesforce user.
* You have a Salesforce user with API access and permission to see the reports, objects and fields you want to track. Field-level security applies.
* Your org signs in at `login.salesforce.com`. Sandbox orgs are not supported.

## How Salesforce authentication works

You sign in to Salesforce (OAuth) from **My connectors › Salesforce › Connect** or when the setup chat prompts you, and allow access. Rhythms requests API access plus a refresh token so the connection stays active. Rhythms hosts the Salesforce connector itself and reads through the Salesforce REST API.

## Setting up in chat

Rhythms works report-first: it asks for a Salesforce **report link or report name**. It then lists the report's summary columns, you pick the one to track, and Rhythms shows the current value and asks whether to track the whole report or a subset (owner, stage, segment). If a report does not fit, Rhythms can use ready-made pipeline, opportunity, lead and case summaries, or query any object directly.

## What you can track from Salesforce

* Any aggregate column of a Salesforce report (sum, count, average)
* Opportunity pipeline by stage, closed-won revenue, win rate, average deal size
* Lead counts and conversion rate; case counts and resolution rate
* Counts or sums over standard objects, custom objects and custom fields, with date-range filters

## Limits

* There is no manual "sync now" button; updates run on the schedule described in the article above, and you can ask Rhythms to change it.
* Rhythms never creates or changes Salesforce records during an auto-update.

## Example prompts

* "Track the Total Amount column of this report: ‹paste report link›."
* "Sum closed-won opportunity amounts with a close date in this quarter."

## Related articles

* [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)
* [Enable Connectors for Your Workspace](/connectivity/manage-connectors-for-your-workspace.md)
* [Set up automatic updates from a connector](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md)
* [Manage connectors for your workspace](/connectivity/manage-connectors-for-your-workspace.md)


---

# 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://help.rhythms.ai/connectivity/connectors/connect-salesforce-for-auto-updates.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.