HR & RECRUITING
Audit a merit-cycle raise batch against bands and log exceptions to Notion
When a merit-cycle raise file is uploaded, this workflow checks every proposed new salary against its level-and-geo band in BigQuery and writes each out-of-band raise to a Notion…
How it runs
The automated pipeline, trigger to output.
- TriggerMerit-cycle raise file uploadedGoogle Drive
- ActionLook up band per row from BigQueryBigQuery
- LogicTag raises that fall outside band
- ActionWrite each exception to Notion trackerNotion
- OutputPost run summary to NotionNotion
What it does
Merit cycles move hundreds of salaries at once, and bands are easy to blow past in bulk. This workflow takes an uploaded raise batch, looks up the approved band for each employee's level and geo in BigQuery, and evaluates every proposed new salary in one run. Raises that stay inside band pass silently; raises that push above the ceiling or sit below the floor become rows in a Notion exception tracker, each with the employee, manager, level, geo, current and proposed salary, the band range, and the dollar and percent variance. The result is a living review queue the comp team works through before the cycle is finalized, instead of discovering breaches after letters go out.
When to use it
Use it during planning or annual merit cycles when managers propose raises in a spreadsheet and comp needs a band check across the whole batch. It fits teams that run structured cycles and want every exception captured in one Notion board for review and sign-off.
How it works
- 1A trigger fires when the merit-cycle raise file lands in the watched cloud folder.
- 2The workflow reads the batch and, for each row, queries BigQuery for the approved band by level and geo.
- 3A logic step computes each proposed salary's position relative to its band and tags the out-of-band ones.
- 4Each exception is written as a row to the Notion comp-review tracker with variance and reason.
- 5A summary count of rows reviewed and exceptions logged closes the run in Notion.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect NotionPages, databases, comments.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More HR & Recruiting workflows
Day-one readiness orchestrator across all onboarding owners
An agent-driven coordinator that, when a hire is launched, plans the full provisioning program across IT, Facilities, and Finance, opens the work in your tracker.
Escalate Compliance-Blocking Credential Lapses to Managers
Each day it finds credentials that have already expired or expire within 48 hours and are flagged compliance-blocking.
Assemble and send the debrief packet after the final interview
Triggered when a candidate's final interview ends on the calendar, it waits a short window for scorecards, compiles the aggregated packet to Google Drive.
Credential Renewal Evidence Verification Agent
When an employee replies with a renewed credential document, an agent reads the attachment, extracts the new expiry date and credential number.
New-Hire Credential Intake to Renewal Calendar Holds
When a new credential is added to the tracker, it validates the record, files the document.
New-hire equipment order email to IT and vendor
On a scheduled lead-time before each start date, drafts and sends an equipment order email (laptop, monitor.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
