CRM

Dormant-Stage Re-Engagement Task Builder (Postgres to Asana)

Identifies CRM contacts whose lifecycle stage implies active engagement but whose Postgres-recorded last touch has gone dormant.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule triggers the dormancy sweep
  • ActionQuery Postgres for active-stage contacts, last-touch date, ownerPostgreSQLPostgres
  • LogicKeep contacts past dormancy window; dedupe against open tasks
  • ActionCreate owner-assigned re-engagement task per contact in AsanaAsanaAsana
  • OutputPost Slack summary of tasks createdSlack

What it does

Detection is useless without follow-through. This workflow reads contacts and their lifecycle stages from your CRM mirror in Postgres, finds those whose stage promises momentum (Engaged, Opportunity, In Trial) but whose last touch has gone cold past the dormancy window, and turns each into an actionable Asana task assigned to the owning rep with the contact, stage, and days-dormant baked in.

When to use it

Use it when stale-stage detection already exists but nothing gets done about it, when reps need work routed to them rather than a report to read, or when you want re-engagement to become a tracked, closable task instead of a forgotten alert.

How it works

  1. 1A schedule triggers the dormancy sweep.
  2. 2An action queries Postgres for contacts whose stage implies active engagement plus their last-touch date and owner.
  3. 3A logic step keeps only contacts past the dormancy window for their stage and dedupes against tasks already open.
  4. 4An action creates one Asana task per dormant contact, assigned to the owner with stage and days-dormant in the description.
  5. 5An output step posts a Slack summary of how many re-engagement tasks were created and for whom.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect AsanaTasks, projects, milestones — everywhere.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.