Skip to content
CRM ⇄ Business productivity

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

Keep Salesforce 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 Salesforce and Wrike

Sync what happens in Wrike with the customer records in Salesforce, 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 Comments, Timelogs, Contacts, Workflows in Wrike to Custom Objects, Accounts, Contacts, Leads in Salesforce with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Salesforce, and CRM data flows the other way wherever Wrike can store and use it.

Common use cases

  • 01 Write closed deals or new orders from a CRM or ERP into Wrike Tasks to launch delivery, onboarding, or fulfillment projects automatically.
  • 02 Mirror Folders, Projects, and Timelogs into a warehouse for cross-team reporting on status, timelines, and logged hours without manual exports.
  • 03 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 04 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.

Common sync patterns

Where Wrike can store CRM context: fields kept current

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

Where Wrike handles support or shared inboxes

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

Where Wrike supplies contact or company data

Enriched fields land directly on records in Salesforce, and refreshes keep them from going stale.

What you can sync between Salesforce 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.

Salesforce objects Wrike objects How this pairing syncs
Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. 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.
Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. 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. Custom Objects is specific to Salesforce and Tasks to Wrike — each maps to any object or custom field on the other side.
Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. 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. Accounts is specific to Salesforce and Folders & Projects to Wrike — each maps to any object or custom field on the other side.
Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. 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. Leads is specific to Salesforce and Custom Fields to Wrike — each maps to any object or custom field on the other side.
Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Opportunities is specific to Salesforce and Comments to Wrike — each maps to any object or custom field on the other side.
Cases Support records; synced with help desk tools or internal databases for escalation workflows. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Cases is specific to Salesforce and Timelogs to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Salesforce 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.

Salesforce Wrike Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

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

Rate-limit considerations

  • Salesforce: Daily API request allocations vary by edition and license count.
  • 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 Salesforce ⇄ Wrike

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce 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 Salesforce or Wrike record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Salesforce and Wrike connectors work

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide

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

    Choose tables

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

Salesforce 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 542 integrations available for Salesforce and Wrike.

Popular · 8 of 542
All Salesforce 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