A Salesforce-synced company list is linked 1:1 to a Salesforce list view. CTD pulls the latest set of accounts from Salesforce once per day, so whatever is in your Salesforce list is reflected in CTD automatically — no manual imports, no CSV exports. If a company gets added to or removed from the Salesforce list, CTD updates the next time the sync runs.

This is the right choice when Salesforce is the system of record for your target accounts and you want CTD's warm path intelligence layered on top without managing two lists separately.

How the sync works

  • You select a Salesforce list view (e.g., a specific Account list view like "Q3 Target Accounts") when creating the CTD list.
  • CTD reads that list view once per day and updates the CTD list to match.
  • The sync is one-way: Salesforce drives the membership. Changes you make to the list in CTD (e.g., notes, Board column positions) are not written back to Salesforce.
  • If the Salesforce list view is updated — companies added, removed, or re-filtered — CTD reflects those changes within 24 hours.
Prerequisite: Your CTD workspace must have the Salesforce integration connected. If you don't see Salesforce as an option when creating a list, contact your CTD admin to set up the integration. See Salesforce integration.

Walkthrough

📹 Walkthrough coming soon.

What stays in CTD vs. what Salesforce controls

Controlled by SalesforceControlled in CTD
Which companies are on the listNotes and annotations per company
Company additions and removalsBoard column positions and statuses
Sync frequency (daily)Persona filters in Paths view
Sharing settings and collaborators

Use cases

Sales team using Salesforce as the TAL source of truth

A VP of Sales maintains the official target account list as a Salesforce Account list view, filtered by territory and deal stage. Rather than exporting to a spreadsheet and re-importing to CTD, they create a Salesforce-synced list. Every morning, CTD reflects the latest accounts, and the sales team can jump straight into Paths view to find warm intros — without ever leaving CTD to check who's on the list.

RevOps team syncing a tiered account program

A RevOps team maintains three Salesforce list views: Tier 1, Tier 2, and Tier 3 target accounts. They create three corresponding CTD lists, one synced to each view. Sales leadership can quickly switch between tiers in CTD to see relationship density and warm path coverage — a useful input for quarterly territory planning.

Account management tracking renewal accounts

A customer success team creates a Salesforce list view of accounts with renewals due in the next 90 days, then links it to a CTD list. The CS team uses CTD's Paths view to see which teammates have existing relationships with key stakeholders at each account — making it easier to identify who should lead the renewal conversation before it becomes urgent.

Enterprise AE using Salesforce-managed named accounts

An enterprise AE is assigned a named account list managed centrally in Salesforce by their Sales Ops team. Rather than trying to stay in sync with Sales Ops manually, they connect the Salesforce list directly to CTD. When Sales Ops adds or removes accounts — due to territory changes or account reassignments — CTD automatically stays in sync.

Tip: The Salesforce sync is read-only from CTD's perspective — it won't modify your Salesforce data. Any status updates, column moves, or notes you add in CTD stay in CTD only. This makes it safe to use even if multiple teams are working from the same Salesforce list.