Salesforce logo
โ†’
Drata logo

Fix Salesforce โ†’ Drata Sync Issues (Not Working, Errors, Duplicates)

๐Ÿ”ง 3 Common Issues

Diagnose and resolve common sync problems. We've documented the 3 most common issues, their root causes, and exactly how to fix them. See step-by-step fixes for duplicates, missing fields, rate limit errors, and connection issues.

critical 40% Frequency

Security controls not syncing from Salesforce to Drata

Also searched as: "Salesforce Drata security controls not syncing from salesforce to drata"

#1 API Permissions Issue 50% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Drata > Settings > Integrations > Salesforce
  2. 2. Check if integration status is 'Connected'
  3. 3. Verify Salesforce connected app permissions
  4. 4. Ensure API user has 'Modify All' permissions on custom objects

โœ“ Solution

Reconnect Salesforce integration in Drata. Verify API user permissions. Check if connected app has access to custom objects.

โฑ๏ธ Est. time: 15 min

#2 Field Mapping Errors 30% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Drata > Integration > Salesforce > Field Mappings
  2. 2. Check if required fields are mapped correctly
  3. 3. Verify data types match between Drata and Salesforce
  4. 4. Look for any validation rule errors in Drata

โœ“ Solution

Update field mappings in Drata. Fix data type mismatches. Resolve Drata validation rules blocking sync.

โฑ๏ธ Est. time: 20 min

#3 Control Type Mismatch 20% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Drata > Controls > Control Types
  2. 2. Check if control types match Salesforce picklist values
  3. 3. Verify control type field mapping configuration

โœ“ Solution

Update control type picklist values in Salesforce to match Drata. Reconfigure field mapping for control type.

โฑ๏ธ Est. time: 10 min

high 30% Frequency

Salesforce cases not creating Drata incident reports

Also searched as: "Salesforce Drata salesforce cases not creating drata incident reports"

#1 Case Object Configuration 40% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Salesforce > Setup > Objects and Fields > Object Manager > Case
  2. 2. Check if case record type configuration matches Drata settings
  3. 3. Verify required fields for incident creation
  4. 4. Check if case assignment rules are active

โœ“ Solution

Update case record type configuration. Ensure required fields are optional or pre-populated. Verify assignment rules are active.

โฑ๏ธ Est. time: 15 min

#2 Custom Field Requirements 35% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Drata > Integration > Salesforce > Field Mappings > Incidents
  2. 2. Check if all required custom fields are mapped
  3. 3. Verify field-level security settings for API user
  4. 4. Look for validation rule errors on incident creation

โœ“ Solution

Update field mappings to include required custom fields. Adjust field-level security. Fix validation rules blocking incident creation.

โฑ๏ธ Est. time: 20 min

#3 Webhook Failures 25% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Salesforce > Setup > Process Automation > Flow
  2. 2. Check if case creation webhook flow is active
  3. 3. Verify webhook URL and secret
  4. 4. Look for flow failure logs in Salesforce

โœ“ Solution

Reconfigure case creation webhook flow. Verify webhook URL and secret. Check Drata webhook listener configuration.

โฑ๏ธ Est. time: 10 min

medium 25% Frequency

User access data not updating from Salesforce to Drata

Also searched as: "Salesforce Drata user access data not updating from salesforce to drata"

#1 Profile Permissions 45% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Salesforce > Setup > Users > Profiles
  2. 2. Check if API user has 'View All' and 'Modify All' permissions on User object
  3. 3. Verify profile has access to user role and profile fields
  4. 4. Check if field-level security blocks access to certain fields

โœ“ Solution

Update API user profile permissions. Adjust field-level security settings. Ensure user role and profile fields are accessible.

โฑ๏ธ Est. time: 15 min

#2 User Deactivation Workflow 30% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Salesforce > Setup > Process Automation > Workflow Rules
  2. 2. Check if user deactivation workflow is active
  3. 3. Verify workflow rule criteria and actions
  4. 4. Look for workflow failure logs

โœ“ Solution

Update user deactivation workflow. Fix workflow rule criteria. Ensure workflow actions are correctly configured.

โฑ๏ธ Est. time: 20 min

#3 API Rate Limits 25% likely

๐Ÿ“‹ How to Diagnose

  1. 1. Salesforce > Setup > System > System Overview
  2. 2. Check API call limits usage
  3. 3. Verify Drata integration API usage
  4. 4. Look for rate limit exceeded errors in Drata logs

โœ“ Solution

Adjust Drata sync frequency. Implement API call limiting. Consider upgrading Salesforce edition for higher API limits.

โฑ๏ธ Est. time: 10 min

Step 1: Try the Official Integration

Direct connection

Start with the native integration if available. It's usually the most reliable, but may have limitations.

View Setup Guide

Free with your subscription

Step 2: Use Make for Custom Flows

No code automation

Create custom integration workflows with Make's visual designer. It works with almost any API.

Try Make Free โ†’

1000 ops/mo free. No credit card.

Step 3: Self-Hosted with n8n

Full data control

Need complete data privacy? n8n is open-source and self-hostable. Build custom integrations with full control over your data.

Try n8n Free โ†’

Open source. Self-host or cloud. Unlimited ops.

Step 4: Add Human Review

Approval automation

Relay adds human-in-the-loop approvals, Slack/Teams alerts, and conditional logic to your automation.

Try Relay Free โ†’

1000 actions/mo free. No credit card.