Real-time
Two-way sync
Changes in Twenty CRM or Wrike instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Twenty CRM to Wrike integration — real-time, two-way sync
Keep Twenty CRM 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 Twenty CRM and Wrike
Sync what happens in Wrike with the customer records in Twenty CRM, 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 Workflows, Spaces, Tasks, Folders & Projects in Wrike to Custom Objects, Attachments, Workspace Members, People in Twenty CRM with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Twenty CRM, and CRM data flows the other way wherever Wrike can store and use it.
Common use cases
- 01 Push support tickets or intake requests from an operational database into Wrike Tasks, then read completion and status Custom Fields back when work finishes.
- 02 Sync Comments and status changes from Wrike into a database so downstream dashboards and tools react to project progress in near real time.
- 03 Push product usage or billing data from a warehouse into Twenty custom fields to give reps account context.
- 04 Sync Opportunities into a finance system to keep revenue forecasts current.
Common sync patterns
Where Wrike supplies contact or company data
Enriched fields land directly on records in Twenty CRM, and refreshes keep them from going stale.
Where Wrike can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Twenty CRM 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 Twenty CRM, so sales sees open issues before the next call.
What you can sync between Twenty CRM 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.
| Twenty CRM objects | Wrike objects | How this pairing syncs | |
|---|---|---|---|
| Tasks To-dos linked to people, companies, or deals. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Attachments Files linked to records. | Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. | Attachments is specific to Twenty CRM and Comments to Wrike — each maps to any object or custom field on the other side. | |
| Workspace Members User accounts used for record ownership and assignment mapping. | Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. | Workspace Members is specific to Twenty CRM and Timelogs to Wrike — each maps to any object or custom field on the other side. | |
| People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. | People is specific to Twenty CRM and Contacts to Wrike — each maps to any object or custom field on the other side. | |
| Companies Account-level records that group people and opportunities. | Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. | Companies is specific to Twenty CRM and Workflows to Wrike — each maps to any object or custom field on the other side. | |
| Opportunities Deal records tracked through pipeline stages, synced for forecasting. | Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. | Opportunities is specific to Twenty CRM and Spaces to Wrike — each maps to any object or custom field on the other side. |
How changes propagate between Twenty CRM 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.
Twenty CRM Wrike Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.
Wrike Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
- 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 Twenty CRM ⇄ Wrike
Connect Twenty CRM and Wrike for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Twenty CRM–Wrike connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Twenty CRM 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 Twenty CRM or Wrike record.
Observability
Monitoring
Track your Twenty CRM ⇄ Wrike sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Twenty CRM and Wrike.
How the Twenty CRM and Wrike connectors work
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
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
How it works
How to connect Twenty CRM 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.
- 01
Connect your apps
Authenticate Twenty CRM 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.
Twenty CRM
connected
Wrike
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Twenty CRM 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.
objects · Twenty CRM ⇄ WrikeCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Twenty CRM WrikeCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Twenty CRM and Wrike integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Twenty CRM and Wrike: authenticate both systems, choose the objects to sync (such as Twenty CRM's Tasks and Attachments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Twenty CRM and Wrike records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Twenty CRM and Wrike connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Twenty CRM–Wrike integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Twenty CRM and Wrike. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. On Wrike: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Wrike side: Workflows, Spaces, Tasks, Folders & Projects, plus custom fields where Wrike exposes them. On the Twenty CRM side: Custom Objects, Attachments, Workspace Members, People. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 440 integrations available for Twenty CRM and Wrike.
Popular · 7 of 440
-
Twenty CRM ⇄ GitHub -
Twenty CRM ⇄ Braze -
Twenty CRM ⇄ ConnectWise -
Wrike ⇄ DealCloud -
Wrike ⇄ Chorusai -
Wrike ⇄ Clari -
Wrike ⇄ Dun And Bradstreet
No integrations match .
