Skip to content

Tour Weather Go/No-Go · Hospitality & Events

Make tomorrow's weather call the night before, the same way

AI checks the forecast at each meeting point against your limits and recommends go, marginal or cancel. Your lead guide approves every call before guests hear a thing.

Available now $149 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
  • 3 AI steps
  • A person approves before it acts
  • About 35 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Every evening I'm refreshing forecasts and texting guides about tomorrow.”
  • “Guests show up in sandals for a rainy hike because nobody told them what to bring.”
  • “Cancellations go out late and inconsistent, and the refund questions pile up.”

What you get with the agent

  • Every evening, reads tomorrow's departures and gets the National Weather Service forecast at each meeting point.
  • Applies your written limits per activity (wind, thunderstorms, heat, rain) and recommends go, marginal or cancel with the forecast values behind it.
  • Drafts a what-to-wear-and-bring email and a cancellation email with your rebook and refund policy copied exactly.
  • The lead guide reviews and edits every call; guests on go or cancelled departures then get the approved email by first name.
  • Guides get a Slack briefing with tomorrow's calls and reasons.

Before

At 9 p.m. you're comparing three weather apps, deciding on the sunrise kayak by gut, and emailing guests one at a time.

After

At 6 p.m. your lead guide opens one review: kayaks marked marginal for 18 mph gusts, the hike a go with a rain-layer note. They decide, and every guest hears that evening.

How it works

The whole workflow, step by step.

Every evening the agent reads tomorrow's departures from Google Sheets and gets the National Weather Service forecast at each meeting point (US only). AI applies your limits per activity — wind for kayaks and boats, thunderstorms for hikes, heat, rain — and recommends go, marginal or cancel with the forecast values behind it, drafting a “what to wear and bring for this forecast” email and a cancellation email with your own rebook and refund policy text. The lead guide reviews every call and edits anything before guests hear. Each booking on a go or cancelled departure then gets the approved email, greeted by first name, and your guides get a Slack briefing. It isn't a marine, aviation or lightning-detection service, the guide's call on the day overrides it, and refunds stay in your booking system.

  1. TriggerEvery evening at 17:00
  2. App callRead tomorrow's departures
  3. LogicKeep tomorrow's departures
  4. LogicEach departure tomorrow
  5. App callFind the forecast office
  6. App callGet the forecast
  7. AI stepMake the go / no-go call
  8. Human approvalLead guide reviews every call
    • Approved:Write the guides' briefing
    • Rejected:Calls rejected
  9. OutputCalls rejected
  10. AI stepWrite the guides' briefing
  11. App callRead the bookings
  12. LogicKeep tomorrow's bookings
  13. LogicEach booking tomorrow
  14. AI stepMatch the booking to its call
  15. LogicCheck before sending
  16. LogicEmail this guest?
    • Send:Email the guest
    • Skip:Not emailed
  17. OutputEmail the guest
  18. OutputNot emailed
  19. LogicCount the guest emails
  20. App callBrief the guides in Slack
  21. OutputDone

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

  1. Step 1Every evening at 17:00Runs the evening before each tour day. Set your time zone on the trigger.
  2. Step 2Read tomorrow's departuresReads your departures tab: date, time, tour, activity type, meeting point with Lat and Lon, and the guide.
  3. Step 3Keep tomorrow's departuresIn code, not AI: works out tomorrow's date in your time zone and keeps only the departures dated tomorrow, so the AI never decides which day a tour runs. Change the window here (within.min / within.max).
  4. Step 4Each departure tomorrowGets the forecast and makes the call for every departure the date check kept (up to 20).
  5. Step 5Find the forecast officeAsks the National Weather Service which forecast grid covers the meeting point (from its latitude and longitude).
  6. Step 6Get the forecastReads the National Weather Service 12-hour forecast periods for the meeting point (temperature, chance of rain, wind and the forecast text).
  7. Step 7Make the go / no-go callAI applies your limits for this activity (wind for kayaks and boats, thunderstorms for hikes, heat) to the forecast at the meeting point and recommends go, marginal or cancel with reasons, plus both guest emails for the guide to review. The departure date was checked in code.
  8. Step 8Lead guide reviews every callAll of tomorrow's calls wait in Reviews together. The lead guide checks each forecast and reason, changes any call to go or cancel, edits the guest emails and approves; guests hear nothing before that.
  9. Step 9Calls rejectedNo guest emails were sent; the run history keeps the calls.
  10. Step 10Write the guides' briefingAI turns the approved calls into a short Slack briefing for your guides (each departure's call, the reasons and the forecast) and lists the approved guest emails to send.
  11. Step 11Read the bookingsReads your bookings tab (date, time, tour, guest name, email, party size, status). Keep upcoming bookings there.
  12. Step 12Keep tomorrow's bookingsIn code, not AI: keeps only the booking rows dated tomorrow (in your time zone), so guests booked on other days are never matched or emailed.
  13. Step 13Each booking tomorrowMatches every booking for tomorrow to its approved call, checks the email and sends it (up to 100).
  14. Step 14Match the booking to its callAI matches the booking (dated tomorrow, checked in code) to its departure and picks the approved go or cancel email, greeting the guest by first name. Open calls and cancelled bookings get nothing.
  15. Step 15Check before sendingIn code: matched to an approved call, exactly one valid guest email, and a subject and body with no placeholders left. Anything that fails isn't emailed and is listed with the reason.
  16. Step 16Email this guest?Guests on tomorrow's go or cancelled departures that pass the check get the approved email; everyone else is skipped.
  17. Step 17Email the guestSends the approved go or cancel email from your workspace's sender, with replies going to your bookings inbox.
  18. Step 18Not emailedA call still open, a cancelled booking, no email or a failed check.
  19. Step 19Count the guest emailsIn code, not AI: counts the bookings for tomorrow that were emailed, not emailed (with the reason) or failed, from what each step really did.
  20. Step 20Brief the guides in SlackPosts tomorrow's approved calls with reasons to your guides' channel, with the guest emails sent and not sent (counted in code).
  21. Step 21DoneThe run history keeps the forecasts, the approved calls and every guest email.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Tomorrow (fictional): 8:00 Bay Kayak (12 guests) and 10:00 Ridge Hike (8 guests). Your kayak limit: gusts over 20 mph.

The agent produces

Kayak: marginal, gusts forecast near your limit, no guest email until you decide. Hike: go, afternoon showers forecast, packing email drafted. Waiting for the lead guide.

What you need

Everything it takes to run it.

About 35 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 $149 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 departures tab with each meeting point's Lat and Lon, and a bookings tab with guest emails.
  • Your written limits per activity, packing list and cancellation policy.

Setup, about 35 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 departures and bookings 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 guides use (Settings → Integrations → Slack).
  5. Pick your departures sheet. Open “Read tomorrow's departures” and pick your account, spreadsheet and departures tab.
  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 limits and policy. Open “Make the go / no-go call” and replace the placeholder with your limits per activity, packing list, cancellation policy and sign-off.
  8. Pick your bookings sheet. Open “Read the bookings” and pick your account, spreadsheet and bookings tab.
  9. Add your bookings inbox and guides' channel. Open “Email the guest” and enter the Reply-to address, then “Brief the guides in Slack” and pick your account and channel.
  10. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  11. Switch the trigger on. Open the trigger, set your time zone and switch the schedule on. It runs every evening at 17:00.

Is it a fit?

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

Built for

  • Kayak, boat and paddleboard tour operators
  • Hiking and bike tour companies
  • Outdoor adventure and guiding businesses in the US

What it doesn't do

  • It isn't a marine, aviation or lightning-detection service: it reads the National Weather Service area forecast (US only), and the guide's call on the day overrides it.
  • It never cancels or confirms a tour on its own: the lead guide approves every call, and departures left “marginal” get no guest email.
  • It doesn't process refunds or rebookings; those follow your policy in your booking system.
  • It applies only your written limits and never promises the weather.

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

Price

$149 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 Tour Weather Go/No-Go.

Can I rely on it for safety?

It recommends from your written limits and the public forecast; the lead guide makes every call, and the guide on site can always override it. It isn't a marine, aviation or lightning-detection service.

Where does the forecast come from?

The US National Weather Service, which is free and needs no key. It covers US locations only and gives area forecasts, not on-site measurements.

How long does setup take?

About 35 minutes: connect Google Sheets, the weather service and Slack, set up your departures and bookings tabs, and paste your limits and policy.

Is it worth paying for?

It's a one-time purchase that never renews, set against checking forecasts and emailing guests by hand every evening. You need a paid plan and your own AI key; Dry Run is free.

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 departures tab with Date, Time, Tour, Activity, Meeting point, Lat, Lon and Guide (Lat and Lon named exactly so, up to 4 decimals), and a bookings tab with Date, Time, Tour, Guest name, Email, Party size and Status. Keep upcoming rows in both.

Who decides whether a tour runs?

The lead guide. The agent recommends a call from your written limits; every call waits for approval, and departures left “marginal” get no guest email until you decide. Guides on site still make the final safety call.

Does it process refunds?

No. Cancelled guests get your own policy text; refunds and rebookings happen in your booking system.

How does it know which departures and bookings are tomorrow?

In code, not by the AI: “Keep tomorrow's departures” and “Keep tomorrow's bookings” work out tomorrow's date in your trigger's time zone and keep only rows whose Date is that day. The AI only judges the forecast against your limits and writes the emails.

Is this a subscription?

No. Tour Weather Go/No-Go is a one-time purchase of $149 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 Tour Weather Go/No-Go to work.

Free account, no credit card. Your Agents page opens with Tour Weather Go/No-Go ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works