One Call Forecast

openweathermap.one_call
ActionBusiness appsconnection required

Calls the OpenWeather API with the connection's credentials.

Read current conditions, minute-by-minute rain, 48 hourly steps, eight daily steps and any government weather alerts in a single One Call 3.0 request.

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

7 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
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'.
stringNo——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.
numberNo—-90–9051.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.
numberConditional—-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'.
stringNo——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.
stringNo—one of "standard", "metric", "imperial"—
lang
Two-letter language code for the human-readable weather descriptions, such as 'es' or 'de'. Defaults to the connection's setting, and to English.
stringNo——en
exclude
Comma-separated parts of the answer to leave out, any of: current, minutely, hourly, daily, alerts.
stringNo——minutely,alerts
  • 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.

{
  "exclude": "minutely,alerts",
  "lang": "en",
  "lat": 51.5074,
  "lon": -0.1278,
  "place": "London,GB",
  "postcode": "94040,US"
}

Output

One shape.

result

FieldTypeExample
lat
The latitude OpenWeather answered for.
number—
lon
The longitude OpenWeather answered for.
number—
timezone
The IANA time-zone name of that place, such as Europe/London.
string—
timezone_offset
That zone's offset from UTC, in seconds.
number—
current
Conditions now, unless 'current' was excluded.
object—
hourly
The next 48 hourly forecast steps, unless 'hourly' was excluded.
array—
daily
The next eight daily forecast steps, unless 'daily' was excluded.
array—
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—
{
  "current": {},
  "daily": [],
  "hourly": [],
  "lat": 0,
  "location": {
    "country": "",
    "lat": 0,
    "lon": 0,
    "name": "",
    "source": ""
  },
  "lon": 0,
  "timezone": "",
  "timezone_offset": 0
}

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.
  • 'minutely' is only published for some places and 'alerts' only when an agency has issued one, so both are absent more often than not.

See One Call Forecast 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.