Appearance
OpenWeatherMap
undefined
| Detail | Value |
|---|---|
| Category | Data |
| Base URL | https://api.openweathermap.org |
| Authentication | API Key |
| Endpoints | 6 |
| Connector key | openweather |
Using OpenWeatherMap in a workflow
- Go to Connections and click New Connection.
- Pick OpenWeatherMap from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | current_weather_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
current_weather_0. - 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
| Detail | Value |
|---|---|
| Operation ID | 5_day_forecast_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
5_day_forecast_1. - 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
| Detail | Value |
|---|---|
| Operation ID | one_call_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
one_call_2. - 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
| Detail | Value |
|---|---|
| Operation ID | historical_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
historical_3. - 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
| Detail | Value |
|---|---|
| Operation ID | geocoding_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
geocoding_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
| Detail | Value |
|---|---|
| Operation ID | air_pollution_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your OpenWeatherMap connection from the Connection dropdown.
- In the Operation dropdown, select
air_pollution_5. - 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.