HR & RECRUITING

Weekly HRBP Comp-Drift Digest by Email

Each week, compares current pay to refreshed band midpoints in BigQuery and emails each HR business partner a tailored digest of only their client groups' below-midpoint…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionQuery below-midpoint employees by HRBPGoogle BigQueryBigQuery
  • LogicPartition list per HRBP and skip empties
  • ActionDraft per-partner adjustment notes
  • OutputSend tailored digest email to each HRBPGmailGmail

What it does

This workflow runs a weekly comp-drift check against BigQuery, finds employees below their band midpoint, and routes results by HR business partner. Each HRBP receives a single Gmail digest covering only their assigned client groups, listing flagged employees, the percent gap, and a drafted adjustment note they can paste into their tracker.

When to use it

Use it when comp ownership is split across HRBPs and a shared channel would create noise. A weekly email cadence keeps drift visible between formal review cycles without a manual pull, and the per-partner scoping respects who owns which population.

How it works

  1. 1A weekly schedule starts the digest run.
  2. 2A BigQuery query returns below-midpoint employees tagged with their HRBP.
  3. 3A routing step partitions the list by HRBP owner.
  4. 4A draft step composes each partner's adjustment notes and gap summary.
  5. 5A logic step skips any HRBP with zero flagged employees that week.
  6. 6A personalized digest email is sent to each HRBP via Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect GmailRead, draft, send, label.
  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.