Two-way sync
Changes in Intercom or Wrike instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom 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.
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 Contacts, Workflows, Spaces, Tasks in Wrike to Tags, Segments, Admins & Teams, Articles in Intercom with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Intercom, and CRM data flows the other way wherever Wrike can store and use it.
Owner, lifecycle stage, or account details from Intercom sync into Wrike, so people working there have the context without switching tools.
Tickets and conversations attach to the right contact and account in Intercom, so sales sees open issues before the next call.
Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.
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.
| Intercom objects | Wrike objects | How this pairing syncs | |
|---|---|---|---|
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | 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. | |
| Tickets Structured ticket records track issues alongside conversational threads. | 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. | Tickets is specific to Intercom and Custom Fields to Wrike — each maps to any object or custom field on the other side. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. | Data Events is specific to Intercom and Comments to Wrike — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. | Custom Data Attributes is specific to Intercom and Timelogs to Wrike — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. | Tags is specific to Intercom and Workflows to Wrike — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. | Segments is specific to Intercom and Spaces to Wrike — each maps to any object or custom field on the other side. |
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.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.
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 Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Wrike connection.
Changes in Intercom or Wrike instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Wrike data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Wrike record.
Track your Intercom ⇄ Wrike sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Wrike.
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.
Authenticate Intercom 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.
Pick the Intercom 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Wrike: authenticate both systems, choose the objects to sync (such as Intercom's Contacts and Tickets), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Intercom and Wrike: Where Wrike can store CRM context: fields kept current; Where Wrike handles support or shared inboxes; Where Wrike supplies contact or company data. Owner, lifecycle stage, or account details from Intercom sync into Wrike, so people working there have the context without switching tools.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Wrike: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Wrike: The API is REST/JSON (v4) and endpoint URLs must be built from the host returned by the OAuth token call — for example www.wrike.com/api/v4 or app-eu.wrike.com/api/v4 for EU data-center accounts. Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Stacksync's field mapping accounts for these differences between Intercom and Wrike without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Intercom and Wrike records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 518 integrations available for Intercom and Wrike.