Integrating Draftboard with Salesforce

Relationship Data Where Reps Already Work

Your reps live in Salesforce. If relationship intelligence is locked in a separate tool, it won't get used. This guide covers how to bring Draftboard data directly into Salesforce.

What You Can Build

Best connector to this account
Relationship score
Path context (where they worked together)

A new high-value account has a strong warm path
A stalled opportunity has an untapped connection
A target contact changes jobs to a prospect account

3. Prioritization Scoring Include relationship strength in your lead/account scoring model.

Network coverage by territory
Pipeline influenced by relationships
Connector performance

Integration Approaches

Option 1: Native Integration (Coming Soon) Managed package with out-of-the-box functionality.

Option 2: API + Flow Use Salesforce Flows to call the Draftboard API and update records.

Option 3: API + Middleware Use Zapier, Workato, or a custom integration layer.

Option 4: Data Sync Periodic batch sync via data loader or integration tool.

Setting Up with Flows

Step 1: Create Custom Fields

`Best_Connector__c` (Text)
`Relationship_Score__c` (Number)
`Path_Context__c` (Long Text)
`Has_Warm_Path__c` (Checkbox)

`Connector_Name__c` (Text)
`Relationship_Score__c` (Number)
`Shared_Company__c` (Text)

Step 2: Create an External Service

Register the Draftboard API as an External Service: 1. Setup → External Services 2. Add new service with Draftboard API spec 3. Configure authentication (API key)

Step 3: Build the Flow

Create a Record-Triggered Flow on Account: 1. Trigger: Account is created or updated 2. Action: Call Draftboard API with account domain 3. Action: Update custom fields with response data

Step 4: Display in Page Layout

Add the custom fields to your Account and Contact page layouts, or create a custom Lightning component for richer display.

Example: Account Page Component

What reps see:

┌─────────────────────────────────────────┐
│ 🔗 Warm Paths to Acme Corp              │
├─────────────────────────────────────────┤
│ Mike Chen (Score: 85)                   │
│ ├─ Worked with Sarah Johnson at Stripe  │
│ └─ 3 year overlap, ended 2023           │
│                                         │
│ Lisa Park (Score: 62)                   │
│ ├─ Direct LinkedIn connection           │
│ └─ 12 mutual connections                │
│                                         │
│ [Request Intro] [View All Paths]        │
└─────────────────────────────────────────┘

Using Relationship Data in Lead Scoring

Add relationship as a scoring factor:

Factor	Points
ICP match	0-30
Intent signals	0-25
Relationship score	0-25
Engagement	0-20

Implementation: 1. Sync relationship scores nightly 2. Include in Process Builder or Flow scoring logic 3. Higher relationship scores = higher priority

Building Dashboards

Accounts with warm paths vs. no paths (pie chart)
Average relationship score by territory (bar chart)
Top connectors by paths available (leaderboard)

Pipeline by lead source (warm intro vs. other)
Win rate by relationship score tier
Cycle time by relationship involvement

Automation Ideas

High-Value Account Alert: When an account matching ICP criteria is created AND has a relationship score > 70, alert the account owner and suggested connector via Slack.

Stalled Opportunity Path Check: When an opportunity has been in the same stage for 14+ days, check for untapped warm paths and notify the AE.

Champion Change Detection: When a contact at a closed-won account moves to a new company, check if the new company is in your target list and surface the warm path.

Best Practices

Keep it simple initially: Start with basic fields on Account/Contact. Add complexity once adoption is proven.

Train the team: Reps need to understand what relationship scores mean and how to act on them.

Measure impact: Track win rates and cycle times for deals with warm path involvement vs. without.

Maintain data quality: Stale relationship data is worse than no data. Set up regular sync cadence.

Troubleshooting

API rate limits: Use batch sync for bulk operations. Real-time lookup for individual records.

Data latency: If using batch sync, set expectations that data refreshes nightly (or your chosen cadence).

Missing paths: Ensure all team members have connected their LinkedIn in Draftboard.

Conclusion

Bringing Draftboard data into Salesforce puts relationship intelligence where your reps already work. They can see warm paths without switching tools, prioritize accounts with stronger relationships, and track the impact of relationship-driven selling.