Source connector

Salesforce Service Cloud connector

Salesforce Service Cloud integration for databases, warehouses and BI tools

Salesforce case management for support and field service. Datrise captures Salesforce Service Cloud entities such as cases, contacts, accounts, entitlements, milestones and case comments, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Salesforce REST API v68.0 (Winter '27) + Bulk API 2.0 — Service Cloud objects (Case, KnowledgeArticleVersion, Entitlement) authenticates with OAuth 2.0, JWT, username / password, incremental runs key on SystemModstamp, and Salesforce Service Cloud caps calls at 100,000 REST/SOAP/Bulk/Connect API calls per rolling 24 hours per org on Enterprise Edition (higher on Unlimited/Performance Edition, scaling with purchased user licenses) — shared across all Salesforce clouds on the org, not a Service Cloud-specific pool.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `salesforce_service_cloud_cases`) with a schema derived from the Salesforce Service Cloud API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Salesforce Service Cloud pipeline page, and join the waitlist to get the Salesforce Service Cloud connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Salesforce Service Cloud data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
cases	salesforce_service_cloud_cases	Upsert by primary key, incremental on updated-at
contacts	salesforce_service_cloud_contacts	Upsert by primary key, incremental on updated-at
accounts	salesforce_service_cloud_accounts	Upsert by primary key, incremental on updated-at
entitlements	salesforce_service_cloud_entitlements	Upsert by primary key, incremental on updated-at
milestones	salesforce_service_cloud_milestones	Upsert by primary key, incremental on updated-at
case comments	salesforce_service_cloud_case_comments	Upsert by primary key, incremental on updated-at

Salesforce Service Cloud API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Salesforce REST API v68.0 (Winter '27) + Bulk API 2.0 — Service Cloud objects (Case, KnowledgeArticleVersion, Entitlement)
Authentication	OAuth 2.0, JWT, username / password — Same Connected App / OAuth 2.0 layer as core Salesforce; the JWT Bearer flow (RSA-SHA256 signed) is the recommended server-to-server option and requires the standard `api` and `refresh_token` scopes plus access to the relevant Service Cloud objects.
Pagination	token — SOQL `query`/`queryAll` against Case, KnowledgeArticleVersion, or Entitlement returns up to 2,000 records per page with `done`/`nextRecordsUrl`; page by GETing `nextRecordsUrl` until `done: true`.
Rate limit	100,000 REST/SOAP/Bulk/Connect API calls per rolling 24 hours per org on Enterprise Edition (higher on Unlimited/Performance Edition, scaling with purchased user licenses) — shared across all Salesforce clouds on the org, not a Service Cloud-specific pool
Incremental cursor	SystemModstamp — SystemModstamp also advances on formula/rollup recalculation and on Entitlement milestone timer updates, so LastModifiedDate is the narrower field when only direct user edits matter.
Webhooks	Yes — Change Data Capture / Platform Events (Streaming API), including CaseChangeEvent
Bulk export	Yes — Bulk API 2.0
Deletes detectable	Yes — `queryAll ... WHERE IsDeleted = true ALL ROWS` surfaces Recycle Bin records for Case/Entitlement for up to the 15-day retention window; Knowledge articles instead move through a PublishStatus of Archived before they can be deleted

Official API reference

What bites when replicating Salesforce Service Cloud

KnowledgeArticleVersion is a restricted-query object: SOQL against it does not support `OR` conditions and effectively requires filtering by `PublishStatus` and `Language`, so it can't be pulled with the same generic query pattern used for Case or Account.
Editing a published Knowledge article creates a new KnowledgeArticleVersion row rather than updating the existing one, so a connector keyed on article `KnowledgeArticleId` must also track `VersionNumber`/`PublishStatus` to avoid treating each edit as a brand-new duplicate article.
Entitlement and EntitlementProcess milestone timers (e.g. Case Milestone due dates) recalculate on business-hours changes independent of any user edit, so extraction keyed only on `LastModifiedDate` can miss milestone-driven updates that `SystemModstamp` would still catch.
Case Feed attachments live in `ContentVersion`/`ContentDocumentLink`, not on the Case record itself, so replicating case attachments needs a second query joined on `ContentDocumentLink.LinkedEntityId = Case.Id`.

Compare this against every other documented API

Popular destinations for Salesforce Service Cloud

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Salesforce Service Cloud connector FAQ

What Salesforce Service Cloud data does the connector extract?: 6 objects: cases, contacts, accounts, entitlements, milestones and case comments. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Salesforce Service Cloud integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Salesforce Service Cloud data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Salesforce Service Cloud → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Salesforce Service Cloud pipeline with guided onboarding

Join the waitlist to get priority access for Salesforce Service Cloud integrations with guided setup, schema-aware mapping, and production-grade incremental sync.