Salesforce integration

Last updated: November 10, 2026

Connect Salesforce to CRED to bring your Salesforce records into CRED and write changes back. This article covers what's specific to Salesforce. For how sync works in general, see the CRM integrations overview.

What CRED syncs

Salesforce object

In CRED

CRED can write back

Account

Account

Yes

Contact

Contact

Yes

Lead

Lead

Yes

Opportunity

Opportunity

Yes

OpportunityContactRole

Opportunity contact role

Yes

OpportunityLineItem

Opportunity product

Yes

Product2

Product

No

BusinessProcess

Opportunity pipeline

No

OpportunityStage

Opportunity stage

No

Campaign

Campaign

Yes

CampaignMember

Campaign member

Yes

Task (including logged calls)

Task

Yes

Event

Meeting

Yes

ContentNote

Note

Yes

Case

Case

Yes

ContentVersion

File attachment

No

Conversation

Call transcript

No

User

CRM user (for owners)

No

Custom objects (__c)

Custom object records

Yes

  • Custom fields on any of these objects are found automatically and can be mapped in the wizard.

  • Custom objects are found automatically. Choose the ones you want in the wizard's Choose objects step.

  • Email messages (EmailMessage) can be read into contact and account timelines. This may not be enabled for your workspace yet; contact support to turn it on.

  • CRED uses Salesforce API version 68.0.

Before you connect

  • The Salesforce user you connect with needs API Enabled on their profile. Salesforce editions without API access can't connect.

  • CRED can see and edit exactly what that user can. Give the user read and edit access to every object and field you plan to sync, including field-level security.

  • Use a dedicated integration user rather than a person's own login, so the connection doesn't depend on one employee.

  • CRED connects to Salesforce production orgs. To connect a sandbox, contact support@credplatform.com.

How to connect Salesforce

  1. Open Integrations in the left navigation and find Salesforce under CRM & Sales.

  2. Click Connect (or Enable) on the tile and continue to Salesforce.

  3. Sign in and approve access. CRED asks for two permissions: access and manage your data (api), and perform requests at any time (refresh_token), so it can stay signed in between syncs.

  4. Back in CRED, the integration wizard opens. Choose Automatic or Custom setup, pick the objects to sync, map fields and set write rules. See the overview for each step.

To change settings later, click Settings on the Salesforce tile. To disconnect, click Disconnect on the tile. Disconnecting stops syncing; records already in CRED and Salesforce stay where they are.

How Salesforce sync works

  • First read: CRED reads each object you chose, in order (users, pipelines and stages first, then accounts and contacts, then opportunities and activity). Large orgs can take several hours.

  • Ongoing reads: about once an hour, CRED reads the records whose LastModifiedDate changed since the last sync. Very large reads use the Salesforce Bulk API automatically.

  • On demand: Pull latest from Salesforce on a company or person's sidebar re-reads that record now. Pull all changes since last sync in the connection's settings panel reads every recent change.

  • Real-time sync: with Salesforce change events, changes to the listed objects reach CRED within seconds. This may not be enabled for your workspace yet; contact support to turn it on. The panel shows each object's status, for example Real-time, Scheduled (over Salesforce's change-event limit) or Scheduled (missing Salesforce permission).

  • Deleted records: CRED checks for records deleted in Salesforce in the last 29 days and removes them from CRED.

  • Writing back: depends on each object's Update Rule and Create Rule and each field's write rule. See the overview.

API usage

Salesforce limits how many API calls an org can make in 24 hours, shared across every app connected to your org. A large first read uses part of that allowance. If Salesforce returns REQUEST_LIMIT_EXCEEDED, CRED waits and retries automatically. If it keeps failing, the error appears in Sync Health; sync again once your allowance resets.

Troubleshooting

Salesforce error

What it means

What to do

INSUFFICIENT_ACCESS_OR_READONLY or INSUFFICIENT_ACCESS

The connected user can't edit this object or field (often field-level security).

Grant edit access on the user's profile or a permission set, then sync again. You don't need to reconnect.

FIELD_CUSTOM_VALIDATION_EXCEPTION

A Salesforce validation rule rejected the value.

Fix the value in CRED, or adjust the validation rule.

REQUIRED_FIELD_MISSING

Salesforce requires a field CRED didn't send.

Map that field, or mark it Is Required? in CRED so records without it are held back.

INVALID_FIELD

The field was renamed or deleted in Salesforce.

Update the mapping in the wizard.

UNABLE_TO_LOCK_ROW

Another process in Salesforce was editing the record.

CRED retries automatically. If it keeps happening, check long-running jobs in Salesforce.

REQUEST_LIMIT_EXCEEDED

Your org used its daily API allowance.

Wait for the allowance to reset, or ask your Salesforce admin about a higher limit.

The tile says Relink Needed. Salesforce revoked or expired CRED's access. Click Relink and sign in again. No data is lost.

Records aren't being created in Salesforce. Check the object's Create Rule. With Manual, CRED only creates a record when you click Sync to CRM and no match is found.

Duplicates in Salesforce. Set the Create Rule to Manual or Off, and review matches on the Matching page.

For record-level errors and missing required fields, see Fixing CRM sync issues. When you contact support@credplatform.com, include the record name, the field, and the error from Data Sync Log or Sync Health.

Related articles