Codat to Looker Studio Integration

How Datrise loads Codat into Looker Studio

Datrise syncs Codat's companies, accounts, invoices, bills, journal entries, and payments into Looker Studio as warehouse tables Looker Studio connects to. Flexible or custom fields land in flattened columns for chart fields, and timestamps such as created, updated, and status changes are typed as date dimension columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned tables to keep extract refresh fast. Looker Studio performs best on pre-aggregated tables, so Datrise lands tidy, report-shaped tables rather than raw API payloads.

Ideal for free, shareable dashboards on Google data sources.

Endpoints

Codat: Unified API for accounting and banking data.

Looker Studio: Google self-service dashboards and reporting (formerly Data Studio).

How Codat entities map to Looker Studio

Codat entity	Looker Studio object	Notes
companies	`codat_companies`	id PK · custom fields → flattened columns for chart fields
accounts	`codat_accounts`	id PK · linked to codat_companies
invoices	`codat_invoices`	id PK · linked to codat_companies
bills	`codat_bills`	id PK · linked to codat_companies

FAQ

How does Datrise handle Codat's custom fields in Looker Studio?

Flexible values are stored as flattened columns for chart fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker Studio types.

How does the Codat to Looker Studio sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Codat to Looker Studio the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.