Skip to content
For LLMsView as Markdown·

OpenWeatherMap

undefined

DetailValue
CategoryData
Base URLhttps://api.openweathermap.org
AuthenticationAPI Key
Endpoints6
Connector keyopenweather

Using OpenWeatherMap in a workflow

  1. Go to Connections and click New Connection.
  2. Pick OpenWeatherMap from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET Current Weather
GET 5-Day Forecast
GET One Call
GET Historical
GET Geocoding
GET Air Pollution

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Current Weather

DetailValue
Operation IDcurrent_weather_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select current_weather_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.

GET

5-Day Forecast

DetailValue
Operation ID5_day_forecast_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select 5_day_forecast_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.

GET

One Call

DetailValue
Operation IDone_call_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select one_call_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.

GET

Historical

DetailValue
Operation IDhistorical_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select historical_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.

GET

Geocoding

DetailValue
Operation IDgeocoding_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select geocoding_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.

GET

Air Pollution

DetailValue
Operation IDair_pollution_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your OpenWeatherMap connection from the Connection dropdown.
  3. In the Operation dropdown, select air_pollution_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream OpenWeatherMap API reference.