CRM
Departed-Contact Deal Failover
When a webhook reports a key contact has left their company, finds every open deal that depended solely on that person and pages the owning reps with a backfill plan…
How it runs
The automated pipeline, trigger to output.
- TriggerContact-departure webhook receivedHTTP webhook
- ActionFind open deals dependent only on that contactSalesforce
- LogicStop if no single-threaded deals affected
- ActionDraft backfill stakeholder planOpenAI
- ActionLog follow-up task on each opportunitySalesforce
- OutputPage owning reps in SlackSlack
What it does
The worst single-thread failure is sudden: your one contact changes jobs and the deal has no fallback. This workflow reacts to a contact-departure signal, identifies which open deals were riding on that person alone, and triggers immediate recovery so the deal doesn't silently die.
When to use it
Use it when you feed contact-change signals (from a data enrichment provider, HRIS webhook, or email-bounce detector) into Hive and need same-day failover on affected deals. Highest value for teams with long sales cycles where a lost champion is expensive.
How it works
- 1An incoming webhook delivers a departed-contact event with the contact's identifier.
- 2The workflow looks up that contact in Salesforce and finds every open opportunity where they are the sole engaged contact.
- 3A logic step exits quietly if no single-threaded deals are affected.
- 4For each affected deal, an OpenAI step drafts a backfill plan naming likely alternate stakeholders to approach.
- 5The workflow logs a follow-up task on each opportunity in Salesforce.
- 6It pages the owning reps in Slack with the deal, the lost contact, and the backfill plan.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.