Triggers
SalesforceRecord events that should kick off a CTD lookup.
Pick a trigger, pull CTD data, surface it to the seller. Add a follow-up action when you are ready.
Every integration follows this vertical flow. Mix components below to design new plays.
Salesforce record event: Contact, Lead, Opportunity, or Account changes that signal “act now.”
Contact · Lead · Opp · AccountEnterprise API: paths, reachable people, company scores, job changes, connector routes.
Paths · People · Companies · Job changesEmail owner, Slack, Teams, or Task with the insight.
Email · Slack · TeamsWrite scores, path counts, and flags to Contact or Account.
SF fields · FLSAE follows through on the insight: ghost email, call, text, reminder, or other next step.
Ghost email · Call · Text · ReminderRecommended options for Drips. Start with one item from each column; expand as plays mature.
Record events that should kick off a CTD lookup.
/enterprise/atc-paths-api/... — one shared org key.
Persist CTD enrichment on Salesforce records (often before or alongside 3a).
How the AE (or manager) sees the insight outside the record.
After step 3a, the AE acts on the insight. Pick what fits the play.
Documented plays with full diagrams and deployment guides.
When a Contact is created or LinkedIn URL is updated: fetch global paths and reachable-person data, write six CTD fields on the record, email the account owner with the best path, Claude draft links, and ghost-email share via CTD API from Claude.
Stage change → reachable executives → Slack + Tasks.
Scheduled scan → email owner and manager.
Owner change → paths + company score email.