Real-time
Two-way sync
Changes in Box or Wrike instantly reflect in both systems. No stale data, no manual imports.
Storage ⇄ Business productivity
Box to Wrike integration — real-time, two-way sync
Keep Box 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 Box and Wrike
Land the records and documents that build up in Wrike into Box as they are created, and surface Box's file details on the Wrike records that point to them, without an export job to maintain.
Wrike and Box hold different kinds of data. Wrike carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Box holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Wrike produces has to be kept somewhere durable, and many of the files Box stores are the very documents Wrike's records point to.
Stacksync syncs Contacts, Workflows, Spaces, Tasks in Wrike with Collaborations, Users, Groups, Tasks in Box in real time. Records and attachments created in Wrike are written into Box as objects or files within seconds of being created. In the other direction, the metadata Box keeps about those files — name, location, owner, modified date — flows back onto the matching record in Wrike, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.
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 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
- 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.
Common sync patterns
Where Wrike generates attachments: keep the files in Box
Documents attached to records in Wrike land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.
Where Box holds the source documents: file details on the record
A file's name, location, owner, and modified date from Box sync onto the matching record in Wrike, so whoever is working there sees the current version without switching tools.
A copy that outlives the tool
A continuously synced copy in Box preserves records and documents even as they age out of Wrike or get changed inside it, so history stays intact and reachable.
What you can sync between Box 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.
| Box objects | Wrike objects | How this pairing syncs | |
|---|---|---|---|
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | 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. | |
| Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. | Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. | Folders is specific to Box and Contacts to Wrike — each maps to any object or custom field on the other side. | |
| Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. | Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. | Metadata is specific to Box and Workflows to Wrike — each maps to any object or custom field on the other side. | |
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. | Collaborations is specific to Box and Spaces to Wrike — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | 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. | Users is specific to Box and Folders & Projects to Wrike — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | 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. | Groups is specific to Box and Custom Fields to Wrike — each maps to any object or custom field on the other side. |
How changes propagate between Box 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.
Box Wrike Sub-second propagation
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.
Wrike Box 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 Box through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
- 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 Box ⇄ Wrike
Connect Box and Wrike for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Wrike connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Box 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 Box or Wrike record.
Observability
Monitoring
Track your Box ⇄ Wrike sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Box and Wrike.
How the Box and Wrike connectors work
Box
- Integration surface
- REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
- Authentication
- OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
- Change detection
- V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
- Capabilities
- read · write · webhooks
- Rate limits
- Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
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 Box 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 Box 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.
Box
connected
Wrike
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Box 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 · Box ⇄ 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.
Box WrikeCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Box and Wrike integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Box and Wrike: authenticate both systems, choose the objects to sync (such as Box's Tasks and Folders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Box and Wrike. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Box: V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed. 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: Contacts, Workflows, Spaces, Tasks, plus custom fields where Wrike exposes them. On the Box side: Collaborations, Users, Groups, Tasks. Stacksync auto-detects both schemas and converts types between the two systems.
-
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 Box and Wrike: Where Wrike generates attachments: keep the files in Box; Where Box holds the source documents: file details on the record; A copy that outlives the tool. Documents attached to records in Wrike land in the storage system automatically, with the source record holding a link back, so files live in one governed place instead of inside the tool.
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
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 502 integrations available for Box and Wrike.
Popular · 7 of 502
-
Box ⇄ Ironclad -
Box ⇄ Servicemax -
Box ⇄ Adobe Sign -
Box ⇄ Asana -
Wrike ⇄ Egnyte -
Wrike ⇄ Amazon S3 -
Wrike ⇄ Sharepoint
No integrations match .
