SALES
Champion Departure Detector via Job-Title Monitoring
Watches your key Salesforce contacts' public LinkedIn profiles for a job change, and when a champion leaves their company it opens a relationship-rebuild task and alerts…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionFetch champion contacts from SalesforceSalesforce
- ActionScrape public LinkedIn profilesApify
- LogicCompare employer; flag mismatches as departed
- ActionUpdate contact + create rebuild task in SalesforceSalesforce
- OutputAlert account owner in SlackSlack
What it does
It scrapes the public LinkedIn profiles of your most important Salesforce contacts on a schedule, detects when a contact's current employer or title no longer matches what's on the account, and flags that person as a likely departure. Each confirmed departure becomes a tracked rebuild play assigned to the account owner.
When to use it
Use it when your renewals and expansion depend on a single internal champion per account. People change jobs quietly, and you usually find out only when a deal stalls. This catches the move within a scrape cycle so you can re-anchor the relationship before the account goes cold.
How it works
- 1A weekly schedule fires the run.
- 2Pull all contacts tagged as champions from Salesforce, with their stored company and title.
- 3Apify scrapes each contact's public LinkedIn profile for current employer and title.
- 4A logic step compares scraped employer against the Salesforce account; if it differs, mark as departed.
- 5For departures, update the Salesforce contact status to Left Company and create a follow-up task.
- 6Post a Slack alert to the account owner naming the contact, old account, and new employer.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect ApifyActors, scrapers, datasets.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.