Salesforce Destination
Salesforce Destination
Send your standardized People and Organizations data to Salesforce CRM. Salesforce destination provides enterprise-grade data delivery with comprehensive validation and Salesforce-specific features.
β‘ Enterprise Destination
Salesforce destination includes enterprise features like validation rule compliance, trigger compatibility, and comprehensive field-level security support.
Supported Object Mappings
Salesforce destination accepts the following standardized objects:
π₯ People β Contacts
- Target Object: Salesforce Contacts
- Required Fields: Email address
- Default Fields: Email, first name, last name
- Key Features: Account association, validation rule compliance, trigger compatibility
π’ Organizations β Accounts
- Target Object: Salesforce Accounts
- Required Fields: Account name
- Default Fields: Account name, domain
- Key Features: Hierarchy support, territory management, validation compliance
Authentication
Salesforce destination uses OAuth 2.0 with Connected App requirements:
- OAuth Flow: Salesforce OAuth 2.0 with refresh tokens
- Connected App: Requires dedicated Connected App configuration
- Scopes Required:
api
- Access to Salesforce APIsrefresh_token
- Offline accessid
- User identity information
- Security: IP restrictions and session policies respected
- Token Management: Automatic refresh with secure storage
Field Mappings
People β Contacts
Outrun Field | Salesforce Field | Required | Type | Description |
---|---|---|---|---|
emailAddress |
Email |
β | String | Primary email address (required) |
firstName |
FirstName |
β | String | Contact's first name |
lastName |
LastName |
β | String | Contact's last name |
phoneNumbers[].number |
Phone |
β | String | Primary phone number |
phoneNumbers[].number |
MobilePhone |
β | String | Mobile phone number |
addresses[].street |
MailingStreet |
β | String | Mailing street address |
addresses[].city |
MailingCity |
β | String | Mailing city |
addresses[].state |
MailingState |
β | String | Mailing state/province |
addresses[].country |
MailingCountry |
β | String | Mailing country |
addresses[].postalCode |
MailingPostalCode |
β | String | Mailing postal code |
associations[].role |
Title |
β | String | Job title |
associations[].id |
AccountId |
β | String | Associated account ID |
Organizations β Accounts
Outrun Field | Salesforce Field | Required | Type | Description |
---|---|---|---|---|
companyName |
Name |
β | String | Account name (required) |
website |
Website |
β | String | Company website URL |
phoneNumbers[].number |
Phone |
β | String | Primary phone number |
addresses[].street |
BillingStreet |
β | String | Billing street address |
addresses[].city |
BillingCity |
β | String | Billing city |
addresses[].state |
BillingState |
β | String | Billing state/province |
addresses[].country |
BillingCountry |
β | String | Billing country |
addresses[].postalCode |
BillingPostalCode |
β | String | Billing postal code |
industry |
Industry |
β | Picklist | Industry classification |
description |
Description |
β | String | Account description |
numberOfEmployees |
NumberOfEmployees |
β | Number | Employee count |
annualRevenue |
AnnualRevenue |
β | Currency | Annual revenue |
Rate Limits & Performance
Salesforce destination has enterprise-grade rate limiting:
- Destination Writes: 10 requests per second
- Bulk API: Used for large data operations
- Governor Limits: All Salesforce limits respected
- Retry Logic: Intelligent retry with exponential backoff
π’ Enterprise Performance
Salesforce destination leverages Bulk API for large operations and respects all governor limits while providing enterprise-grade performance and reliability.
Data Validation & Processing
Salesforce Validation Rules
- Custom Validation: All custom validation rules are respected
- Required Fields: Salesforce required fields enforced
- Field Dependencies: Dependent picklist values handled
- Formula Fields: Read-only formula fields skipped appropriately
Data Type Handling
- Picklist Values: Validation against valid picklist options
- Currency Fields: Proper currency handling with org settings
- Date/DateTime: Timezone-aware date handling
- Lookup Fields: Proper relationship handling and validation
Deduplication Strategy
- Email-Based: Contacts deduplicated by email address
- Name-Based: Accounts deduplicated by name when domain unavailable
- Custom Logic: Support for custom deduplication rules
- Merge Behavior: Configurable merge vs update behavior
Salesforce-Specific Features
Record Types
- Support: Full record type support for Contacts and Accounts
- Assignment: Automatic record type assignment based on rules
- Validation: Record type-specific validation rules respected
- Flexibility: Configurable record type mapping
Triggers and Workflows
- Trigger Execution: Salesforce triggers fire normally during writes
- Workflow Rules: Process Builder and Flow compatibility
- Automation: Integration with Salesforce automation tools
- Event Handling: Proper event generation for downstream processes
Territory Management
- Territory Assignment: Automatic territory assignment for accounts
- Sharing Rules: Salesforce sharing model respected
- Visibility: Field-level security and record access honored
- Compliance: Full compliance with Salesforce security model
Custom Fields
- Standard Support: All standard fields mapped automatically
- Custom Fields: Custom field mapping configurable
- Field Types: Support for all Salesforce field types
- Validation: Custom field validation rules respected
Sync Behavior
Write Operations
- Upsert Logic: Intelligent create-or-update behavior
- Bulk Processing: Efficient bulk operations for large datasets
- Transaction Handling: Proper transaction management
- Error Recovery: Comprehensive error handling and recovery
Salesforce Integration
- API Versions: Latest Salesforce API version support
- Feature Compatibility: Support for latest Salesforce features
- Edition Support: Works with all Salesforce editions
- Sandbox Support: Full sandbox environment support
Performance Optimization
- Bulk API: Automatic use of Bulk API for large operations
- Selective Updates: Only changed fields are updated
- Batch Optimization: Intelligent batching for optimal performance
- Governor Limit Management: Proactive governor limit monitoring
Best Practices
Setup Recommendations
- Connected App: Create dedicated Connected App for Outrun
- User Permissions: Use integration user with appropriate permissions
- Field Mapping: Review and test field mappings thoroughly
- Validation Rules: Understand and plan for validation rules
Data Quality
- Required Fields: Ensure all Salesforce required fields are populated
- Picklist Values: Validate picklist values against Salesforce org
- Data Types: Ensure proper data type formatting
- Relationships: Plan Account-Contact relationship strategy
Performance Optimization
- Bulk Operations: Use bulk operations for large data sets
- Selective Sync: Only sync necessary fields and records
- Governor Limits: Monitor API usage and governor limits
- Timing: Schedule large syncs during off-peak hours
Security & Compliance
- Field-Level Security: Review field-level security settings
- Sharing Rules: Understand sharing model implications
- IP Restrictions: Configure appropriate IP restrictions
- Audit Trail: Enable field history tracking as needed
Troubleshooting
Common Issues
Authentication Failures
- Verify Connected App configuration and permissions
- Check OAuth scopes and user permissions
- Ensure IP restrictions allow Outrun access
- Confirm user account is active and not locked
Validation Errors
- Review Salesforce validation rules and requirements
- Check required field mappings and data
- Verify picklist values against org configuration
- Confirm field-level security permissions
Governor Limit Issues
- Monitor API usage in Salesforce Setup
- Check for other integrations consuming limits
- Consider bulk operations for large data sets
- Review and optimize sync frequency
Data Quality Issues
- Verify field mappings match Salesforce schema
- Check data type compatibility and formatting
- Review duplicate handling and merge logic
- Confirm relationship field mappings
Performance Issues
Slow Sync Performance
- Enable Bulk API for large operations
- Optimize field selection and filtering
- Review batch sizes and timing
- Check for complex validation rules or triggers
Rate Limit Errors
- Monitor concurrent API usage
- Adjust sync frequency and batch sizes
- Consider upgrading Salesforce edition
- Implement intelligent retry logic
Support Resources
- Salesforce Developer Documentation: developer.salesforce.com
- Trailhead: trailhead.salesforce.com
- Salesforce Help: help.salesforce.com
- Outrun Support: support@getoutrun.com
- Community: Discord
Use Cases
Enterprise CRM Consolidation
- Multi-Org Sync: Consolidate data across multiple Salesforce orgs
- System Migration: Migrate data from legacy systems to Salesforce
- Data Standardization: Standardize data across business units
Sales Operations
- Lead Enrichment: Enrich Salesforce leads with external data
- Account Intelligence: Enhance account records with comprehensive data
- Territory Management: Support complex territory assignment rules
Marketing Integration
- Campaign Data: Sync marketing data into Salesforce campaigns
- Lead Scoring: Integrate lead scoring data from external systems
- Attribution: Track marketing attribution across multiple touchpoints
Ready to configure Salesforce as a destination? Follow our Getting Started guide to set up your first destination sync.