Skip to content
Database ⇄ Business productivity

Reltio to Wrike integration — real-time, two-way sync

Keep Reltio and Wrike in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Reltio and Wrike

Mirror Wrike's data into Reltio so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Wrike through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Reltio.

Stacksync mirrors Comments, Timelogs, Contacts, Workflows from Wrike into Entities, Relations, Crosswalks, Interactions in Reltio and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Wrike, so the tool and the database never disagree.

Common use cases

  • 01 Mirror Folders, Projects, and Timelogs into a warehouse for cross-team reporting on status, timelines, and logged hours without manual exports.
  • 02 Push support tickets or intake requests from an operational database into Wrike Tasks, then read completion and status Custom Fields back when work finishes.
  • 03 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 04 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.

Common sync patterns

Read Wrike with a query

Records from Wrike are ordinary rows in Reltio; join them, index them, and use them in application logic without touching the vendor API.

Automate Wrike from your codebase

Write to the synced tables in Reltio and Stacksync propagates the change into Wrike, replacing custom integration code.

React to changes as they happen

Updates in Wrike arrive as row changes in Reltio, so triggers, jobs, and services can respond in near real time.

What you can sync between Reltio and Wrike

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Reltio objects Wrike objects How this pairing syncs
Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Crosswalks is specific to Reltio and Contacts to Wrike — each maps to any object or custom field on the other side.
Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. Interactions is specific to Reltio and Workflows to Wrike — each maps to any object or custom field on the other side.
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Matches (Potential Matches) is specific to Reltio and Spaces to Wrike — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Tasks The primary unit of work and main record; created, updated, completed, and deleted via the REST v4 API and synced two-way. Subtasks are Tasks linked by superTask/subTask references. Activity Log is specific to Reltio and Tasks to Wrike — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Folders & Projects The container hierarchy: Folders group Tasks, and Projects add dates, an owner, and a status. Each maps to a synced table scope, and its structure defines what a sync covers. Data Change Requests (DCR) is specific to Reltio and Folders & Projects to Wrike — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Custom Fields Typed fields (Text, Numeric, Date, DropDown, Contacts, Checkbox) defined at account or space level; mapped to database columns, with values written by field ID. Reference Data (RDM) is specific to Reltio and Custom Fields to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Reltio and Wrike

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Reltio Wrike Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.

Wrike Reltio Sub-second propagation

DetectionWrike notifies Stacksync of record changes through webhook events. Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event.

DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • Wrike: Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff.
What ships with Reltio ⇄ Wrike

Connect Reltio and Wrike for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Wrike connection.

Real-time

Two-way sync

Changes in Reltio or Wrike instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or Wrike data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Reltio or Wrike record.

Observability

Monitoring

Track your Reltio ⇄ Wrike sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and Wrike.

How the Reltio and Wrike connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

Wrike

Integration surface
REST API v4 (JSON), single account endpoint such as www.wrike.com/api/v4; the data-center host (US or EU) comes from the OAuth token response, plus REST-managed Webhooks
Authentication
OAuth 2.0 for multi-user apps (Authorization header carrying access_token and requested scopes), and a legacy Permanent Access Token for single-account and testing use
Change detection
Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event filtering and custom payload fields; polling the task updatedDate is the fallback
Capabilities
read · write · webhooks
Rate limits
Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff
Wrike setup guide
How it works

How to connect Reltio to Wrike — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Reltio and Wrike with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Reltio connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio and Wrike objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Reltio ⇄ Wrike
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Reltio Wrike
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Reltio and Wrike integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 436 integrations available for Reltio and Wrike.

Popular · 8 of 436
All Reltio integrations All Wrike integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own