Resources · Make integration

Weather Make integrationAutomate Weather with Make.

Need the weather for a place right inside an automation? The Weather Make integration gives you 2 action modules: one reads current conditions, the other a forecast of 1 to 16 days. This guide is for ops and marketing teams, and it walks you from the connection to a first working scenario.

Try the Weather integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Weather Make integration do for you?

The Weather Make integration lets a scenario, the automation you build in Make, ask for the weather at a location and pass the answer to the next step. It has no trigger of its own, so it always works as a step inside a flow that something else starts.

Forecast attached to a booking. An event planner logs a new outdoor booking in a spreadsheet app. The scenario takes the venue city, runs Get daily weather forecast for it, and writes the outlook next to the booking so the team can plan a backup.

Conditions on a field report. A technician closes a site visit in a form tool. Get current weather adds what the sky looked like at that address, which helps when a client later asks why the job was postponed.

Warning before a delivery. A new order reaches your store app with a shipping city. The forecast module checks the coming days, and a filter decides whether a message goes to the customer.

What the app does not do: it cannot start a scenario, and the documentation gives no field list and no limit, so plan your first test with Run once to see what comes back. If you are still choosing a tool, read n8n vs Make; to learn the editor step by step, see Make training.

Connect

How do you connect Weather to Make?

  1. 01

    Add a Weather module

    In your scenario, click the +, type Weather in the search box and pick one of the two modules. Make then asks for a connection, meaning your Weather access linked to Make once and reused by both modules.

  2. 02

    Create the connection

    Click Create a connection. Giving it a name is optional, but a clear one helps when a teammate opens the scenario. The Weather documentation lists no prerequisite, so there is nothing to prepare beforehand.

  3. 03

    Authorize and save

    Follow what the window asks: authorize Make on the app page, or paste the key the app gives you. Then click Save. The module is ready as soon as the connection appears in its dropdown.

First scenario

Build your first scenario with Weather

GoalWhen a new location arrives from another app, Make fetches its daily forecast and hands it to the next step.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app that holds your locations, such as the spreadsheet where bookings land, as the first module.

  2. 02

    Add the forecast module

    Click the + on the right of that first module, search Weather and choose Get daily weather forecast. Select the connection you created, or click Add to make one.

  3. 03

    Map the location

    In the location setting, map the city or address coming from the first module instead of typing it. Each bundle, one item flowing between modules, then gets its own forecast.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you see exactly what the forecast returns before you rely on it.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Weather modules do

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

Weather1

Get current weather

Action

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

Returns the weather right now at the location you give it, so a record can carry the conditions of the moment it was created.

When to use it
a technician closes a job or a delivery is signed off, and you want the conditions at that address stored with it.
Watch out
it describes the present only; for anything ahead, the forecast module is the one to pick.
Weather2

Get daily weather forecast

Action

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

Gives you a day by day outlook for a location, anywhere from 1 to 16 days ahead, ready to map into the next module.

When to use it
a booking, a shoot or a site visit is planned outdoors, and you want its forecast attached as soon as the date is set.
Watch out
run it once with a real place first and read the bundle, since the documentation does not describe the output.
Need help

Need help automating Weather with Make?

A person reads every message.

FAQ

Weather and Make: common questions

01Is the Weather Make integration free?
Yes. Weather is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Every module execution counts as an operation, and usage is counted in credits per month, so one location checked by one module is one operation.
02What do you need to connect Weather to Make?
Only a Make account and the Weather connection. The Weather documentation lists no prerequisite and no dedicated setup steps, so the generic Make flow applies: add a Weather module, click Create a connection, optionally name it, then authorize Make on the app page or paste the key the app provides, and click Save. The same connection serves both modules, Get current weather and Get daily weather forecast, so you set it up only once per account.
03Does Weather trigger a Make scenario in real time?
No. Weather has no trigger module at all, so it cannot start a scenario by itself. You start the flow another way: with a trigger from another app, such as a new row or a new order, or with the schedule on the first module, which runs every 15 minutes by default on a new scenario. Once the flow is running, the Weather modules act as steps: they receive a location, fetch the conditions or the forecast, and pass the result to whatever comes next.
04What if a Weather module is missing or does not fit?
It depends on what is missing. Weather offers only two actions and has no Make an API Call module, so there is no way to send a custom request to the app from Make. If you need something those two modules cannot give, look for another weather app in the Make catalog of more than 3000 standard apps, or ask the team: a Make agency can check whether another route fits your use case before you build around a gap.
05Should you use Make or n8n for Weather?
It depends on where the rest of your automations already live. On Make, Weather gives you two ready modules, available from the Free plan, that you configure without code and test with Run once. Many apps also have an n8n node, so check whether Weather has one before deciding. The useful criterion is practical: if your bookings, orders or reports already run through Make scenarios, adding a weather step there keeps everything in one place and one connection.
Same platform

Other docs you might need on this stack.

Browse all integrations