HR & RECRUITING

Gate every new offer against its approved comp band before it goes out

When a recruiter submits a proposed offer, this workflow looks up the approved salary band for that level and geo in BigQuery and either auto-clears it or routes an exception…

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerRecruiter submits a proposed offerHTTP webhook
  • ActionLook up approved band for level + geoGoogle BigQueryBigQuery
  • LogicClassify: in-band, below floor, above ceiling
  • LogicAuto-approve in-band; branch exceptions
  • OutputPost band breach to comp team in SlackSlack

What it does

This workflow puts a real-time guardrail in front of every offer. The moment a proposed offer is submitted, it pulls the approved compensation band for that job level and work location from your BigQuery comp-band table, compares the proposed base (and optionally bonus and equity) against the floor and ceiling, and decides in one pass: inside band, below floor, or above ceiling. Clean offers are stamped approved automatically. Any offer that lands outside the band is held and pushed to the compensation team's Slack channel with the candidate, level, geo, the band range, and the exact dollar variance so an approver can act without digging.

When to use it

Use it when offers get sent before anyone checks the band, and comp drift only surfaces at year-end. It fits HR and comp teams that maintain banded pay by level and geography and want a hard checkpoint between "recruiter proposes" and "offer sent" without slowing down in-band offers.

How it works

  1. 1A webhook trigger fires when a recruiter submits a proposed offer (level, geo, base, bonus, equity).
  2. 2The workflow queries BigQuery for the approved band matching that level and geo.
  3. 3A logic step compares the proposal to the band and classifies it as in-band, below floor, or above ceiling.
  4. 4In-band offers are recorded as auto-approved; out-of-band offers branch to an exception path.
  5. 5The exception is posted to the comp team's Slack channel with the breach amount and band range for a sign-off decision.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  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.