CRM

Dormant Account Silence-Window Detector

Scans HubSpot for accounts with no logged activity past a configurable threshold and stages them as reactivation candidates in a Coda outreach tracker.

CategoryCRM
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionFetch companies + last-activity dates from HubSpotHubSpotHubSpot
  • LogicCompute days-since-contact, keep accounts past threshold
  • LogicSkip accounts already in the queue
  • OutputAppend dormant accounts to Coda Reactivation QueueCodaCoda

What it does

Every morning this workflow sweeps your HubSpot companies, calculates how many days have passed since the last logged engagement (email, meeting, note, or call), and flags any account that has crossed your silence threshold. Each newly dormant account is written to a Coda "Reactivation Queue" table with its silence duration, owner, and last-touch context so an operator can pick up from a clean staging list instead of hunting through the CRM.

When to use it

Run this when your book of business is large enough that accounts go quiet without anyone noticing, and you want a deterministic, daily-refreshed list of who has gone cold rather than relying on memory or ad-hoc reports.

How it works

A daily schedule triggers the run. The workflow pulls all companies and their last-activity timestamp from HubSpot, then a logic step computes days-since-contact and keeps only accounts past the threshold (e.g. 45 days). A dedupe check skips anything already sitting in the queue, and the survivors are appended as rows to the Coda Reactivation Queue with owner and silence-window metadata.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.