FlowRunner
PricingContact
Theme
Start Free

Retrieve numerical weather forecasts for any coordinates and reach Windy's worldwide webcam network. Agents factor real conditions into dispatch, scheduling, and field work.

14 actions API key available
Windy website ↗ Platform Documentation ↗ Capability data verified 2026-07-31
Tomorrow's job schedule is finalized late the afternoon before
Get Weather Forecast returns wind, gust and precipitation series for each site's coordinates
Agent tests each site's working window against the crew's gust and precipitation limits
Get Nearby Webcams pulls the current image from a camera within range of the marginal sites
Sites comfortably inside the limits are confirmed and their crews are notified
Dispatch channel receives each marginal site with its gust curve and the live image side by side
The dispatcher proceeds, shifts the window, or stands the crew down for each marginal site

What This Integration Enables

Windy brings two very different things into a flow, and the combination is what makes it useful for field operations rather than for a dashboard. The first is raw numerical forecast data for a single coordinate pair from a chosen weather model: a timestamp array plus one value array per requested parameter and level, keyed as "parameter-level" such as temp-surface, with a units object describing every series. Wind comes back as u and v vector components and precipitation as three-hour accumulations. Model choice matters, and the connector does not hide it: global models cover everything, while regional models such as AROME, ICON D2, NAM and HRRR return higher resolution inside their domain and no data at all outside it. Marine forecasts add wave, wind wave and swell height, period and direction plus ocean currents, and the air quality forecast from Copernicus CAMS adds the US Air Quality Index with sulfur dioxide, dust, carbon monoxide, ozone, nitrogen dioxide, PM10 and PM2.5, and pollen for six species on the European model.

The second is Windy's worldwide webcam network, reachable by category, radius around a point, bounding box, map cluster, or direct id, returning preview and daylight images, live player embeds and timelapse links. Windy issues a separate key per product and the keys are not interchangeable, so a connection can subscribe to forecasts, webcams, or both, and an action whose key is missing fails with a clear message rather than silently.

Why this pairing matters operationally: a forecast is a model output, and a camera is an observation. Numbers tell you what is predicted for 14:00 tomorrow. An image tells you what is actually happening at the pass right now. A person deciding whether to send a crew wants both, and FlowRunner agents are built to put both in front of them at the same moment.

Without FlowRunner

Forecast checked by eye Someone opens a weather app the night before and forms an impression of tomorrow
One number for the whole day A daily summary hides the three-hour window where the gusts actually exceed the limit
Conditions confirmed on arrival The crew drives to site and finds out there what the weather is doing

With FlowRunner

Forecast read as a series Hourly values per parameter are tested against the actual operating limit for that crew and task
Windows evaluated separately The flow finds the specific hours that fail rather than passing or failing a whole day
Conditions seen before departure A live camera near the site sits next to the numbers when the call is made

Use Case Scenarios

Threshold alerts on the working window, not the day

An outdoor operation has a hard gust limit for lifting work. Rather than checking a daily forecast, the agent calls Get Weather Forecast for each site with the wind gust and precipitation parameters, reconstructs gust speed from the u and v components, and tests only the hours the crew is scheduled to be working. A day that fails between 13:00 and 16:00 and passes everywhere else produces a schedule shift rather than a cancellation, and the alert that reaches Slack names the failing window instead of the whole date.

Marine conditions for coastal and offshore work

A vessel movement or a coastal survey depends on wave height, period and swell direction rather than on wind alone. The agent calls Get Marine Forecast for the working coordinates and reads the wave, wind wave and swell series along with the current vectors, remembering that wave direction is reported as where the waves come from. It checks the operating envelope for the vessel and the task, and where the point falls outside the chosen sea model's coverage it raises that explicitly rather than reporting a clean pass on missing data.

Air quality driving ventilation and outdoor activity

A facilities flow reads Get Air Quality Forecast for each site every morning, tracking the US Air Quality Index alongside PM2.5 and, on the European model, the pollen series. When the index or the particulate concentration crosses the threshold for a site, the agent switches building ventilation to recirculation through Home Assistant and posts an advisory for outdoor activities scheduled that day. Pollen thresholds are handled separately from particulates, because the people affected and the response are different.

Human-in-Loop Highlight

The gate is standing down a crew, and it is the clearest example in this batch of a decision that should never be automated in either direction. Sending people into gusts that exceed a lifting limit risks injury. Standing them down costs a day of billable work, a customer reschedule, and the crew's confidence in the system that made the call. A forecast model is not entitled to decide that, and neither is an agent reading one. So the agent does everything up to the decision and nothing past it. It identifies the marginal sites, pulls Get Nearby Webcams within range of each one, and posts to dispatch: "Site 12, Ridgeway. Forecast gusts 24 to 29 knots between 13:00 and 16:00 against a 25 knot lift limit, HRRR model. Nearest camera 4 km away, image from 6 minutes ago attached. Proceed, shift to the 08:00 to 12:00 window, or stand down?" The dispatcher looks at the sky in the picture, weighs it against the curve, and answers. The sites that are plainly fine were confirmed without anyone being asked, which is what makes the dispatcher's attention worth spending on the three that are not.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

14 actions

Point Forecast

3
  • Get Weather Forecast Retrieves a raw numerical weather forecast for one coordinate pair from a chosen Windy model. Returns a timestamp array plus one value array per requested parameter and level, keyed as "parameter-level" such as temp-surface, with a units object describing each series. Wind is returned as u and v vector components and precipitation as three-hour accumulations. Coordinates are rounded to two decimal places, roughly 1 km. Choose a model that covers the location, since regional models such as AROME, ICON D2, NAM and HRRR return no data outside their domain.
  • Get Marine Forecast Retrieves a raw wave, swell and ocean current forecast for one coordinate pair from a Windy sea model. Waves, wind waves and swells each come back as height, period and direction series, with direction reported as where the waves come from in degrees, and currents as u and v vector components. All sea parameters are surface level only. The point must lie over water covered by the chosen model.
  • Get Air Quality Forecast Retrieves a raw air quality and pollen forecast for one coordinate pair from a Copernicus CAMS model. Returns the US Air Quality Index from 0 to 500 together with concentrations of sulfur dioxide, dust, carbon monoxide, ozone, nitrogen dioxide, PM10 and PM2.5, and on the European model alder, birch, grass, mugwort, olive and ragweed pollen. All parameters are surface level. Used to drive health alerts, ventilation control and outdoor activity planning.

Webcams

6
  • Search Webcams Searches Windy's worldwide webcam repository by category and geography, returning the total match count plus a page of webcams. Each result carries a title, status, view count and last update timestamp, and depending on the requested parts it also carries categories, preview and daylight image URLs, coordinates and place names, timelapse and live player embeds, and detail links. Categories combine with AND or OR logic while continents, countries and regions always use OR. Returns at most 50 per call, paged by offset up to 1,000 on the free tier and 10,000 on professional. Image URLs are signed and expire after 10 minutes on free and 24 hours on professional.
  • Get Nearby Webcams Finds webcams within a radius around a geographic point, returning the total match count plus a page of webcams with images, coordinates, place names and player links. The radius is measured in kilometres and cannot exceed 250 km. Used to show live conditions around a venue, trailhead, marina or delivery address, or to pair a location with a point forecast. Returns at most 50 per call.
  • Get Webcams In Bounding Box Returns the webcams inside a rectangular area defined by its north, east, south and west edges, with the total match count. Used to populate a map viewport, monitor a corridor such as a mountain pass or coastline, or restrict a category search to one area. Returns at most 50 per call, paged by offset.
  • Get Webcam Retrieves a single webcam by numeric id. Returns title, status, view count, last update timestamp, categories, coordinates and place names, plus current and daylight image URLs in every size available to your tier, embed links for the live stream and the daily, monthly, yearly and lifetime timelapses, and detail links. Image URLs are signed and expire, so call this again rather than caching the URLs.
  • Get Webcams By IDs Retrieves up to 50 specific webcams in one call from their numeric ids, returning the same feed parts as the search actions. Used to refresh a saved shortlist and its signed image URLs in one request instead of fetching each webcam separately. When ids are supplied the API applies no other filter.
  • Get Webcam Map Clusters Returns a set of webcams spread evenly across a map bounding box at a given zoom level so markers do not overlap when drawn. Each returned webcam carries a cluster size indicating how many nearby webcams it represents. Zoom levels follow the Google tile system from 4 to 18, and at zoom 4 the bounding box may span at most 22.5 degrees of latitude and 45 of longitude, halving with each lower level.

Webcam Reference Data

5
  • List Webcam Categories Returns the complete list of webcam categories, each with the id used by the search filters and its name translated into the requested language. Used to build a category picker or to translate the ids returned on a webcam feed.
  • List Webcam Continents Returns every continent geocode with its translated name. The codes are the values accepted by the continents filter of Search Webcams and are reported as the continent code on a webcam's location.
  • List Webcam Countries Returns every country geocode with its translated name. The codes, such as DE or NO, are the values accepted by the countries filter of Search Webcams and are reported as the country code on a webcam's location.
  • List Webcam Regions Returns every region geocode with its translated name. Region codes combine a country code and a region suffix, such as CH.ZH or ES.51, and are the values accepted by the regions filter of Search Webcams. The list is worldwide, so filter by country prefix when you need one country's regions.
  • List Webcam Cities Returns every city geocode with its translated name. The codes are the values accepted by the cities filter of Search Webcams and match the city code reported on a webcam's location. The list is worldwide and large, so narrow it before presenting it to a user.

Frequently Asked Questions

What can FlowRunner do with Windy?

FlowRunner agents can run Get Weather Forecast, Get Marine Forecast, and Get Air Quality Forecast in Windy, plus 11 more actions.

Does connecting Windy to FlowRunner require OAuth?

No. Windy connects to FlowRunner with an API key, no OAuth flow required.

Can Windy trigger a FlowRunner workflow automatically?

Windy doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Windy

$100 in credits. No card required. Connect in minutes.