The CTD API lets you build triggers in your CRM that fire at key moments in the sales cycle and automatically pull in relationship intelligence. Instead of reps manually checking who knows who, the right information surfaces at the right time — without anyone lifting a finger.

These patterns work with Salesforce and HubSpot natively, or with any CRM via the CTD API and a webhook.

1

CRM event fires

A record change signals it's time to act — a new contact, a stage move, a deal that's gone cold, or a key executive just hired at a target account.

New contact Stage change Deal stuck New opportunity Renewal approaching
2

CTD enriches in real time

The CTD API returns the full relationship picture — warm paths, scores, reachable contacts, job change signals — in milliseconds. No manual lookup. No tab switching.

Warm paths Relationship scores Best connectors Reachable people Job changes
your automation does two things
3a

Surface to your team

Notify the AE, post to Slack, or create a task with the specific insight and a recommended next action.

Slack Email CRM task
3b

Update CRM record

Write relationship scores, path counts, and the best connector's name directly onto the Contact or Account.

Score field Best connector Path count
4a

Rep acts at the right moment

Armed with context they didn't have to find, the AE sends a ghost email, requests an exec intro, or picks up the phone — while the timing is still right.

Ghost email Intro request Call Exec sponsor ask
4b

Data drives the next action

Relationship scores, path counts, and connector names in your CRM power routing rules, rep queues, and sequences — the enrichment keeps working after the trigger fires.

Rep routing Score-based queues Sequence enrollment Exec flagging

New contact created

When a new contact is added to your CRM, call the CTD API and enrich the record immediately. Write back the relationship score, best connector name, and a deep link to the contact's CTD profile. The rep has everything they need to plan their approach before the first outreach — no manual lookup required.

Use GET /reachable-person with the contact's LinkedIn URL or email. If CTD returns a strong score, you can auto-tag the contact as "warm path available" so it surfaces in rep queues and list views.

New lead created

Same enrichment pattern as contacts, but the stakes are higher — a warm connection to a new inbound lead can cut response time from days to hours. Enrich the lead record the moment it's created, and if the relationship score is strong, route it to the rep with the best connection rather than standard round-robin logic. CTD can also fill in missing job titles on leads, a persistent data quality problem for most teams.

New opportunity created

When an opportunity is opened, immediately check which people in your org have connections to the account and surface the best paths to the AE. If any executive — CEO, board member, investor, or advisor — has a strong connection to someone at the account, flag that separately. Executive sponsorship decisions are best made at the start of a deal, not when it's already stuck.

Example: New opportunity at Acme Corp → CTD finds your CEO has a strong connection to Acme's CFO → Slack message to CEO: "New deal opened at Acme. You know their CFO — worth a warm intro from you?"

Opportunity stage changes

Entering early pipeline

Notify the AE with a warm path summary: who in the org knows people at this account, relationship scores, and whether any board members, investors, or advisors are connected. Give the AE a starting point for their intro strategy before the first call.

Entering mid-pipeline

Multi-threading matters at this stage. Trigger a check: does the AE have paths to the economic buyer, the champion, and the technical evaluator? If gaps exist, surface who does have those connections and notify the AE's manager so they can coach on intro strategy in the next 1:1.

Deal stuck — no stage movement

When a deal hasn't moved in a set number of days, check for strong warm paths to key stakeholders that haven't been activated. If a board member knows the prospect's CEO and no intro has been requested, that's an unused lever. Alert the manager with a specific recommendation rather than a generic nudge: "You have a strong path through [Name] to their VP of Engineering — has anyone asked for an intro?"

Entering late pipeline

Executive alignment can make or break a late-stage deal. Trigger a check for C-level connections: if your CEO or CRO knows a decision-maker at the account, this is the moment to activate it. Surface the information to whoever owns executive sponsorship and make it easy to act — ideally with a pre-drafted ghost email they can approve in one click.

New account added to target list

When an account is added to your target list, enrich it immediately with CTD data — relationship score, number of warm paths, and best connectors. Accounts with strong network coverage can be prioritized for outbound and assigned to the rep with the most relevant connections, rather than by territory alone.

New executive hired at a target account

CTD tracks job changes across your network. When a new executive joins a target account, trigger a check: does anyone in your org know them from a previous role? New executives are high-value entry points — a warm connection to the incoming CRO or VP of Sales before they've settled in is a significant early-mover advantage.

Contract renewal approaching

90 days before a renewal, check the relationship health of your primary contacts at the account. If the relationship score has weakened — or if your main champion has left — surface that to the CSM and their manager so they can rebuild the relationship before it becomes a renewal risk.

How to implement

For Salesforce and HubSpot, most of these triggers can be built using native workflow automation (Salesforce Flow, HubSpot Workflows) with an HTTP action that calls the CTD API. For other CRMs or more complex logic, use the CTD API directly and route notifications through Slack or your existing alerting tooling. Contact our team for setup playbooks specific to your CRM and stack.