CRM
Flag Departed Contacts and Trigger Replacement Mapping
Detects when an email bounces or an out-of-office reply names a successor, marks the contact as departed in Attio.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email received (bounce or auto-reply)Gmail
- ActionClassify message and extract successorOpenAI
- LogicDrop if not a departure signal
- ActionMark contact as departed in AttioAttio
- ActionCreate successor contact stubAttio
- OutputOpen remap task in LinearLinear
What it does
When a key contact leaves a target account, deals stall because nobody noticed. This template watches for the two earliest signals of a departure: a hard bounce and an auto-reply that names a successor. It flags the contact as departed, captures any named replacement, and kicks off the work to remap the buying committee.
When to use it
Use this on accounts where a single champion carries the relationship. The moment that person leaves, you want their record updated and a replacement-mapping task in your owner's queue, not a surprise three weeks later.
How it works
- 1A new email arrives in Gmail and fires the trigger (a bounce notice or auto-reply).
- 2An OpenAI step classifies the message as a hard bounce, a departure auto-reply, or neither, and extracts any successor name and email.
- 3A logic branch drops messages that are not departure signals.
- 4The contact is marked "Departed" in Attio with the detected reason.
- 5If a successor was named, a new contact stub is created in Attio and linked to the same account.
- 6A Linear issue is opened to remap the buying committee for that account.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AttioReal-time CRM with structured data + powerful views.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Spin up a Monday handoff board for a departing rep's deals
When a rep is deactivated in Salesforce, this creates a Monday.com board with one item per open opportunity so the manager can manually triage and assign each handoff.
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Reassign a departed rep's open pipeline by territory
When a Salesforce user is deactivated, this finds all of their open opportunities and reassigns each one to the active rep who owns its territory, then logs the moves.
Escalate opportunities still owned by an inactive rep after grace period
Checks daily for open opportunities that have stayed with an inactive owner past a grace window and escalates each to the regional director by email and Slack with deal context.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
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.