kimo
Files

Google Sheets + Kimo

Targets, budgets and mapping tables from Google Sheets, refreshed every 15 minutes and joinable with anything.

Auth
OAuth 2.0
Sync
Every 15 min
Setup
≈ 2 min
Request access

Live demo workspace with fictional data · no signup, no credentials needed

kimo / connectors / sheetsSyncing
Sync logevery 15 min
  • Succeeded:files+1,306 rowsnow
  • Succeeded:sheet_rows+525 rows2m ago
  • Succeeded:files+468 rows4m ago
  • Succeeded:sheet_rows+2,087 rows6m ago
Rows synced · 30 days
126.4M
Workspaces
24%
Simulated demo data
What you can do

What teams build with Google Sheets

Google Sheets on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.

01

Targets in a sheet

Keep monthly goals in Sheets and show progress against them in every dashboard.

Plan vs. actual
02

Living mapping tables

UTM-to-channel or SKU-to-category mappings your team edits without filing a ticket.

Lookup join
03

Fresh every 15 minutes

Edits flow into models automatically. No re-upload, no broken links.

Auto-refresh
Objects & tables

Exactly what gets synced

Kimo maps Google Sheets into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.

2 tables · 9 fields

sheet_rows

Full refresh≈ 58,400,000 rows
FieldTypeNotes
row_ididPrimary key
col_astring
col_bstring
col_cstring
updated_attimestampIncremental cursor
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model

From raw Google Sheets tables to a certified metric

A starter model Kimo suggests the moment Google Sheets is connected. Every join is editable.

Google Sheets · Targets vs. actuals

Monthly targets from a sheet joined with live revenue and signups.

Template
  • Google Sheets
    sheet_rows
  • Stripe
    subscriptions
  • PostgreSQL
    users
Model
month · team
Measuresactualsignups
Actual revenue · last 30 days
$47.7K-4.6% wk/wk

Fictional data · hover the chart for daily values

Setup

Connect Google Sheets in 2 min

No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.

  1. 1

    Click “Connect Google Sheets”

    You are redirected to Google Sheets to sign in. Kimo never sees your password.

  2. 2

    Approve read-only scopes

    Kimo requests the narrowest scopes available. You can revoke access at any time.

  3. 3

    Pick spreadsheets

    Choose which spreadsheets to sync. Add more later without reconnecting.

  4. 4

    First sync and schema mapping

    Kimo backfills history, maps sheet_rows and suggests joins with your other sources.

Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.

Connect Google Sheets
Step 2 of 3 · Kimo demo workspace

Kimo wants read-only access to your Google Sheets account

  • spreadsheets.readonlyread
  • drive.metadata.readonlyread
Spreadsheets
  • FY27 targets
  • UTM → channel mapping
  • Territories
Read-only access
Illustration only · placeholder values, never real secrets
FAQ

Google Sheets questions, answered

By default Kimo syncs Google Sheets every 15 min. You can change the schedule per table, or trigger a sync manually from the connector page.

Google Sheets · OAuth 2.0 · Every 15 min

See your Google Sheets data in Kimo in 2 min.

Try it on the live demo workspace first, then connect your own account when you are ready.

Request access