Skip to content

Weather Reschedule Notifier · Field Services

Make tomorrow's weather calls by afternoon, not at 6am

Each afternoon it checks the National Weather Service forecast for your service areas against your limits per job type and drafts reschedule notes for affected customers. Your dispatcher approves.

Available now $119 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Runs on a schedule
  • 2 AI steps
  • A person approves before it acts
  • About 30 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Every afternoon I'm checking the weather app for each crew's area.”
  • “Customers take a day off work and we cancel at 7am.”
  • “Crews hear the rain call from three different people.”

What you get with the agent

  • Tomorrow's NWS forecast for up to 10 service areas, judged against your own limits for rain, wind, heat, freeze and thunderstorms.
  • The forecast value shown behind every impact, and an all-clear in Slack when nothing is affected.
  • Short notes offering your next open day to each affected customer, up to 40 a run.
  • Nothing is emailed until the dispatcher approves the batch, editing notes or removing jobs they'll keep.
  • A crew notice in Slack with impacts, affected jobs and calls to make.

Before

4pm: five weather tabs, a list of mowing and painting jobs, and an evening of calling customers.

After

4pm: Slack shows rain over your limit in the north area. Eight notes offering Thursday are drafted; you drop one job you'll keep and approve the rest.

How it works

The whole workflow, step by step.

Every afternoon the agent reads your service areas from Google Sheets and gets tomorrow's National Weather Service forecast for each (free, no key, US only). AI applies only your limits per job type — rain for mowing and painting, wind for roofing, heat for crews, freeze for pressure washing — and shows the forecast value behind every impact. When nothing is affected, an “all clear” goes to Slack. Otherwise it reads tomorrow's jobs and drafts a short note to each affected customer offering your next open day (up to 40 per run). The dispatcher approves the batch, editing notes or removing jobs they'll keep; the notes are emailed with replies to your office inbox and a crew notice goes to Slack. It doesn't move jobs in Jobber or Housecall Pro, and it works from a forecast, so the dispatcher makes the call.

  1. TriggerEvery day at 16:00
  2. App callRead your jobs
  3. LogicKeep tomorrow's jobs
  4. App callRead your service areas
  5. LogicEach service area
  6. App callFind the forecast office
  7. App callGet the forecast
  8. AI stepCheck tomorrow against your limits
  9. LogicAny weather impact tomorrow?
    • All clear:Post the all clear
    • Impact:Draft the reschedule notes
  10. App callPost the all clear
  11. OutputAll clear
  12. AI stepDraft the reschedule notes
  13. Human approvalApprove the reschedule batch
    • Approved:Each approved note
    • Rejected:Batch rejected
  14. OutputBatch rejected
  15. LogicEach approved note
  16. OutputEmail the customer
  17. App callPost the crew notice
  18. OutputDone

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1Every day at 16:00Runs every afternoon to check tomorrow's weather. Set your time zone on the trigger.
  2. Step 2Read your jobsReads your jobs tab (date, customer, email, job type, service area, address, crew). Keep upcoming jobs there; past ones can move to another tab.
  3. Step 3Keep tomorrow's jobsIn code, not AI: works out tomorrow's date in your time zone and keeps only the jobs dated tomorrow, so the AI never decides which day a job is on. Change the window here (within.min / within.max).
  4. Step 4Read your service areasReads your service-areas tab: one row per area with its name and a forecast point (Lat, Lon).
  5. Step 5Each service areaGets the forecast for every service area (up to 10).
  6. Step 6Find the forecast officeAsks the National Weather Service which forecast grid covers this service area (from its latitude and longitude).
  7. Step 7Get the forecastReads the National Weather Service 12-hour forecast periods for this service area (temperature, chance of rain, wind and the forecast text).
  8. Step 8Check tomorrow against your limitsAI reads tomorrow's daytime forecast for each area (tomorrow's date comes from code) and applies your limits per job type (rain, wind, heat, freeze), with the forecast value behind every call.
  9. Step 9Any weather impact tomorrow?No impact anywhere: a short “all clear” goes to Slack and the run ends. Otherwise reschedule notes are drafted for tomorrow's jobs.
  10. Step 10Post the all clearPosts “tomorrow looks workable” with a one-line forecast per area to your dispatch channel.
  11. Step 11All clearNo jobs affected; the run history keeps the forecast check.
  12. Step 12Draft the reschedule notesFrom tomorrow's jobs (picked in code), AI picks the ones in affected areas whose job type is hit by the weather, and drafts a short note to each customer offering your next open day, plus the crew notice.
  13. Step 13Approve the reschedule batchThe dispatcher reads tomorrow's affected jobs and every drafted note in Reviews, edits them, removes any job they'll keep, and approves; nothing is sent before that.
  14. Step 14Batch rejectedNothing was sent; the run history keeps the forecast check and the drafts.
  15. Step 15Each approved noteEmails every approved reschedule note (up to 40).
  16. Step 16Email the customerSends the approved note to the customer from your workspace's sender, with replies going to your office inbox.
  17. Step 17Post the crew noticePosts tomorrow's weather impacts, the affected jobs and the calls you still need to make to your crew channel, with how many notes went out.
  18. Step 18DoneThe run history keeps the forecast check, the approved notes and the crew notice.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional run: north area forecast shows a 70 percent chance of rain tomorrow; your limit for mowing is 50 percent.

The agent produces

Impact flagged with the forecast value, notes drafted to that area's mowing customers offering your next open day, and a crew notice listing the moves, all waiting for one approval.

What you need

Everything it takes to run it.

About 30 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $119 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations, plus an HTTP / Custom API connection to https://api.weather.gov (free, no key).
  • A service-areas tab (Area, Lat, Lon) and a jobs tab with customer emails.
  • Your written weather limits per job type and your rebooking message.

Setup, about 30 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your service-areas and jobs sheets (Settings → Integrations → Google Sheets).
  3. Connect the National Weather Service (HTTP / Custom API). In Settings → Integrations, add an HTTP / Custom API connection named “National Weather Service” with base URL https://api.weather.gov and Authentication “None”. The NWS API is free, public domain and needs no key; it covers US locations only.
  4. Connect Slack. Connect the Slack workspace your dispatch team and crews use (Settings → Integrations → Slack).
  5. Pick your service areas. Open “Read your service areas” and pick your account, spreadsheet and the tab with Area, Lat and Lon.
  6. Set up the weather lookups. Open “Find the forecast office” and “Get the forecast”: pick the National Weather Service connection in both, and in Extra headers replace the placeholder with your business name and a contact email.
  7. Paste your weather limits. Open “Check tomorrow against your limits” and replace the placeholder with your limits per job type.
  8. Pick the dispatch channel. Open “Post the all clear” and pick your account and channel.
  9. Pick your jobs sheet. Open “Read your jobs” and pick your account, spreadsheet and jobs tab (with a Date column).
  10. Write your rebooking message. Open “Draft the reschedule notes” and replace the placeholder with your open days, what customers should know and your sign-off.
  11. Add your office inbox and crew channel. Open “Email the customer” and enter the Reply-to address, then “Post the crew notice” and pick your account and channel.
  12. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  13. Switch the trigger on. Open the trigger, set your time zone and switch the schedule on. It runs every day at 16:00.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Lawn care and landscaping companies
  • Painters, roofers and pressure washers
  • Dispatchers scheduling outdoor work

What it doesn't do

  • It doesn't move jobs in Jobber, Housecall Pro or your calendar: you update the schedule.
  • It works from a National Weather Service area forecast (US only), not on-site conditions, so the dispatcher makes the call. One forecast point per service area.
  • It applies only the limits you write and never promises the weather, dates or discounts.
  • Nothing is emailed before the batch is approved. Affected jobs without an email are listed for you to call.

We list the limits up front so you can decide before you buy.

Price

$119 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Weather Reschedule Notifier.

Does it move jobs in my scheduling software?

No. It drafts customer notes and tells the crew; you move the jobs in your scheduling tool or calendar. Affected jobs with no email are listed for you to call.

What if the forecast is wrong?

It works from an NWS area forecast (US only), not on-site conditions, so the dispatcher makes the call. It applies only your limits and never promises weather, dates or discounts.

How long is setup?

About 30 minutes: connect Google Sheets and Slack, add the free NWS connection, list your service areas with coordinates, paste your limits and rebooking message, then Dry Run.

What does it cost?

The weather data is free. The agent is a one-time unlock that never renews; live runs need a paid plan and your own AI key.

Where does the weather come from?

The US National Weather Service API (https://api.weather.gov): free, public domain and no key, through an HTTP / Custom API connection. Two calls per location: one finds the forecast grid for the latitude and longitude, the second reads the 12-hour forecast. US locations only. NWS asks every app to name itself and a contact in the User-Agent header, which is why you add yours in setup. Its forecasts are general area forecasts, not on-site measurements.

What should the sheets look like?

A service-areas tab with a header row and the columns Area, Lat and Lon exactly (the forecast point for each area, up to 4 decimals, e.g. 39.7456 and -97.0892), up to 10 areas. A jobs tab with Date, Customer, Email, Job type, Area and Address (plus Crew if you like); keep upcoming jobs there.

Does it move the jobs?

No. It drafts the customer notes and tells the crew; you move the jobs in Jobber, Housecall Pro or your calendar. It works from a forecast, so the dispatcher makes the call.

Can I use a forecast point per job?

This version uses one point per service area (one weather lookup each), which keeps it fast and inside the free API's fair use. Keep areas small enough that one forecast fits them.

How does it know which jobs are tomorrow?

In code, not by the AI: “Keep tomorrow's jobs” works out tomorrow's date in your trigger's time zone and keeps only job rows dated that day (dates like 2026-10-14, 10/14/2026 or October 14, 2026 all work). The AI only judges the weather against your limits and writes the notes.

Is this a subscription?

No. Weather Reschedule Notifier is a one-time purchase of $119 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Weather Reschedule Notifier to work.

Free account, no credit card. Your Agents page opens with Weather Reschedule Notifier ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works