Name Coordinates
openweathermap.reverse_geocode
ActionBusiness appsconnection required
Calls the OpenWeather API with the connection's credentials.
Read the place names that sit at a pair of coordinates, with their country codes and translations.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- OpenWeather
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- units, lang, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
lat Latitude to name, from -90 to 90. | number | Yes | — | -90–90 | 51.5074 |
lon Longitude to name, from -180 to 180. | number | Yes | — | -180–180 | -0.1278 |
limit How many place names to return. Leave blank for OpenWeather's default. | number | No | — | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"lat": 51.5074,
"lon": -0.1278
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The matched places, each with 'name', 'lat', 'lon', 'country', 'local_names' and, where OpenWeather has one, 'state'. | array | — |
count How many places were matched. | number | — |
{
"count": 0,
"items": []
}See Name Coordinates run in a workflow.
In a technical demo we add the OpenWeather connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.