- Current conditions: temperature, feels-like, humidity, wind, precipitation probability, UV index and weather condition
- Forecasts by hour (up to 240 hours) and by day (up to 10 days), plus hourly history for the past 24 hours
- Halo's maps scenario answers “what's the weather at…” with a live call through Atlas
- Four read-only routes keyed by latitude and longitude; units and language selectable per request
- Your key, your Google Cloud project; every call logged in your tenant
Google Weather API Connector
Google's Weather API — current conditions, hourly and daily forecasts and recent history for any coordinate — connected to Apivom Halo with your own Maps Platform key so the assistant can answer weather questions for a location with live data, and registered in Apivom Atlas for your own use.
What you can do
Use cases
- Weather in the assistant's answer — Halo tells a caller whether it will rain at the outdoor venue tomorrow afternoon, from the daily and hourly forecast for that exact location.
- Field and delivery planning — Check the hourly forecast for a service address before dispatching an outdoor crew, with your own tooling against the registered route.
- Context for incidents — Pull the 24-hour history for a site to document conditions at the time of a reported fault.
The Weather API is one of Google Maps Platform's environment APIs on weather.googleapis.com. Four read-only routes cover it: current conditions for a coordinate, an hourly forecast for up to ten days ahead, a daily forecast, and hourly history for the previous day — each returning temperature, apparent temperature, humidity, wind, precipitation, UV index, visibility and a condition code with a localised description. Apivom Atlas registers all four. Apivom Halo uses them in its maps scenario: when a visitor or caller asks about the weather at a branch, an event venue or a delivery address, the assistant resolves the location, calls the Weather API through Atlas with the tenant's key and answers with current conditions and the short-term forecast rather than a guess. The key can be stored in Apivom Iris with your other Google Maps Platform credentials; no scheduled CRM workflow uses weather data today. Requests go out with your own Google Cloud API key, Google bills the owning project, and each call is logged in your tenant.
Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
How far ahead and how far back does the data go?
Hourly forecasts up to 240 hours (ten days), daily forecasts up to ten days, and hourly history for the past 24 hours. Coverage and some fields vary by region; Google documents the supported countries.
Is weather data used anywhere in the CRM?
Not today. The connector is registered so the key can be stored in Apivom Iris and the routes are documented in the AI integration guide; the live product use is Halo's maps scenario.
Which Google Cloud project pays for the calls?
The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.