Source connector

Wrike connector

Wrike integration for databases, warehouses and BI tools

Project and task management with custom workflows. Datrise captures Wrike entities such as tasks, folders, projects, timelogs, custom fields and task statuses, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Wrike API v4 (REST) authenticates with OAuth 2.0, incremental runs key on updatedDate range filter (InstantRange: start/end in yyyy-MM-dd'T'HH:mm:ss'Z' format) on the Get Tasks endpoint, and Wrike caps calls at 400 requests per minute per user; 5,000 requests per minute per IP address.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `wrike_tasks`) with a schema derived from the Wrike API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Wrike pipeline page, and join the waitlist to get the Wrike connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Wrike data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
tasks	wrike_tasks	Upsert by primary key, incremental on updated-at
folders	wrike_folders	Upsert by primary key, incremental on updated-at
projects	wrike_projects	Upsert by primary key, incremental on updated-at
timelogs	wrike_timelogs	Upsert by primary key, incremental on updated-at
custom fields	wrike_custom_fields	Upsert by primary key, incremental on updated-at
task statuses	wrike_task_statuses	Upsert by primary key, incremental on updated-at

Wrike API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Wrike API v4 (REST)
Authentication	OAuth 2.0 — OAuth 2.0; every request needs an Authorization: Bearer header (a legacy access_token query parameter is also accepted).
Pagination	token — pageSize query param, max 1,000 items per page on endpoints like Get Tasks; continue with the returned nextPageToken, which applies an offset for the following request.
Rate limit	400 requests per minute per user; 5,000 requests per minute per IP address
Incremental cursor	updatedDate range filter (InstantRange: start/end in yyyy-MM-dd'T'HH:mm:ss'Z' format) on the Get Tasks endpoint — updatedDate range filtering is documented on Tasks; other resource types don't necessarily expose the same filter.
Webhooks	Yes — Wrike Webhooks (folder, account or space scoped; task/folder/project/comment/attachment change events)
Bulk export	Yes — Datahub API (raw analytical data export) and native BI export to Tableau, Power BI or Looker
Deletes detectable	Yes — task.deleted webhook event, or the scope field on Get Tasks returning RbTask for items sitting in the account's Recycle Bin.

Official API reference

What bites when replicating Wrike

The per-user throttle is only 400 requests/minute (versus 5,000/min per IP); the first 400 are served and the rest return 429 with error too_many_requests, so a single shared token can throttle an entire integration.
Get Tasks caps pageSize at 1,000; without an explicit pageSize/nextPageToken, some list endpoints just return the first 1,000 records with no continuation.
Deleted tasks aren't purged — they move to a Recycle Bin scope (scope: RbTask in the response), so fetching a 'deleted' task by ID can still succeed unless you inspect scope.
Webhook deliveries are skipped for changes made via mass actions such as bulk CSV import; importing 100+ tasks at once can update the account with zero webhook events fired.

Compare this against every other documented API

Popular destinations for Wrike

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Wrike connector FAQ

What Wrike data does the connector extract?: 6 objects: tasks, folders, projects, timelogs, custom fields and task statuses. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Wrike integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Wrike data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Wrike → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Wrike pipeline with guided onboarding

Join the waitlist to get priority access for Wrike integrations with guided setup, schema-aware mapping, and production-grade incremental sync.