CRM

Reactivation Reply Detection and Owner Handoff

Detects when a dormant account replies to a win-back email, logs the response back to HubSpot, marks the Coda queue row as re-engaged, and pings the owner.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew inbound email arrives in outreach mailboxGmailGmail
  • LogicMatch sender to an account in the reactivation queue
  • ActionLog reply as engagement on HubSpot companyHubSpotHubSpot
  • ActionMark Coda row "Re-engaged" to stop the sequenceCodaCoda
  • OutputAlert account owner in Slack with thread linkSlack

What it does

This workflow closes the loop on reactivation outreach. It watches the shared outreach mailbox for replies from accounts in an active win-back sequence, identifies which queued account responded, logs the reply as an engagement on the HubSpot company, marks the Coda row as "Re-engaged," and notifies the account owner so they can jump on a warm conversation immediately.

When to use it

Use this whenever you run staged win-back emails and need replies to pull accounts out of the automated sequence the moment a human responds — preventing a re-engaged prospect from getting another robotic follow-up.

How it works

A Gmail trigger fires on new inbound messages. A logic step matches the sender against accounts currently in the reactivation queue and ignores everything else. For matches, the workflow logs the reply text as a HubSpot engagement, updates the Coda row status to "Re-engaged" so the sequence stops, and sends the owner a Slack alert with the account and a link to the thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Connect CodaDocs, packs, automations.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.