CRM

Merge Queue Health Digest

Each morning reports on the duplicate merge queue — backlog size, oldest pending pair, approvals and rejections in the last day, and auto-resolution rate.

CategoryCRM
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMorning schedule triggers run
  • ActionQuery merge queue state and transitionsPostgreSQLPostgres
  • LogicCompute metrics and check threshold
  • OutputEmail digest to data teamGmailGmail
  • OutputSlack alert if backlog over thresholdSlack

What it does

Gives operators a daily pulse on the reconciliation pipeline. It reads the Postgres merge queue, computes backlog and throughput metrics (pending count, oldest pending age, last-24h approved versus rejected, share auto-resolved by enrichment), formats a digest, and emails it to the data team. If the pending backlog crosses a set threshold, it also fires a Slack alert so the queue never silently piles up.

When to use it

You are running the dedupe and executor workflows and need visibility into whether reviewers are keeping pace and whether auto-resolution is working — without opening the database yourself.

How it works

  1. 1A morning schedule triggers the run.
  2. 2Query the Postgres merge queue for current state and last-24h transitions.
  3. 3A logic step computes the metrics and checks the backlog threshold.
  4. 4Email the formatted digest to the data team via Gmail.
  5. 5If the backlog exceeds the threshold, send a Slack alert tagging the queue owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect GmailRead, draft, send, label.
  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.