The moment it happens
Look up the weather for any city from a link
You send a city name or coordinates to a private link and get the current weather back by email.
- Runs
- The moment it happens
- Apps
- OpenWeatherMap
- AI
- Not needed
- Access
- API key
Send this to your assistant
Create a ClickRuntime automation: give me a link I can send a city name or latitude and longitude to, and email me the current temperature and conditions there.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A travel planner, a delivery dispatcher or a small business owner often needs weather for a place that is not home: a client site in another country, a drop-off point tomorrow, a venue for a weekend event. Looking it up means opening an app, typing the city, choosing the right one out of several with the same name, and copying the numbers into a message or a spreadsheet. If this happens twenty times a day, those minutes add up quickly.
You send a city name or latitude and longitude to your personal link from a chat bot, a form, a shortcut or a spreadsheet script. The current weather for that place is fetched from OpenWeatherMap, formatted into a short readable line and either emailed to you or returned straight back to whatever sent the request.
It also suits developers who want a simple weather lookup for their own app without managing an API key in client code.
What you get out of it
Answers in seconds for any place
A dispatcher can ask about a drop-off town and get temperature, wind and conditions back immediately, without opening a separate weather site or app. That makes planning routes, deliveries and site visits noticeably quicker for the whole team.
Other tools can ask on your behalf
A spreadsheet, a chat shortcut or a form can send a city to the link, so teammates get weather without learning anything new or holding an account of their own.
Coordinates avoid city name confusion
There is a Springfield in many states and a Cambridge in two countries. Sending exact latitude and longitude removes the doubt about which place you meant. Using exact coordinates is also the best option when a site is in a village or at a remote location.
Keys stay out of client code
The OpenWeatherMap key sits as a secret on ClickRuntime's side, so a shortcut or web page that calls the link never contains it, and it cannot be copied by anyone viewing the page.
Consistent format every time
Each reply follows the same layout, so staff can read results at a glance and paste them into reports without reformatting different app screenshots. That also makes it easy to log results in a sheet for later.
How it works
What happens, step by step
When you send a city name or map coordinates to your private ClickRuntime link, the automation starts.
It looks up the current weather for that place on OpenWeather.
You get an email with the temperature, conditions and what it feels like, for example "Lisbon: 22°C, scattered clouds".
Before it runs live
- Connect OpenWeatherMap
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other OpenWeatherMap steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, notify
@on_event
def handle(event):
body = event.json or {}
params = {"appid": credentials.secret("OPENWEATHER_API_KEY"), "units": "metric"}
if body.get("city"):
params["q"] = body["city"]
else:
params.update(lat=body["lat"], lon=body["lon"])
w = http.get("https://api.openweathermap.org/data/2.5/weather", params=params).json()
text = f"{w['name']}: {w['main']['temp']:.0f}°C, {w['weather'][0]['description']}, feels like {w['main']['feels_like']:.0f}°C"
notify.email_me(f"Weather in {w['name']}", text)
return {"weather": text}FAQ
Common questions
How should I send the city?
Does it return the current weather or a forecast?
Can the answer come back directly to the caller?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get the day's weather every morning
Each morning at 7 you get today's temperature, conditions and rain chance for your city.
See how it worksGet warned before frost, snow or extreme heat
You hear about the weather only when freezing, snow or heat over your limit is forecast.
See how it worksKeep a monthly record of temperatures
Each day's weather is stored, and once a month you get averages and extremes.
See how it worksKeep exploring
Set up “Look up the weather for any city from a link” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
