Integrating Draftboard with Salesforce

Updated September 28, 2026: the API details below now match the current Integration API reference.

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 with the Draftboard Integration API.

What You Can Build

1. Relationship Fields on Records

Add custom fields showing:

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

2. Warm Path Alerts

Trigger notifications when:

A new high-value account has a strong warm path
A stalled opportunity has an untapped connection

3. Prioritization Scoring

Include relationship strength in your lead/account scoring model.

4. Reports & Dashboards

Track:

Network coverage by territory
Pipeline influenced by relationships
Connector performance

Integration Approaches

All of these call the same API. Create a token in the Draftboard app under Settings → API Keys; the full reference is at intros.draftboard.com/api.

Option 1: API + Flow

Call the Draftboard API from an invocable Apex action that your Flows use, and update records with the response.

Option 2: API + Middleware

Use Zapier, Workato, or a custom integration layer to call the API and write to Salesforce.

Option 3: Scheduled Sync

Pull relationship data on a schedule and load it into Salesforce. GET /api/v1/integration/targets and GET /api/v1/integration/targets/{target_id}/connections accept updatedSince, so each run can fetch only what changed.

Setting Up with Flows

Step 1: Create Custom Fields

On the Account object:

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

On the Contact object:

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

Step 2: Store the Token

Keep the token out of your code:

Create a Named Credential for https://intros.draftboard.com
Have it send the header Authorization: Bearer followed by your Draftboard token on every request
Reference the Named Credential from your Apex callouts

A missing or revoked token gets a 403 from the API, not a 401.

Step 3: Build the Flow

Create a Record-Triggered Flow on Account:

Trigger: Account is created or updated
Action: Call your Apex action with the account name. It looks the company up with GET /api/v1/integration/accounts?query=(account name), lists its targets with GET /api/v1/integration/targets?accountId=(the account's id), and reads the paths to the strongest target with GET /api/v1/integration/targets/{target_id}/connections
Action: Update custom fields with the response data

Draftboard's company search matches by company name (or a saved person's name or title), not by domain, and only returns companies where you have saved targets.

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           │
│   Your teammate Ana Ruiz knows Mike     │
│                                         │
│ Lisa Park (Score: 62)                   │
│ ├─ Studied with Sarah at Michigan       │
│ └─ 12 mutual connections                │
│                                         │
│ [Mark intro requested]                  │
└─────────────────────────────────────────┘

Each line comes from a path's scoreDetails and relationshipDetails, and the teammate from its owners. The button can call POST /api/v1/integration/intros/{intro_id}/requested with the path's id, so Draftboard shows the intro as requested too.

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:

Sync relationship scores nightly
Include them in your Flow scoring logic
Higher relationship scores = higher priority

Building Dashboards

Network Coverage Dashboard:

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

Pipeline Influence Dashboard:

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 Follow-up:

When your CRM records that a contact at a closed-won account has moved to a new company, look that company up with GET /api/v1/integration/accounts and surface any warm path you hold there.

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:

Reads and writes have separate per-minute limits, and a write counts against both. Every response carries X-RateLimit-Limit-{read|write}, X-RateLimit-Remaining-{read|write}, and X-RateLimit-Reset-{read|write} for each bucket. Over a limit, the API returns 429 with the code rate_limited; X-RateLimit-Reset-{read|write} tells you when to retry. Use a scheduled sync with updatedSince for bulk work and real-time lookups for individual records. The current limits are in the reference.

Data latency:

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

Missing paths:

GET /api/v1/integration/targets lists only targets that already have a path, and paths for newly added targets are found asynchronously. To check that a person is in Draftboard at all, use GET /api/v1/integration/targets/resolve with their LinkedIn URL, then poll their connections.

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.

Want the same answers in ChatGPT, Claude, or Codex instead? Connect Draftboard's hosted MCP server - it needs no token.