Wrike to Looker Studio Integration

How Datrise loads Wrike into Looker Studio

Datrise syncs Wrike's tasks, folders, projects, timelogs, custom fields, and task statuses 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

Wrike: Project and task management with custom workflows.

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

How Wrike entities map to Looker Studio

Wrike entity	Looker Studio object	Notes
tasks	`wrike_tasks`	id PK · custom fields → flattened columns for chart fields
folders	`wrike_folders`	id PK · linked to wrike_tasks
projects	`wrike_projects`	id PK · linked to wrike_tasks
timelogs	`wrike_timelogs`	id PK · linked to wrike_tasks

FAQ

How does Datrise handle Wrike'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 Wrike to Looker Studio sync stay up to date?

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

Related pipelines

Early access

Connect Wrike 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.