Skip to content
Book a demoStart free
Connectors

OpenWeather connector

Set up the OpenWeather connector in Kaivo: authentication, configuration, the 1 BigQuery tables it syncs, and answers to common questions.

OpenWeather connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your OpenWeather data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from OpenWeather instead of moving it.

Sync your OpenWeather forecasts and conditions into BigQuery with Kaivo to analyse weather over time and relate it to your business data.

CategoryOther
AuthenticationAPI key
SetupSelf-service

Getting started with the OpenWeather connector

Section titled “Getting started with the OpenWeather connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your OpenWeather account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key
Your OpenWeather API key.

|

When you set up the connector, you provide:

Field Description
Language
Language for weather description output. See supported languages for the full list.

| | Latitude |

Latitude of the location to retrieve weather data for, as a decimal between -90 and 90.

| | Longitude |

Longitude of the location to retrieve weather data for, as a decimal between -180 and 180.

| | Units |

Units of measurement for temperature and wind speed. Standard uses Kelvin, metric uses Celsius, and imperial uses Fahrenheit.

|

Tables and columns synced from OpenWeather

Section titled “Tables and columns synced from OpenWeather”

Kaivo syncs 1 table from OpenWeather into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

onecall (20 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
current__clouds FLOAT64 Cloudiness percentage
current__dew_point FLOAT64 Dew point temperature
current__dt FLOAT64 Time of the data forecasted
current__feels_like FLOAT64 Apparent (feels like) temperature
current__humidity FLOAT64 Humidity percentage
current__pressure FLOAT64 Atmospheric pressure on the sea level
current__rain___1h FLOAT64 Rain volume for the last hour
current__sunrise FLOAT64 Sunrise time
current__sunset FLOAT64 Sunset time
current__temp FLOAT64 Temperature
current__uvi FLOAT64 UV index
current__visibility FLOAT64 Visibility distance
current__wind_deg FLOAT64 Wind direction in degrees
current__wind_speed FLOAT64 Wind speed in meters per second
lat FLOAT64 Latitude of the requested location
lon FLOAT64 Longitude of the requested location
timezone STRING Time zone name for the requested location
timezone_offset FLOAT64 Time offset in seconds from UTC
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value JSON
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where OpenWeather supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for OpenWeather?

Section titled “How long does the initial sync take for OpenWeather?”

It depends on how much history is in your OpenWeather account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when OpenWeather’s schema changes?

Section titled “What happens when OpenWeather’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in OpenWeather, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in OpenWeather instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the OpenWeather connector in Kaivo and all of its synced data is deleted with it.

Use the onecall daily and hourly data to track conditions over time by location.

Join weather with your sales data to see how conditions affect demand.

Use alerts to record severe-weather events for your locations.

Report on conditions across your locations in one place.

Use OpenWeather data in your AI and BI tools

Section titled “Use OpenWeather data in your AI and BI tools”

Once OpenWeather data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with OpenWeather data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for OpenWeather connector pricing and plan details.