You opened Looker Studio, clicked Add data, typed Airtable into the connector search, and nothing came back that Google built. That is the correct result. Google renamed Data Studio to Looker Studio in 2022, and under either name it has never shipped an Airtable connector.
So every working route puts something in the middle. There are three of them, they cost different amounts, and they differ in one way that decides whether your dashboard is trusted: how old the numbers on it are allowed to get.
The three routes
| Route | What sits in the middle | Cost | How fresh |
|---|---|---|---|
| Partner connector | A third-party connector | Paid, per connector vendor | The vendor's refresh, plus Looker's cache |
| Through Google Sheets | A synced spreadsheet | Free connector, paid sync tool | Your sync interval, plus Looker's cache |
| Through BigQuery | A warehouse and a pipeline | BigQuery storage and query costs | Your pipeline's schedule, plus the cache |
Every one of them has "plus Looker's cache" in the last column, and that is the part almost nobody accounts for.
The two clocks
A dashboard reading Airtable data is never as current as the fastest link in the chain. It is as current as the sum of two separate waits.
Clock one is the trip out of Airtable. However your data reaches Looker Studio, something is pulling it on a schedule. A partner connector refreshes on its plan's interval. A synced spreadsheet refreshes on the sync tool's interval. A warehouse pipeline runs on its own cron.
Clock two is Looker Studio's own cache. Looker Studio stores query results in memory and serves them again rather than re-querying the source. For a Google Sheets data source the freshness setting offers 15 minutes, 1 hour, 4 hours or 12 hours, and it defaults to 15 minutes. Until that window expires, the report shows what it last fetched, however new the underlying data is.
Add them. A source refreshing hourly behind a cache set to 4 hours produces a dashboard that can be five hours behind, and the setting people go looking for when they notice is almost always the first clock.
Viewers cannot clear the cache themselves unless the report editor turns on Viewer data refresh in report settings. Once it is on, a viewer can right-click a chart and choose Refresh data, with a one minute cooldown between attempts. Turning that on is the cheapest fix for "the dashboard looks wrong" complaints, because it hands the person looking at it a way to check.
Route 1: a partner connector
Several vendors publish Airtable connectors in Looker Studio's partner gallery, including Coupler.io, Jivrus, Windsor.ai, Skyvia and Improvado. These appear inside Looker Studio's own Add data screen and connect to Airtable directly, with no spreadsheet in between.
This is the shortest chain, and it is the one to pick when the dashboard is the only thing you are building. The trade is that you are buying a connector subscription per vendor, and the refresh interval is set by whichever plan you land on rather than by you. Coupler.io, to take the one with published prices, schedules daily on its $32 and $132 plans and does not reach hourly until $259 a month. Coupler.io pricing has the full ladder.
Check the row limits before you commit. Connector plans are usually metered on rows per run, and an Airtable base grows past those ceilings quietly.
Route 2: through Google Sheets
Looker Studio's Google Sheets connector is built by Google, free, and already in the connector list. So syncing Airtable into a spreadsheet and pointing Looker Studio at that spreadsheet turns an unsupported source into a supported one.
Since this is our own tool, plainly: Airtable to Sheets is a Google Sheets add-on that keeps a tab current from an Airtable base, table or view, $9 to $39 a month flat for the whole account with no per-seat charge. Scheduled sync runs every 3 hours, because it runs on Apps Script and Google caps scheduled triggers in Workspace add-ons at roughly one run an hour. Set against a Looker Studio cache of 4 hours, that first clock is no longer the thing holding your dashboard back. Set against a cache of 15 minutes, it is. Our numbers are on the pricing page.
Two things make this route better than it sounds.
The spreadsheet is a place to fix data before the chart sees it. Looker Studio calculated fields are limited, and Airtable columns rarely arrive shaped the way a chart wants them. A second tab holding formulas, pointing at the synced tab, gives you somewhere to reshape before Looker Studio reads anything. The two-tab pattern is that structure, and it matters more here than in a plain report, because a Looker Studio data source breaks loudly when columns move.
A spreadsheet is legible when the dashboard disagrees with the base. With a connector, a wrong number has two places to hide. With a sheet in the middle, you open the sheet and see immediately which side of the chain is wrong.
The trade is one more moving part and one more clock.