Overview
The Salesforce integration enables workflow triggers when opportunities reach specific stages, automatic data synchronization, and rich CRM context for AI-powered features. [SCREENSHOT: Salesforce integration connected status] Caption: Salesforce integration connected and ready for workflow triggersBenefits
Workflow Triggers
Opportunities reaching stages automatically trigger Thread workflows
Rich Data Sync
Opportunity data, contacts, and notes flow into Thread
AI Context
Salesforce notes and history power handoff generation
Enterprise Ready
Full support for Salesforce enterprise features
Setup Instructions
Prerequisites
- Salesforce Sales Cloud (Professional or higher)
- System Administrator or delegated admin permissions
- Thread account with admin role
- API access enabled in Salesforce
Step 1: Connect OAuth
Choose Environment
Select your Salesforce environment:
- Production - Live Salesforce org
- Sandbox - Test environment (for setup/testing)
Authorize Thread
Redirected to Salesforce login → Sign in → Review permissions → Click “Allow”Permissions requested:
- Read opportunities
- Read accounts
- Read contacts
- Read notes and attachments
- Access custom objects (if configured)
Step 2: Configure Workflow Triggers
Salesforce triggers are configured in workflows, not in the connector settings.Select Trigger Stage
Choose which opportunity stage triggers the workflow:
- “Closed Won” (most common)
- “Contract Sent”
- Custom stages
Test the Trigger
Create a test opportunity:
- Move to your trigger stage
- Wait 1-2 minutes
- Check workflow runs
- Verify data captured correctly
How It Works
Trigger Flow
Data Available to Workflows
| Salesforce Object | Available Data |
|---|---|
| Opportunity | Name, Amount, Stage, Close Date, Owner |
| Account | Company name, Website, Industry, Size |
| Contacts | Name, Email, Phone, Title |
| Notes | All notes attached to opportunity |
| Custom Fields | Any mapped custom fields |
Field Mappings
Standard Mappings
| Salesforce Field | Thread Field | Notes |
|---|---|---|
| Opportunity Name | Account Name | Can be customized |
| Amount | ARR | Automatic conversion |
| Close Date | Close Date | Format normalized |
| Account Name | Company Name | From related account |
| Opportunity Owner | AE Email | For handoff |
| Primary Contact | Primary Contact | From contact role |
Custom Field Mappings
Map additional Salesforce fields to Thread:Use Cases
1. Automated Account Creation
Scenario: When sales closes a deal, automatically create the Thread account. Workflow:2. Segment-Based Routing
Scenario: Route enterprise deals differently than SMB. Workflow:3. Manager Approval Gate
Scenario: High-value deals require manager approval before onboarding. Workflow:Troubleshooting
Connection Failed
Connection Failed
Check:
- You have System Admin or appropriate permissions
- API access is enabled in Salesforce
- IP restrictions allow Thread’s servers
- Log out/in to Salesforce
- Check Salesforce setup audit trail
- Contact Salesforce admin
Workflow Not Triggering
Workflow Not Triggering
Check:
- Workflow is Active (not Draft)
- Correct stage selected in Start node
- Webhook configured in Salesforce
- Test with a sandbox opportunity
- Check workflow run history for errors
- Verify webhook delivery in Salesforce
Missing Data in Thread
Missing Data in Thread
Check:
- Fields are mapped correctly
- Data exists in Salesforce
- Permissions include the fields
- Check field mappings
- Verify opportunity has required data
- Reconnect with full permissions
Duplicate Accounts
Duplicate Accounts
Check:
- Workflow only triggers once per opportunity
- Manual accounts not also being created
- Add condition to check for existing accounts
- Merge duplicate accounts manually
Best Practices
Start with Sandbox
Test the integration in a Salesforce sandbox first
Clean Data
Standardize opportunity names and required fields
Rich Notes
Encourage AEs to add detailed notes for AI context
Monitor Runs
Check first 10-20 workflow runs for issues
Salesforce-Specific Tips
- Use Contact Roles - Primary contact should be set for best data
- Standardize Stages - Consistent stage names improve reliability
- Consider Sandbox - Test complex workflows in sandbox first
- Watch API Limits - High volume may need API limit consideration
Enterprise Features
Multi-Sandbox Support
Connect multiple sandboxes for different purposes:- Development sandbox for testing
- Staging sandbox for validation
- Production for live operations
Custom Objects
If you use custom Salesforce objects:- Contact support to enable custom object access
- Map custom object fields to Thread
Field-Level Security
Thread respects Salesforce field-level security:- Users only see data they have access to
- Restricted fields won’t sync
