Open-Meteo

• Get current weatherGet current conditions for a place or an exact coordinate: temperature, feels-like, humidity, precipitation, wind, cloud cover, and a readable description of the weather code.
• Get hourly forecastGet an hour-by-hour forecast for up to 16 days, returned as one row per hour so a workflow can loop over the timesteps.
• Get daily forecastGet a day-by-day forecast for up to 16 days: highs and lows, precipitation totals and chance, wind, UV, and sunrise and sunset, returned as one row per day.
• Get historical weatherRead the weather that actually happened over a past date range, from Open-Meteo's archive of reanalysis data going back to 1940. Returns daily aggregations, hourly readings, or both. The archive runs a few days behind; for the last day or two, use 'Past days' on a forecast action instead.
• Get air qualityGet air-quality indices and pollutant levels for a place: European and US AQI, particulates, gases, dust, UV index, and (in Europe) pollen, now and, optionally, hour by hour.
• Search locationsSearch the GeoNames database for places matching a name and get back their coordinates, elevation, time zone, region, and population. Useful for pinning an exact point to reuse, or for telling same-named towns apart.
• Get 15 minute forecastGet a forecast in 15 minute steps instead of whole hours, for the next few hours or the next few days. Use it when an hourly row is too coarse to act on: when a shower arrives, when a gust hits, when it is worth moving something indoors. Where a high resolution national model covers the location the steps are genuinely 15 minutes apart; elsewhere the hourly values are interpolated.
• Get marine forecastGet sea conditions for a point on the water: wave height, direction and period, wind waves and swell separately, ocean currents, and sea surface temperature, now and by the hour and the day. The wave models only cover open water, so a point inland comes back as an error saying so rather than as a row of blanks.
• Get river dischargeGet the daily flow of the river nearest a point, in cubic metres per second, for up to a year ahead and three months back. The figures come from GloFAS, the global flood modelling system, and are what a flood watch or a river level alert is built on. Ask for the ensemble to get the spread between model runs rather than one number.
• Get elevationLook up how high the ground is at a place, or at up to 100 coordinates in one call. Heights come from the Copernicus digital elevation model on a 90 metre grid, in metres above sea level, and describe the terrain rather than anything standing on it. Paste a column of coordinates from a spreadsheet to profile a route or rank a list of sites.
• Get ensemble forecastRun the forecast dozens of times over from slightly different starting conditions and get back how far the runs disagree. Where the members agree the forecast is confident; where they scatter it is not, which is the difference between 'it will rain' and 'it might'. Each row gives the lowest, highest and mean member value per variable, so a workflow can act on the confidence rather than only on the headline number.
• Get seasonal forecastLook months ahead, out to about seven, with ECMWF's seasonal forecast. This answers a different question from a daily forecast: not what the weather will be on a given day, but how a whole week or month is leaning against its own long run normal. The anomaly variables carry that lean, which is what a planting date, a heating budget or a stock forecast turns on.
• Get climate projectionRead downscaled IPCC climate model output for any date from 1950 to 2050, at a resolution of around 25 km. This is not a forecast: a date in 2043 says what the model expects an average day of that season to look like by then, under a high emissions scenario. Use it to compare a future decade against a past one for the same place. Naming more than one model returns a column per model so they can be set side by side.
• Get solar radiationRead solar irradiance as weather satellites actually measured it, rather than as a weather model predicted it, going back as far as 1983. This is the number a solar yield or panel performance calculation wants. Set the tilt and the compass bearing of an array to get the irradiance falling on the panels rather than on flat ground.
• Get past forecastRead the forecast that was being issued on a past date, from the archive of model output kept since 2021. This is a different question from what the weather turned out to be: use it to score a forecast against the outcome, to reconstruct what a workflow would have seen on the day, or to settle an argument about what was predicted. For what actually happened, use 'Get historical weather' instead.
• Get a single model runRead one named run of one weather model exactly as it was issued. Every other forecast action answers with the freshest data available for each hour, stitched across runs; this one pins a single computation, so the whole series is internally consistent. That matters when comparing runs against each other or reproducing a number someone quoted. Runs start on fixed hours, usually 00:00, 06:00, 12:00 and 18:00 UTC.
• Compare forecast runsSee how the forecast for each hour has moved as that hour drew closer. For every hour it returns today's forecast beside the forecasts issued one, two and more days ago, plus a drift figure per variable: how much the outlook has shifted on average. Use it to tell a settling forecast from a wobbling one before committing to an outdoor booking, a delivery slot or a shutdown.
• Get location detailsLook up one place by the id that a search returned, and get the fuller record: the postcodes it covers, the whole chain of administrative areas it sits in, its elevation, time zone and population. Use it as the second step after 'Search locations', once a particular match has been chosen.

No actions match that.