Resources · n8n integration

OpenWeatherMap n8n integrationAutomate OpenWeatherMap with n8n.

Weather data belongs in a workflow, not in a browser tab. The OpenWeatherMap n8n integration opens one node with 2 operations: the conditions of the moment, and the next 5 days. No trigger node comes with it, so a Schedule Trigger starts the run. Ops teams plan their week around that answer.

Try the OpenWeatherMap integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the OpenWeatherMap n8n integration actually cover?

It plugs the OpenWeatherMap node (n8n-nodes-base.openWeatherMap) into any workflow you build in n8n. The node gets current and future weather information through 2 operations on a single resource: default.currentWeather for what the sky is doing now, default.5DayForecast for the next 5 days. Each call takes a location, a unit format and an output language.

Take the morning briefing first. A Schedule Trigger, the node that starts a workflow at a fixed time, fires before the shift, default.currentWeather reads the conditions around each site, and the result lands in Slack where the team already looks. Push the same execution into Google Sheets and you keep your own history, one row per run, instead of asking the API twice for the same answer.

The second pattern plans rather than alerts. default.5DayForecast returns the weather data for the next 5 days, enough to decide whether an outdoor install, a delivery round or a shoot holds this week. That answer can leave as an email through Gmail, or feed a condition that only warns the crew when the forecast changes the plan.

The third pattern reacts to an incoming item. A Webhook, a URL n8n exposes so another service can call it, receives an order; the node then checks the weather at the delivery address through Zip Code or Coordinates, and the workflow picks a slot from there. Nothing runs by itself: the node answers when your workflow calls it, so the interval on the Schedule Trigger sets how fresh the data is.

For anything outside those 2 operations, the HTTP Request node calls any OpenWeatherMap endpoint, meaning any address of the API, and reuses the same credential, the login saved once in n8n and reused across workflows, through predefined authentication. Keep that split in mind while you design: current conditions and a 5 day horizon belong to the dedicated node, the rest of the API does not.

Two boundaries deserve a mention before you build. The catalog lists 1 resource, 2 operations and 0 events for this tool, and n8n ships no OpenWeatherMap trigger, so a weather workflow always starts with something else. If the platform choice is still open, the n8n review goes into hosting and pricing with more room than a FAQ answer.

Connect

How do you connect OpenWeatherMap to n8n?

  1. 01

    Get your API key

    OpenWeatherMap includes an API Key in the welcome email, once you verify your email address. That key is the only thing n8n asks for. Would you rather keep a key dedicated to automation? Open Account, then API Keys, type a name in the Create Key section, something like n8n integration, and select Generate.

  2. 02

    Create the credential in n8n

    In n8n, open the Credentials menu and create an OpenWeatherMap credential, the saved login that nodes reuse. This node supports one authentication method, an API access token, so there is a single field to fill: Access Token. Paste the key, save, and every workflow in that instance can reach it from a dropdown.

  3. 03

    Pick an operation and run it once

    Add the OpenWeatherMap node, select the credential, then choose the operation you need. Location Selection decides how you name the place: City Name, City ID, Coordinates or Zip Code. Put berlin,de in City, execute the node alone, and read the output before wiring anything after it.

Actions

What can the OpenWeatherMap node do in a workflow?

The OpenWeatherMap node exposes 2 operations. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Return current weather data

currentWeather

What you see in n8n

Notes & use cases

Returns the current weather data for one location, ready to route into a message, a spreadsheet row or a condition.

Key parameters

  • Location Selection: how you name the place, between City Name, City ID, Coordinates and Zip Code.
  • City: the name of the city to return the weather of, written as berlin,de, often {{ $json.city }} when the city arrives from a previous node.
  • Format: Metric returns Celsius and meters per second, Imperial returns Fahrenheit and miles per hour, Scientific returns Kelvin.
Use cases
a support workflow that attaches the local conditions to a late delivery ticket, so the agent explains the delay without opening a weather site.
02

Return weather data for the next 5 days

5DayForecast

What you see in n8n

Notes & use cases

Same node, longer horizon: this operation covers the weather data for the next 5 days at a single location. The output feeds a plan rather than an alarm, what is coming rather than what is happening.

Key parameters

  • Latitude and Longitude: the coordinates of the location, such as 13.39 and 52.52, handy for a site that carries no city name.
  • Zip Code: the postal code followed by its country, as in 10115,de.
  • Language: the two letter language code of the output, en, de and so on.
Use cases
a Monday planning workflow that sends the week ahead to field teams before the schedule gets locked.
Need help

Need help automating OpenWeatherMap with n8n?

A person reads every message.

FAQ

OpenWeatherMap and n8n: questions that come up

01Is the OpenWeatherMap n8n integration free?
On the n8n side, yes. The OpenWeatherMap node ships with n8n, so there is nothing to install and no extra cost, on n8n Cloud as well as on a self-hosted instance running the Community Edition under its Sustainable Use license. A workflow behaves the same way in both setups, so you can prototype on Cloud and move the same flow to your own server later. What an OpenWeatherMap account costs depends on the plan attached to your Access Token, and this page does not cover that side. For the node itself, the budget line stays at zero.
02What credentials does the OpenWeatherMap node need in n8n?
One API access token, nothing else. OpenWeatherMap puts an API Key in the welcome email sent after you verify your email address, and that key goes into the single Access Token field of the n8n credential. If you prefer a key dedicated to automation, open Account, then API Keys, type a name in the Create Key section, select Generate and copy the result. The node has no authentication selector, no OAuth screen and no scopes to tick. The credential is created once in the Credentials menu, and every OpenWeatherMap node you add later finds it in its dropdown.
03What are the limits of the OpenWeatherMap node?
Two operations, and the node stops there: current weather, and the weather data for the next 5 days. It exposes 1 resource, 0 events and no trigger. Every call needs a location, given through City, City ID, Latitude and Longitude, or Zip Code, with Format and Language left as options. Any other OpenWeatherMap endpoint sits outside the node, so the HTTP Request node takes over and reuses the same credential through predefined authentication. Worth knowing before you design a workflow around a value this node does not return.
04Does the OpenWeatherMap node update in real time?
No, and it cannot: n8n ships no OpenWeatherMap trigger node. A weather workflow therefore starts somewhere else, with a Schedule Trigger running at a fixed interval, with an n8n Webhook, meaning a URL another service calls, or with the trigger of a tool you already automate. The node answers only when the workflow reaches it, so the interval you choose defines how fresh the values are. Set that interval from the decision behind it: a morning briefing runs once a day, a delivery check runs when the order arrives.
05n8n or Make for OpenWeatherMap?
It depends on hosting and on how you want to pay. n8n runs on your own infrastructure through Docker or npm, or on n8n Cloud, and the same workflow behaves identically in both. Make is hosted by its publisher, with no self-hosting option, and it bills per operation, which changes the math when a weather check repeats all day. n8n fits when the data has to stay on machines you control. Make keeps its edge when its visual logic suits the people who will maintain the flows. Both reach OpenWeatherMap; the difference sits in hosting, data control and cost model.
Same platform

Other docs you might need on this stack.

Browse all integrations