Resources · Make integration

OpenWeatherMap Make integrationAutomate OpenWeatherMap with Make.

Weather can decide what your automation does next. The OpenWeatherMap Make integration adds 2 modules, the bricks you chain into a scenario, and a scenario is simply the automation you build in Make. Neither module waits for an event, so the run starts elsewhere.

Try the OpenWeatherMap integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OpenWeatherMap Make integration actually do?

Short answer: Make can read the weather, not write it. OpenWeatherMap brings 2 modules to Make, both of them actions, which means each one does a job when your scenario reaches it. One returns the conditions at a place right now. The other returns the days ahead. Everything else in the scenario decides what that weather changes.

Three shapes come back often. The morning briefing: a scenario runs on its own schedule, Get current weather reads the towns you cover, and the answer goes wherever your team looks first. The planning check: Get weather forecast reads the days ahead before a delivery round or an outdoor shoot, so the call gets made early instead of at dawn. The reaction: another app starts the scenario, Get current weather reads the site, and what happens next is built on that answer.

Two things this app does not do in Make. It has no trigger, the kind of module that starts a scenario by itself, so nothing on the OpenWeatherMap side can wake Make up. The start always comes from Make's own scheduling or from another app. There is also no generic Make an API Call module in this app, so what you can build stops at what the 2 modules return. The documentation lists no size or volume limit on them, which also means there is no published ceiling to design around.

The same weather job exists on the other side of the fence. n8n has an OpenWeatherMap node too, and the OpenWeatherMap n8n integration page covers it. Picking between the two is mostly a question of where your other automations already run, and the n8n vs Make comparison goes through the criteria.

If Make is new and the editor still looks like an empty canvas, the Make training covers the first scenarios before you hang anything important on the weather.

Connect

How do you connect OpenWeatherMap to Make?

  1. 01

    Drop a module in first

    A connection in Make is your OpenWeatherMap account linked once and reused by every module of the app, and you create it from inside a module. Add Get current weather to a scenario, then click Create a connection.

  2. 02

    Name it, then authorize

    Make offers to name the connection. Give it something you will still recognize in six months, or skip that. Then Make either sends you to the app's own page to authorize the link, or asks for the key the app hands you. Follow whichever window opens.

  3. 03

    Save and forget it

    Click Save. The connection is now attached to your Make account, and the next OpenWeatherMap module you add will offer it instead of asking again. The documentation for this app lists no prerequisite to prepare beforehand.

First scenario

Your first scenario, step by step

GoalOn the schedule you set, Make asks OpenWeatherMap what the weather is doing at a place and passes the answer down the scenario.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Search OpenWeatherMap by name and pick Get current weather.

  2. 02

    Link the account

    The module asks for a connection before it will do anything. Click Create a connection, go through the window Make opens, and save. Every OpenWeatherMap module after this one reuses it.

  3. 03

    Point it at a place

    Fill the fields the module shows so it reads the location you care about. When it runs, it hands back a bundle, which is one item passing from a module to the next.

  4. 04

    Add the second module

    Click the + on the right of Get current weather and add Get weather forecast. Map the data you need from the first module so the two of them read the same thing.

  5. 05

    Test with Run once

    Click Run once. The scenario executes a single time and shows the bundles each module received, so you read the real answer before anything downstream depends on it.

  6. 06

    Schedule it and switch on

    Set Scheduling on the first module, every 15 minutes by default, then switch the scenario on. Each run of each module counts as one operation, the unit Make counts against your plan.

Modules

What the 2 modules actually do

OpenWeatherMap gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

OpenWeatherMap1

Get current weather

Action

In Make“Returns current weather information for a specified location.”

Get current weather returns the conditions at a place you name, taken at the moment the scenario runs. One module, one answer, ready for whatever the next module does with it.

When to use it
a morning message telling a delivery team what they are driving into today.
Watch out
the answer is a snapshot of that single run, so a scenario checking twice a day knows nothing about the hours in between.
OpenWeatherMap2

Get weather forecast

Action

In Make“Returns 1-16 days weather forecast for a specified location.”

Where the first module looks at now, this one looks ahead. Get weather forecast returns the daily outlook for a place, up to sixteen days out, in a single run.

When to use it
booking an outdoor shoot or a site visit a week before anyone blocks a calendar.
Watch out
it answers with the days to come, not with what is happening right now; for that, the other module is the one you want.
Need help

Need help automating OpenWeatherMap with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the OpenWeatherMap Make integration free?
Yes. OpenWeatherMap is a standard app in Make, and standard apps ship with every plan including Free, alongside more than 3,000 others. What Free limits is the running, not the app: 2 scenarios active at a time, a scheduled scenario firing every 15 minutes at the fastest, and 5 minutes for a single run to finish. Paid plans drop the interval to a minute, lift the cap on active scenarios and stretch a run to 40 minutes. Your own OpenWeatherMap account is a separate matter, handled on their side.
02What do you need to connect OpenWeatherMap to Make?
An account on OpenWeatherMap and a single authorization inside Make. The documentation for this app lists no prerequisite beyond that, so there is nothing to install first and no setting to flip. In the editor, add one of the 2 modules, click Create a connection, name it if you want, then either authorize Make on the app's own page or paste the key the app hands you, and save. That connection is the account linked to Make once, and every OpenWeatherMap module in every scenario picks it up instead of asking again.
03Does OpenWeatherMap trigger a Make scenario in real time?
No, because it has no trigger at all. Both modules are actions, so neither one watches the sky and wakes Make up. A scenario using them has to start somewhere else. Either Make's own scheduling on the first module, which is every 15 minutes by default and goes down to a minute on a paid plan, or a trigger belonging to another app, the instant kind that calls Make through a webhook the moment something happens on its side. So you decide how often the weather gets read, rather than the weather deciding when the scenario runs.
04What if a module is missing or a limit gets in the way?
It depends on what is missing. OpenWeatherMap in Make is these 2 modules and nothing more, and this app has no generic Make an API Call module, so you cannot reach anything the 2 modules do not already return. On limits, the documentation publishes none for them, no size and no volume, so there is no known ceiling to design around. If what you need sits outside those 2 modules, the usual route is another app in Make that covers it, or a hand from the team on the build.
05Make or n8n for OpenWeatherMap?
It depends on where the rest of your work already runs. The same weather job can be built either way: Make draws a scenario as a chain of modules you click together, and n8n has an OpenWeatherMap node of its own. If your other automations already live in one of the two, that is usually the answer, because a second tool means a second place to debug at eleven at night. Starting from zero, the honest test is to build this exact scenario in both and keep the editor you stop fighting. The comparison page on this site goes criterion by criterion.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations