Real-time
Two-way sync
Changes in Close or Wrike instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Close to Wrike integration — real-time, two-way sync
Keep Close 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 Close and Wrike
Sync what happens in Wrike with the customer records in Close, 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 Custom Fields, Comments, Timelogs, Contacts in Wrike to Smart Views, Leads, Contacts, Opportunities in Close with bi-directional, real-time sync. Activity and record changes in Wrike update the matching contact or account in Close, and CRM data flows the other way wherever Wrike can store and use it.
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 call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
- 04 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
Common sync patterns
Where Wrike can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Close 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 Close, so sales sees open issues before the next call.
Where Wrike supplies contact or company data
Enriched fields land directly on records in Close, and refreshes keep them from going stale.
What you can sync between Close 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.
| Close objects | Wrike objects | How this pairing syncs | |
|---|---|---|---|
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | 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. | |
| Tasks Follow-up items assigned to users; synced for workload and SLA 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. | Opportunities is specific to Close and Workflows to Wrike — each maps to any object or custom field on the other side. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. | Activities is specific to Close and Spaces to Wrike — each maps to any object or custom field on the other side. | |
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | 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. | Custom Activities is specific to Close and Folders & Projects to Wrike — each maps to any object or custom field on the other side. |
How changes propagate between Close 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.
Close Wrike Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.
Wrike Close 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 Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- 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 Close ⇄ Wrike
Connect Close and Wrike for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Wrike connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close 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 Close or Wrike record.
Observability
Monitoring
Track your Close ⇄ Wrike sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Wrike.
How the Close and Wrike connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
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 Close 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 Close 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.
Close
connected
Wrike
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close 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 · Close ⇄ 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.
Close WrikeCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Wrike integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Wrike: authenticate both systems, choose the objects to sync (such as Close's Contacts and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Close 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 Close sync into Wrike, so people working there have the context without switching tools.
-
Close: REST API. Authentication: API key (sent via HTTP Basic auth). 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: Rate limiting is roughly 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding it — or hitting Wrike's internal overload protection — returns HTTP 429, best handled with exponential backoff. Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. Stacksync's field mapping accounts for these differences between Close 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 Close and Wrike records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Wrike connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Wrike integration in-house.
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 534 integrations available for Close and Wrike.
Popular · 8 of 534
-
Close ⇄ Gatekeeper -
Close ⇄ Monday -
Close ⇄ Notion -
Close ⇄ Quip -
Wrike ⇄ DealCloud -
Wrike ⇄ Chorusai -
Wrike ⇄ Clari -
Wrike ⇄ Dun And Bradstreet
No integrations match .
