Daily pre-shift weather go/no-go text for field crews

Build me a code-based workflow that runs on a cron schedule every weekday at 5am in my local time. The job is to send each field crew lead one SMS that calls go/no-go on every job they have scheduled that day, based on the local weather forecast at each job site.

Inputs. Use Airtable List Records to read my jobs table, filtered to records where the job date equals today. Each row has these columns: job ID, date, crew lead phone number in E.164 format, latitude, longitude, start time, end time, and job type. Job types include roofing, paving and concrete, painting, landscaping, tree work, solar install, exterior cleaning, and line work.

Forecast lookup per job. Call NOAA Weather Get Point Metadata with the job's latitude and longitude to get the forecast grid identifiers, then call NOAA Weather Get Hourly Forecast on that grid point. Filter the hourly forecast to only the hours that fall inside the job's start time through end time window. Do not evaluate the whole day.

Go/no-go logic. This must be deterministic with no model reasoning. Apply a fixed threshold table keyed on job type. Use this starter table as the default and treat it as configuration the operator can edit later.

• Roofing. No-Go if sustained wind exceeds 25 mph at any point in the window, or any precipitation is forecast. Caution if sustained winds are 20 to 25 mph. Otherwise Go.

• Paving and concrete. No-Go if air temperature drops below 50F at any point in the window, or any precipitation is forecast in the 4 hours after start. Caution if temperature is 50 to 55F. Otherwise Go.

• Painting. No-Go if any precipitation is forecast, relative humidity stays above 85 percent across the window, or temperature is below 50F. Caution if humidity is 75 to 85 percent. Otherwise Go.

• Landscaping. No-Go if thunderstorms are forecast or precipitation exceeds light rain. Caution if any precipitation is forecast. Otherwise Go.

• Tree work. No-Go if wind gusts exceed 30 mph or thunderstorms are forecast. Caution if gusts are 25 to 30 mph. Otherwise Go.

• Solar install. No-Go if precipitation is forecast or wind gusts exceed 25 mph. Caution if gusts are 20 to 25 mph. Otherwise Go.

• Exterior cleaning. No-Go if temperature is below 40F, wind gusts exceed 25 mph, or precipitation is forecast. Otherwise Go.

• Line work. No-Go if thunderstorms are forecast or wind gusts exceed 35 mph. Caution if gusts are 30 to 35 mph, or temperature is below 20F. Otherwise Go.

For each job, capture the single most important driving condition behind the verdict so it can appear in the message. Examples: "winds gusting to 32 mph at 10am" or "rain expected 1pm to 3pm".

Grouping and messaging. Group jobs by crew lead phone number. For each crew lead, build one short SMS that lists each of their jobs in order of start time. Each line should include the job ID, the verdict (Go, Caution, or No-Go), and the driving condition in plain English. Keep the whole message under roughly 320 characters so it fits in two SMS segments when possible. Send one message per crew lead using Twilio Send a Message. Use SMS, not WhatsApp.

Edge cases. If a crew lead has no jobs today, do not send them a message. If a job's location falls outside the United States, skip the forecast lookup for that job and include a single line in that crew lead's message noting it was skipped so they can call in manually.

The threshold table is operator-owned configuration. Do not have the model reinterpret thresholds each run. The workflow should be reproducible: same forecast in, same verdicts out.