Resources · Make integration

Windy Make integrationAutomate Windy with Make.

Want Windy webcam lookups inside your workflows? The Windy Make integration gives you 3 modules: two webcam searches and one open API call. This guide is for travel and outdoor teams, and it walks you from connection to a working first scenario.

Try the Windy integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Windy Make integration do for you?

The Windy Make integration links your Windy account to Make, a visual tool where you chain apps without code. Inside a scenario (the automation you build in Make), Windy can look up webcams and reach any part of its API, then pass what it finds to your other apps.

Webcam list for a destination. A travel agency stores trip requests in a spreadsheet. When a request lands, Search Webcams pulls the matching webcams, and the next module sends them to the client file or a chat channel.

Webcams for a map view. If you publish a map on a site or an internal dashboard, Search WebCams Optimized For a Map is the search built for that display, as its name says. Each webcam comes back as a bundle, one item that flows to the next module.

Anything else the API offers. When neither search covers your case, Make an API Call reaches any endpoint of the Windy API with the same connection.

Be aware of one limit: Make says its own documentation for Windy is incomplete, because public information about the app is scarce. This page therefore sticks to what Make lists and never guesses field names. For a broader view of the platform, read our Make review. The same app often exists as an n8n node too, and n8n vs Make lays out the criteria. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect Windy to Make?

  1. 01

    Add a Windy module

    In a scenario, click the + and search for Windy. Pick any of its modules, then click Create a connection. A connection is your Windy account linked to Make once and reused by every Windy module.

  2. 02

    Name the connection

    Giving it a name is optional, yet it pays off later. A clear label such as the team or project helps you pick the right account when several people build scenarios in the same Make organization.

  3. 03

    Authorize and save

    Depending on what Windy asks for, either approve Make on the Windy page that opens or paste the key Windy gives you. Then click Save, and the module is ready to fill.

First scenario

Your first scenario with Windy

GoalWhen a new trip request reaches another app, Make searches Windy for webcams and passes each result along.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Windy has no trigger, start with the app that holds your requests, a spreadsheet or a form tool.

  2. 02

    Add Search Webcams

    Click the + on the right of that first module, search for Windy and choose Search Webcams. Create the connection or reuse the one you already saved.

  3. 03

    Map the request data

    Fill the Windy fields Make shows you, dragging values from the previous module into them. Make lists what it can read once the connection exists, so you rarely type anything by hand.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, so you can check that webcams actually came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on each bundle counts as one operation on your plan.

Modules

What each Windy module does

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

Windy1

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Windy API from your scenario, reusing the connection you already created, so a missing module never blocks you.

When to use it
the two webcam searches do not return what your process needs and the Windy API documentation shows an endpoint that does.
Watch out
you write the request yourself, so test it with Run once before switching the scenario on.
Windy2

Search WebCams Optimized For a Map

SearchIn the docs only

Gives you a set of webcams shaped for a map display, as the module name indicates, with each webcam arriving as its own bundle for the following modules.

When to use it
you feed a map on a website or a dashboard and want the search designed for that purpose.
Watch out
a search can return zero, one or many bundles, so plan what the next module does when nothing is found.
Windy3

Search Webcams

SearchIn the docs only

Returns the Windy webcams that match your search, ready to send to a sheet, a message or a client file further down the scenario.

When to use it
you need a plain list of webcams for a request, with no map in the picture.
Watch out
every webcam found is a separate bundle, and each module after it runs once per bundle, which adds operations to your plan.
Need help

Need help automating Windy with Make?

A person reads every message.

FAQ

Windy and Make: common questions

01Is the Windy Make integration free?
Yes, Windy is a standard app, so it works from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB 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 execution. Usage is counted in operations each month, and Windy itself carries no separate price in Make.
02What do you need to connect Windy to Make?
A Windy account and a Make account. Make's documentation for Windy lists no specific prerequisite. You add a Windy module, click Create a connection, optionally name it, then either authorize Make on the Windy page or paste the key Windy provides, and click Save. The connection is then reused by all three Windy modules, so you set it up only once per account. If several teammates build scenarios, give each connection a clear name so nobody picks the wrong Windy account by mistake.
03Does the Windy Make integration have a trigger?
No. Windy offers no trigger module, so nothing in Windy can start a scenario by itself. You have two ways to start anyway. Place a trigger from another app first, such as a new row in a spreadsheet, and add a Windy search after it. Or put a Windy search as the first module and let Make run it on the scenario schedule, every 15 minutes by default, with 1 minute as the shortest interval on paid plans.
04What if a Windy module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Windy API with the same connection, which covers what the two webcam searches do not. Keep in mind that Make describes its Windy documentation as limited, because little public information about the app exists. You will rely on the Windy API documentation to build the request, then test it with Run once and check the bundles that come back before activating.
05Should you use Make or n8n for Windy?
It depends on the tool your team already runs. On Make, Windy offers 3 modules: two webcam searches plus Make an API Call for the rest of the API, built in a visual editor with clearly labelled buttons. The same app often has an n8n node as well. Compare which operations each side exposes for the webcams you need, and choose the platform where your other scenarios and connections already live, so everything stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations