Salesforce Feeds v2

Salesforce is the industry-leading CRM platform for managing sales, service, marketing, and customer data across standard and custom objects. The Salesforce Feeds v2 connector is a source-only ELT connector that ingests Salesforce objects (sobjects) as feeds. Nexla discovers the standard and custom objects available in your Salesforce org, lets you select which objects to ingest, and reads each selected object as its own feed using either an incremental (auto-increment) or full-refresh sync strategy.

Power end-to-end data operations for your Salesforce Feeds v2 API with Nexla. Our bi-directional Salesforce Feeds v2 connector is purpose-built for Salesforce Feeds v2, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Salesforce Feeds v2 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Salesforce Feeds v2 workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Salesforce Feeds v2 connector authenticates through Nexla's own OAuth2 application, so you do not need to register a Salesforce connected app or manage a client ID and secret yourself. During credential creation you sign in to Salesforce and authorize the Nexla app to read data from your org.

Before creating a credential in Nexla, confirm the following:

1. You have a Salesforce login for the org you want to ingest. The connector reads data through the Salesforce REST API using the permissions of the authorizing user, so use an account that can see the objects and records you intend to ingest. For repeatable ELT pipelines, Salesforce recommends using a dedicated integration user rather than a personal account.

2. The authorizing user has the "API Enabled" permission. Salesforce grants REST API access through the API Enabled permission on the user's profile or an assigned permission set. Without it, the org rejects API requests even after a successful login. An administrator can enable it under Setup > Users (profile or permission set) > System Permissions > API Enabled.

3. You know whether the org is a Production or Sandbox instance. Production orgs authenticate against login.salesforce.com and sandboxes against test.salesforce.com. You select the instance type when creating the credential, and Nexla routes the OAuth login accordingly.

Grant the authorizing user only the object and field access needed for the feeds you plan to ingest. The connector inherits that user's visibility, so object- and field-level security in Salesforce directly controls what Nexla can read.

For more information, see the Salesforce REST API Developer Guide and Authorization Through Connected Apps and OAuth 2.0.

Authenticate

Credentials required

Field	Required	Secret	Description
Salesforce Feeds Instance Type	No	No	Salesforce Instance you wish to connect to Allowed values: Production; Sandbox

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   Resource descriptions are recommended but are not required. Use them to identify the Salesforce org, instance type, or integration user represented by this credential.

3. Select the instance you want to connect to in the Salesforce Feeds Instance Type field. Choose Production to authenticate against login.salesforce.com, or Sandbox to authenticate against test.salesforce.com. The default is Production.

4. Click the button to authorize with Salesforce. Nexla redirects you to the Salesforce login page for the selected instance type. Sign in with a user that has the API Enabled permission and access to the objects you plan to ingest, then grant the Nexla app the requested access. Salesforce returns an OAuth token that Nexla stores and refreshes automatically.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Salesforce Feeds v2 flows.

Use as a data source

How This Connector Works

The Salesforce Feeds v2 connector is a source-only, multi-object ELT connector. Rather than configuring one endpoint at a time, you select the Salesforce objects you want from the set of objects discovered in your org, and Nexla ingests each selected object as its own feed.

• Discovery: When you create the source, Nexla queries the Salesforce REST API to list the sobjects available in your org — standard objects such as Account, Contact, Lead, and Opportunity, along with any custom objects — and presents them for selection. Nexla also discovers the fields for each object so it can build the correct schema.

• Sync strategies: Each selected object is ingested with one of two strategies. Auto-increment (the default) reads only records created or modified since the last run, using a timestamp cursor for efficient incremental loads. Full ingest reads the complete current set of records for the object on every run. Records are uniquely identified by the Salesforce Id field.

• Parallel ingestion: Selected feeds are read in parallel, so a single source can pull many Salesforce objects on the same schedule.

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

2. Select the Salesforce Feeds v2 connector tile from the list of available connectors. Then, select the credential that will be used to connect to your Salesforce org and click Next; or, create a new Salesforce Feeds v2 credential for use in this flow.

Select the Objects to Ingest

After authenticating, Nexla lists the Salesforce objects discovered in your org. Select one or more objects to ingest. Each selected object becomes its own feed, and the fields available for that object are read from Salesforce automatically.

The following source settings control how each feed is read:

• Sync strategy — Choose Auto-increment to load only records changed since the previous run (incremental), or Full ingest to load all records on every run. Auto-increment is the default.

• Start Date — The earliest date from which to load data. Leave the default (1970-01-01T00:00:00Z) to load all history, or enter a date in the format YYYY-MM-DDTHH:mm:ssZ (for example, 2023-01-01T00:00:00Z) to begin from a later point. This is most useful with the auto-increment strategy to bound the initial backfill.

• Salesforce API Version — The Salesforce REST API version used for extraction (default v59.0). Use the version supported by your org; the latest stable version is recommended unless you need compatibility with an older feature.

Salesforce query responses are paginated. Nexla follows the Salesforce nextRecordsUrl links automatically while reading each feed, so a run ingests all available pages for the selected objects.

Schedule and Activate

Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, auto-increment feeds load records changed since the last successful run, and full-ingest feeds reload the complete object.

Reference

For object schemas, field definitions, and query syntax, see the Salesforce REST API Developer Guide and the Salesforce Object Reference.