Skip to content
CRM ⇄ Business productivity

Microsoft Dynamics 365 Sales to Wrike integration — real-time, two-way sync

Keep Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales and Wrike

Sync what happens in Wrike with the customer records in Microsoft Dynamics 365 Sales, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Wrike holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Spaces, Tasks, Folders & Projects, Custom Fields in Wrike to Contacts, Leads, Opportunities, Quotes in Microsoft Dynamics 365 Sales with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Microsoft Dynamics 365 Sales, and CRM data flows the other way wherever Wrike can store and use it.

Common use cases

  • 01 Sync Comments and status changes from Wrike into a database so downstream dashboards and tools react to project progress in near real time.
  • 02 Two-way sync of Tasks and their Custom Fields between a Wrike project and Postgres so ops teams work in SQL while project owners stay in Wrike.
  • 03 Feed BI models with continuously updated CRM data instead of scheduled exports.
  • 04 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.

Common sync patterns

Where Wrike handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Microsoft Dynamics 365 Sales, so sales sees open issues before the next call.

Where Wrike supplies contact or company data

Enriched fields land directly on records in Microsoft Dynamics 365 Sales, and refreshes keep them from going stale.

Where Wrike can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Microsoft Dynamics 365 Sales sync into Wrike, so people working there have the context without switching tools.

What you can sync between Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales objects Wrike objects How this pairing syncs
Contacts Person records linked to accounts; synced with marketing and support systems. Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Invoices is specific to Microsoft Dynamics 365 Sales and Comments to Wrike — each maps to any object or custom field on the other side.
Activities Emails, calls, appointments, and tasks; read out for activity analytics. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Activities is specific to Microsoft Dynamics 365 Sales and Timelogs to Wrike — each maps to any object or custom field on the other side.
Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. Custom Tables is specific to Microsoft Dynamics 365 Sales and Workflows to Wrike — each maps to any object or custom field on the other side.
Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Accounts is specific to Microsoft Dynamics 365 Sales and Spaces to Wrike — each maps to any object or custom field on the other side.
Leads Prospect records; written in from enrichment or web forms, read out on qualification. 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. Leads is specific to Microsoft Dynamics 365 Sales and Tasks to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales Wrike Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

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

Wrike Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
  • 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 Microsoft Dynamics 365 Sales ⇄ Wrike

Connect Microsoft Dynamics 365 Sales and Wrike for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–Wrike connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics 365 Sales or Wrike instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales or Wrike record.

Observability

Monitoring

Track your Microsoft Dynamics 365 Sales ⇄ Wrike sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 Sales and Wrike.

How the Microsoft Dynamics 365 Sales and Wrike connectors work

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.

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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales 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
    Microsoft Dynamics 365 Sales connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics 365 Sales 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 · Microsoft Dynamics 365 Sales ⇄ 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
    Microsoft Dynamics 365 Sales Wrike
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales and Wrike.

Popular · 8 of 436
All Microsoft Dynamics 365 Sales 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