Salesforce Connector

Load eligible Salesforce objects into your warehouse, or activate selected warehouse data back into Salesforce.

SourceDestinationGold

Evaluating against Fivetran? See how Supaflow handles Salesforce pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Load Salesforce into Snowflake

Dedicated pages for destination-specific setup, buyer questions, and Snowflake sync behavior.

Salesforce to Snowflake

Sync eligible Salesforce standard and custom objects with scheduled incremental reads and bulk extraction.

View pipeline page

Setup a Salesforce Source in Supaflow

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

OAuth or Basic Authentication

Use browser-based OAuth by default, or connect with a Salesforce username, password, and security token. Production, sandbox, and custom My Domain hosts are supported.

Standard and Custom Object Discovery

Discover API-accessible standard and custom objects and the fields the connected Salesforce user can read. Objects Salesforce does not expose to the connected user may not appear in discovery; returned objects without a usable incremental timestamp are skipped with a reason.

Scheduled Incremental Extraction

Use a filterable Salesforce timestamp for each eligible object and an optional lookback for late-arriving updates. This is cursor-based incremental sync, not Salesforce CDC.

Bulk Reads with Fallback

Use Salesforce bulk extraction for large supported objects by default, with the synchronous API path available when a read is not supported by the bulk path.

Salesforce Activation

Use Salesforce as a destination for selected warehouse attributes and operational activation workflows. Source extraction and destination writes are configured as separate pipelines.

Supported Objects

Sales and CRM

Account and Contact

Organizations and the people associated with them.

Opportunity and Lead

Sales opportunities and prospects.

OpportunityLineItem and Pricebook2

Opportunity products and price-book records.

Service and Activity

Case and CaseComment

Customer service records and their comments.

Task and Event

Supported activity and calendar records.

Org-Specific Data

Custom objects and fields

API-accessible custom objects and fields are discovered when the connected user can read them and the object supports the required query path.

Picklist metadata tables

Optional Supaflow tables provide API values, display labels, and supported dependent-picklist relationships for warehouse joins.

Not Selected for Source Sync

Objects Salesforce cannot query safely

Deprecated, hidden, non-queryable, Big, external, and other restricted object types may be omitted or marked as skipped during source discovery.

Objects without a usable cursor

An object without a filterable SystemModstamp, LastModifiedDate, or CreatedDate field is skipped rather than presented as safely incremental.

How It Works

Prepare the Salesforce user

Confirm API access and object- and field-level read permissions. Configure the OAuth approval or security token required by your organization.

Choose authentication and domain

Select OAuth or Basic authentication, then use the production, sandbox, or custom My Domain host for the Salesforce org.

Test, save, and select objects

Verify the connection, review eligible objects and fields, and select the source data required by the pipeline.

Use Cases

Sales analytics in the warehouse

Analyze accounts, contacts, opportunities, and leads alongside finance, product, and support data.

Picklist-aware reporting

Keep Salesforce API values in fact tables while joining optional metadata tables for the labels users see in Salesforce.

Warehouse activation

Send selected scores, segments, or operational attributes back to Salesforce through a separate destination pipeline.

Frequently Asked Questions

Which Salesforce orgs can connect?

The Salesforce org must provide API access to the connecting user. Available objects and fields follow that user’s permissions and the query capabilities Salesforce exposes.

Can Supaflow replicate custom objects and fields?

Yes, when the custom object is API-accessible, queryable, visible to the connected user, and has a usable incremental timestamp. Objects Salesforce does not expose to the connected user may not appear; a returned custom object without a usable incremental timestamp is skipped with a reason.

Does the Salesforce connector use CDC?

No. The source connector uses scheduled cursor-based incremental reads. It does not subscribe to Salesforce Change Data Capture events.

How are deleted Salesforce records handled?

The connector reads records Salesforce still exposes through its all-record path and marks deleted rows when Salesforce returns the deletion indicator. It cannot detect a record after Salesforce permanently purges it.

What happens when OAuth access expires?

Supaflow refreshes OAuth access automatically. Reauthorize the source if the refresh grant is revoked or an administrator changes the Connected App policy.

How do I connect a Salesforce sandbox?

Set Salesforce Domain to the sandbox login host or the sandbox’s custom My Domain. Sandbox credentials and grants remain separate from production.