Weather Overview
openweathermap.weather_overview
ActionBusiness appsconnection required
Calls the OpenWeather API with the connection's credentials.
Read OpenWeather's written summary of today's or tomorrow's weather for one place, ready to paste into a message.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- OpenWeather
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- units, lang, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
date The day to summarise, as YYYY-MM-DD. OpenWeather only writes one for today or tomorrow; leave blank for today. | string | No | — | matches \d{4}-\d{2}-\d{2} | 2024-03-14 |
place A place name to resolve through the Geocoding API, as 'city', 'city,country code' or 'city,state code,country code' for the US — for example 'London,GB'. | string | No | — | — | London,GB |
lat Latitude of the place to look up, from -90 to 90. Give it together with 'lon', or name a 'place' or a 'postcode' instead. | number | No | — | -90–90 | 51.5074 |
lon Longitude of the place to look up, from -180 to 180. Give it together with 'lat', or name a 'place' or a 'postcode' instead. | number | Conditional | — | -180–180; only with lat | -0.1278 |
postcode A post code and its two-letter country code, divided by a comma, resolved through the Geocoding API — for example '94040,US'. | string | No | — | — | 94040,US |
units The unit system for this call: 'standard' is Kelvin and metres per second, 'metric' is Celsius, 'imperial' is Fahrenheit. Defaults to the connection's setting. | string | No | — | one of "standard", "metric", "imperial" | — |
- At least one of place, lat, postcode must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"date": "2024-03-14",
"lat": 51.5074,
"lon": -0.1278,
"place": "London,GB",
"postcode": "94040,US"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
lat The latitude OpenWeather answered for. | number | — |
lon The longitude OpenWeather answered for. | number | — |
tz The time-zone offset the summary is written for. | string | — |
date The day the summary covers, as YYYY-MM-DD. | string | — |
units The unit system the summary quotes figures in. | string | — |
weather_overview The written summary itself. | string | — |
location.lat The latitude this call actually used. | number | — |
location.lon The longitude this call actually used. | number | — |
location.name The place name the Geocoding API matched; empty when coordinates were given. | string | — |
location.country The two-letter country code of the matched place, when one was geocoded. | string | — |
location.source How the coordinates were reached: 'coordinates', 'geocode' or 'postcode'. | string | — |
{
"date": "",
"lat": 0,
"location": {
"country": "",
"lat": 0,
"lon": 0,
"name": "",
"source": ""
},
"lon": 0,
"tz": "",
"units": "",
"weather_overview": ""
}Notes
- One Call API 3.0 needs the separate 'One Call by Call' subscription on the OpenWeather account; without it OpenWeather answers 401 for this endpoint.
- A 'place' or 'postcode' costs one extra Geocoding API call before the weather call; passing 'lat' and 'lon' skips it.
See Weather Overview run in a workflow.
In a technical demo we add the OpenWeather connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.