Auto-fill salary bands for new hiring requisitions

Build a code workflow that auto-fills a suggested salary band on every new role added to our hiring tracker in Airtable, so we never ship a posting without one (pay transparency laws in CA, NY, CO, WA, IL and similar require it).

Trigger: Airtable poll trigger, event type 'new_record', watching our Open Reqs table. The poll payload gives me the new record's fields, including Job Title and Location.

Step 1. Read Job Title and Location off the new record from the trigger payload. If either is missing or blank, skip the rest of the workflow gracefully.

Step 2. Call Job Salary Data 'Get Job Salary Estimate' with that Job Title and Location. The response is an envelope with a data[] array of up to three publisher estimates; take the first entry (typically Glassdoor) and pull out min_salary, median_salary, max_salary, salary_currency, salary_period, publisher_name, and confidence.

Step 3. Format a single string for the Suggested Salary Band field that looks like: "$120,000 min / $145,000 median / $170,000 max, source: Glassdoor, confidence: CONFIDENT". Use thousands separators and the currency from the response. Also keep the raw confidence value to write into a separate Benchmark Confidence field.

Step 4. Call Airtable 'Update Record' (PATCH) on the same record id, in the same base and table the trigger fired from, setting Suggested Salary Band to the formatted string and Benchmark Confidence to the raw confidence value.

Step 5. Call Slack Bot 'Send a Message' to a hiring channel (treat the channel as a configurable input, defaulting to #recruiting) with a short note like: "Fresh salary band ready for review on <Job Title> (<Location>): $120k / $145k / $170k, confidence CONFIDENT. Check the Open Reqs row in Airtable." Use Slack mrkdwn formatting.

This is a deterministic pipeline with no judgement calls, so a code workflow is the right shape. Surface base id, table id, the field names (Job Title, Location, Suggested Salary Band, Benchmark Confidence), and the Slack channel as configuration so a different team can repoint it without editing code.