CRED × Salesforce — sync, enrichment, troubleshooting

Audience: CRED customers using Salesforce as their CRM.

Purpose: Answer the day-one operational questions about the Salesforce integration — sync cadence, manual triggers, enrichment vs sync, troubleshooting fields that fail to sync, and where to find action logs.

Read this first: CRED × CRM — How the integration works in the CRED UI. That article covers the cross-CRM concepts (sync vs enrichment, update modes, action logs, etc). This article covers the Salesforce-specific behaviour.

Quick answers

1. What CRED syncs from Salesforce

Salesforce has the deepest coverage of any CRM CRED integrates with — 13 entity types:

Custom objects: Fully supported. CRED auto-discovers every custom object accessible to the connected user and lets you opt them in to sync individually.

Custom fields: Auto-discovered on every standard and custom object during initial setup.

Sandbox vs Production: Both are supported. Pick the environment when connecting; sandbox uses test.salesforce.com and the connection is tagged so production data is never accidentally written.

2. When and how often CRED syncs with Salesforce

Initial sync

Triggered immediately after OAuth completes. CRED runs a full DATA_SYNC_READ for each entity type in dependency order, staggered every two minutes:

1. Users

2. Accounts

3. Contacts

4. Custom entity metadata

5. Custom entity records

6. Pipelines (BusinessProcess)

7. Stages (OpportunityStage)

8. Opportunities

9. Campaigns

10. Campaign members

11. Tasks

12. Notes (ContentNote)

13. Transcripts (Conversation)

Total time is org-size-dependent; large orgs (1M+ accounts and contacts) often take overnight to complete. Progress is visible in Settings → Integrations → Salesforce → Sync log.

Ongoing incremental sync

• SOQL queries filter by LastModifiedDate >= the last sync timestamp.

• A new pass is queued shortly after the previous one finishes; new and modified records typically arrive in CRED within a few minutes.

• Deleted records: CRED uses Salesforce's getDeletedRecords() SOAP endpoint to detect deletions in the last 30 days. Records deleted more than 30 days ago are not detected (Salesforce's recycle-bin retention limit) — if you need to clean those up, run a full re-sync.

• If a read task hangs > 15 min it is auto-restarted. Failed Phase-2 records are retried after 4h.

Rate-limit awareness

Salesforce REST API limit is 15,000 calls / 24h per organization across all apps connecting to your org. CRED self-throttles and watches the Limits endpoint — if remaining calls drop below 1,000 we pause sync for an hour to avoid blocking your other Salesforce apps. If you have a small Developer or Essentials org with a low ceiling, contact us — we can lower the throughput target.

Bulk API for very large operations

For initial reads of objects with millions of records, CRED can fall back to the Bulk API (10,000 records / batch, 15 batches / 24h). This is configured per connection — ask your CSM if you need it enabled.

3. How to trigger a manual sync

Salesforce → CRED (pull)

CRED → Salesforce (push)

Manual sync respects update modes — if write-back is OFF, the button is disabled.

4. Sync vs Enrichment with Salesforce

The "Sync with Salesforce" button moves the record's current CRED values to Salesforce. It does not run the CRED enrichment waterfall and does not consume credits. Three ways to combine them:

1. Manual two-step: click Enrich, wait for fields to populate, then click Sync with Salesforce.

2. Workflow: Workflows → trigger on list / signal / create → Enrich → Sync to CRM (Salesforce).

3. Auto-enrich on create: Settings → Integrations → Salesforce → Enrichment → toggle Auto-enrich on create. Every new record gets the waterfall before it's written back.

See the cross-CRM article for the full rationale on why we keep these separate.

5. Mapped fields not passing over — Salesforce-specific troubleshooting

Walk the seven-reason cross-CRM checklist first. Salesforce has three extra reasons:

FLS — the most common Salesforce-specific blocker

Salesforce's Field-Level Security means every field on every object can be hidden / read-only / read-write per profile and per permission set. CRED writes as the user who connected the integration. If that user's profile lacks write access on a field, that field will silently fail with INSUFFICIENT_ACCESS_OR_READONLY.

Recommended setup:

1. Create a dedicated "CRED Integration User" in Salesforce.

2. Give it a profile (or a permission set on top of a base profile) with read+write access to every object and field you want to sync.

3. Connect CRED as that user. This avoids "it works for Alice but not for Bob" classes of bugs.

If you can't create a dedicated user, audit FLS on the connected user's profile for every field in your CRED → Salesforce mapping.

Validation rules

Salesforce validation rules fire on every write. If a CRED-pushed value fails a rule, the write is rejected and logged. Open Salesforce Setup → Object Manager → [object] → Validation Rules to audit.

Required-on-layout fields

A field can be marked "required" on the page layout (separate from "required on the object"). If CRED isn't pushing that field, the write fails. Either map the field in CRED or move "required" to a default in Salesforce.

6. Action logs

Same four locations as every CRM. Salesforce specifics:

• Record Activity tab in CRED shows the Salesforce Id for every sync attempt — copy/paste it into Salesforce's URL bar to jump to the record.

• Each error log entry includes the Salesforce errorCode, fields[] array (which fields the error applies to), and the API call's requestId. The requestId can be used by Salesforce support to trace the failure in their logs.

• Salesforce Setup → Setup Audit Trail (in Salesforce, not CRED) lists permission and metadata changes — useful when "this used to work" but now doesn't.

• If a sync fails with UNABLE_TO_LOCK_ROW repeatedly on the same record, check Salesforce's Setup → Apex Jobs for long-running batch jobs touching that object.

7. Salesforce integration limits and known constraints

Things that look like a sync bug but aren't

• Person Accounts are partially supported. Standard B2B accounts work without caveats; if your org uses Person Accounts, a few fields behave differently — talk to your CSM before mapping.

• Multi-currency orgs: Opportunity amounts respect the CurrencyIsoCode on the record. CRED converts to the connection's default for display but stores the original currency.

• Record types: If an object has multiple record types, CRED defaults to the user's default record type for new records. Specify the record type in the field mapping if you need a non-default.

8. Reference — CRED-side technical detail

• Library: jsforce (Salesforce JavaScript SDK)

• API version: 62.0

• Query language: SOQL with cursor pagination via nextRecordsUrl

• Auth: OAuth 2.0 Authorization Code with automatic token refresh

• Production OAuth host: login.salesforce.com

• Sandbox OAuth host: test.salesforce.com

Useful Salesforce links

• REST API Developer Guide

• SOQL Reference

• Bulk API 2.0

• API Limits