Salesforce — Historical data
This connector captures data from Salesforce objects into Flow collections. It uses batch processing and is ideal for syncing your historical Salesforce data.
A separate connector is available for real-time Salesforce data capture. For help using both connectors in parallel, contact your Estuary account manager.
This connector is available for use in the Flow web application.
For local development or open-source workflows,
ghcr.io/estuary/source-salesforce:dev provides the latest connector image. You can also follow the link in your browser to see past image versions.
This connector is based on an open-source connector from a third party, with modifications for performance in the Flow system. You can find their documentation here, but keep in mind that the two versions may be significantly different.
Supported data resources
This connector can capture the following Salesforce standard objects, if present in your account:
Custom objects aren't currently supported. Each captured object is mapped to a Flow collection through a separate binding.
Because most Salesforce accounts contain large volumes of data, you may only want to capture a subset of the available objects. There are several ways to control this:
Create a dedicated Salesforce user with access only to the objects you'd like to capture.
Apply a filter when you configure the connector. If you don't apply a filter, the connector captures all objects available to the user.
During capture creation in the web application, remove the bindings for objects you don't want to capture.
Using OAuth2 to authenticate with Salesforce in the Flow web app
If you're using the Flow web app, you'll be prompted to authenticate with Salesforce using OAuth. You'll need the following:
A Salesforce organization on the Enterprise tier, or with an equivalent API request allocation.
Salesforce user credentials. We recommend creating a dedicated read-only Salesforce user.
Configuring the connector specification manually
If you're working with flowctl and writing specifications in a local development environment, you'll need to manually supply OAuth credentials. You'll need:
The items required to set up with OAuth2.
A Salesforce developer application with a generated client ID, client secret, and refresh token. See setup steps.
Create a read-only Salesforce user
Creating a dedicated read-only Salesforce user is a simple way to specify which objects Flow will capture. This is useful if you have a large amount of data in your Salesforce organization.
Edit the new profile's permissions. Grant it read access to all the standard and custom objects you'd like to capture with Flow.
Create a new user, applying the profile you just created. You'll use this user's email address and password to authenticate Salesforce in Flow.
Create a developer application and generate authorization tokens
To manually write a capture specification for Salesforce, you need to create and configure a developer application. Through this process, you'll obtain the client ID, client secret, and refresh token.
Create a new developer application.
a. When selecting Scopes for your app, select Manage user data via APIs
(api), Perform requests at any time
(refresh_token, offline_access), and Manage user data via Web browsers
Edit the app to ensure that Permitted users is set to All users may self-authorize.
Locate the Consumer Key and Consumer Secret. These are equivalent to the client id and client secret, respectively.
Follow the Salesforce Web Server Flow. The final POST response will include your refresh token.
You configure connectors either in the Flow web app, or by directly editing the Flow specification file. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the batch Salesforce source connector.
The properties in the table below reflect the manual authentication method.
If you're working in the Flow web app, you'll use OAuth2,
so you won't need the
/credentials values listed here.
|Authorization type||Set to ||string|
|Client ID||The Salesforce Client ID, also known as a Consumer Key, for your developer application.||string||Required|
|Client Secret||The Salesforce Client Secret, also known as a Consumer Secret, for your developer application.||string||Required|
|Refresh Token||The refresh token generated by your developer application.||string||Required|
|Sandbox||Whether you're using a Salesforce Sandbox.||boolean|
|Start Date||Start date in the format YYYY-MM-DD. Data added on and after this date will be captured. If this field is blank, all data will be captured.||string|
|Filter Salesforce Objects (Optional)||Filter Salesforce objects for capture.||array|
|Search criteria||Possible criteria are ||string|
|Search value||Search term used with the selected criterion to filter objects.||string|
|Cursor field||Field used as a cursor to track data replication; typically a timestamp field.||array, null|
|Stream||Salesforce object from which a collection is captured.||string||Required|
|Sync Mode||Connection method.||string||Required|
This sample specification reflects the manual authentication method.
- criteria: "starts with"