HR & RECRUITING

New-Hire Offer Below-Midpoint Guardrail Alert

When a new offer record posts via webhook, checks the proposed salary against the live band midpoint in BigQuery and, if it lands below, drafts a justification prompt and alerts…

CategoryHR & Recruiting
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOffer-created webhookHTTP webhook
  • ActionLook up current band midpointGoogle BigQueryBigQuery
  • LogicCompare proposed salary to midpoint
  • ActionDraft justification prompt if below
  • OutputAlert recruiting lead in SlackSlack

What it does

This workflow intercepts new offer records as they are created and compares the proposed base salary to the current band midpoint for that role and level, pulled from BigQuery. If the offer would start the hire below midpoint, it drafts a short justification request and alerts the recruiting lead in Slack so the gap is acknowledged before the offer is sent.

When to use it

Use it to prevent new pay drift at the source. While the other sweeps catch existing employees, this one stops below-midpoint hires from being created unexamined, which is where future equity problems often begin. Ideal when your ATS or offer tool can post a webhook on offer creation.

How it works

  1. 1An offer-created webhook triggers the check.
  2. 2A BigQuery lookup fetches the current midpoint for the role and level.
  3. 3A logic step compares the proposed salary to midpoint.
  4. 4If at or above midpoint, the run ends silently.
  5. 5If below, a justification prompt is drafted for the hiring team.
  6. 6A Slack alert with the gap and prompt is sent to the recruiting lead.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  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.