CRM

Reactivation Cohort Export to BigQuery for Analysis

Snapshots the weekly dormant-account reactivation cohort from Salesforce with recency scores into BigQuery.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionQuery dormant cohort with scores from SalesforceSalesforce
  • LogicNormalize rows, stamp snapshot date and run ID
  • ActionAppend snapshot to BigQuery history tableGoogle BigQueryBigQuery
  • OutputConfirm snapshot to analytics Slack channelSlack

What it does

This workflow makes reactivation measurable. Every week it captures the dormant cohort and its recency scores from Salesforce, then appends a timestamped snapshot to a BigQuery table. Over time that table becomes a history of who was dormant, how cold, and whether they came back — the dataset you need to prove (or disprove) that win-back motions work.

When to use it

Use it when leadership asks 'does our reactivation program actually recover revenue?' and you have no longitudinal data to answer. It builds the analytics backbone without manual CSV exports, and feeds dashboards or cohort-retention queries.

How it works

  1. 1A weekly schedule starts the snapshot.
  2. 2Query Salesforce for the current dormant cohort with last-activity dates, owner, value, and reactivation score.
  3. 3A transform step normalizes the rows and stamps a snapshot date and run ID.
  4. 4Append the snapshot to the BigQuery reactivation-history table.
  5. 5Post a confirmation with row count and snapshot date to the analytics Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  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.