HR & RECRUITING

Scheduled compensation-band drift audit to Notion

Runs nightly to compare every active employee's pay against their role's current salary band in BigQuery.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires the audit
  • ActionQuery BigQuery for employees joined to current bandsGoogle BigQueryBigQuery
  • LogicCompute band position; keep only out-of-band rows
  • ActionBuild a drift card per flagged employee
  • OutputUpsert cards onto the Notion comp-review boardNotionNotion

What it does

Each night this workflow pulls current compensation for all active employees and the canonical salary bands for their role, level, and location from BigQuery. It computes where each person sits relative to their band's min and max, and surfaces anyone who has drifted below the floor or above the ceiling. Every flagged case becomes a structured card on a Notion comp-review database, with the exact dollar gap, the percent-of-band position, and whether the drift is high or low.

When to use it

Use this when comp data lives in a warehouse and you want a standing, no-touch audit instead of running ad-hoc spreadsheet checks before each review cycle. It keeps a living queue of out-of-band employees ready for HR to triage.

How it works

  1. 1A nightly schedule fires the audit.
  2. 2Query BigQuery for active employees joined to their role's current band (min, mid, max).
  3. 3Compute band position; filter to only rows below min or above max.
  4. 4For each flagged employee, build a card with the gap and direction.
  5. 5Upsert the card into the Notion comp-review board, updating any existing card for that employee.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect NotionPages, databases, comments.
  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.