WeatherMap provides visual weather data, forecasts, and mappings, helping users understand climate patterns or track severe weather conditions
WeatherMap provides visual weather data, forecasts, and mappings, helping users understand climate patterns or track severe weather conditions On Nagent, OpenWeatherMap is exposed as a fully-configurable developer tools integration that any agent can call — 2 actions, and no authentication authentication. No code is required to wire OpenWeatherMap into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use OpenWeatherMap to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire OpenWeatherMap into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against OpenWeatherMap, with input parameters and output schema. Drop these into any step of an agent built in Helix.
WEATHERMAP_GEOCODE_LOCATIONTool to resolve a human place name into canonical lat/lon coordinates using OpenWeather Geocoding API. Use when you need to convert location strings (city names, addresses) into coordinates for weather forecasts or other location-based queries. Returns up to 5 candidate matches; the first result is typically the most relevant.
Input parameters
Location query string in format 'city' or 'city,country_code' or 'city,state,country_code'. For US locations, you can include state code (e.g., 'Austin,TX,US'). Use ISO 3166 country codes (e.g., 'London,GB', 'Paris,FR'). The API supports 200,000+ registered locations.
Maximum number of location matches to return (1-5). Use this to limit results when multiple locations share the same name. Default is 5.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
WEATHERMAP_WEATHERTool for querying the OpenWeatherMap API. Returns current weather conditions only — no UV index, AQI, or official alerts. Timestamps are in UTC; apply the timezone offset field before grouping by local day.
Input parameters
A real city name (e.g., 'London', 'New York', 'Tokyo'). MUST be an actual city name - NOT a placeholder like 'your location', 'current location', or 'my location'. City names must be in English/Latin characters only. You may optionally append a country code (e.g., 'London,GB'). For US cities with state abbreviations, use the 3-part format 'City,StateCode,US' (e.g., 'Redding,CA,US', 'Portland,OR,US') - the 2-part format 'City,StateCode' will be interpreted as a country code (e.g., 'CA' = Canada, not California). If a 'city not found' error occurs, retry with a simpler string (e.g., drop state code, use just 'City' or 'City,CountryCode'). Small or remote locations may return no data; handle gracefully rather than retrying indefinitely.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 34 agents privately built on Nagent that already use OpenWeatherMap.
Build on Nagent
Connect OpenWeatherMap to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find OpenWeatherMap, and click "Connect Now." You'll authenticate with no authentication (it’s public) — Nagent handles credential storage and refresh automatically. Once connected, OpenWeatherMap is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once OpenWeatherMap is connected, you configure its 2 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop OpenWeatherMap steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a OpenWeatherMap event fires, the agent kicks off automatically.
Every OpenWeatherMap action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While OpenWeatherMap ships with 2 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching OpenWeatherMap together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build OpenWeatherMap-based workflows tailored to your business.