Real-time
Two-way sync
Changes in Braze or Wrike instantly reflect in both systems. No stale data, no manual imports.
Business productivity
Braze to Wrike integration — real-time, two-way sync
Keep Braze 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 Braze and Wrike
Stop re-entering the same information in Braze and Wrike: Stacksync keeps the records they share consistent in real time, in both directions.
Two tools in the daily stack often hold overlapping information: the same people, the same companies, or the same pieces of work, described twice. The tools do different jobs, so consolidating is not the answer; the overlap just needs to stop drifting.
Stacksync syncs Segments, Campaigns, Canvases, Subscription Groups in Braze with Folders & Projects, Custom Fields, Comments, Timelogs in Wrike in real time. You choose which records overlap, map the fields that should match, and pick a direction or let changes flow both ways. From then on, an update made in either tool is reflected in the other within seconds, without exports or copy-paste.
Because the sync is field-level, each tool keeps its own extras; only the shared data is held in agreement.
Common use cases
- 01 Sync CRM and billing attributes onto Braze user profiles so lifecycle campaigns target accurate plan and status data.
- 02 Push product usage events from a database or warehouse into Braze to trigger onboarding and retention journeys.
- 03 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.
- 04 Write closed deals or new orders from a CRM or ERP into Wrike Tasks to launch delivery, onboarding, or fulfillment projects automatically.
Common sync patterns
Where both tools track people or companies: one consistent record
Contact and company details corrected in either tool update the other, so nobody works from the old version.
Where one tool produces events: mirror them in the other
Payments, replies, messages, or tickets created in one tool can create or update matching records in the other, keeping context in one place.
Where Wrike is where the team documents or plans: keep its data fed
Information that originates in Braze stays current in Wrike instead of going stale after a one-time paste.
What you can sync between Braze 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.
| Braze objects | Wrike objects | How this pairing syncs | |
|---|---|---|---|
| Custom Attributes Profile fields written from CRMs, warehouses, and product databases to drive personalization. | Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. | Custom Attributes is specific to Braze and Contacts to Wrike — each maps to any object or custom field on the other side. | |
| Custom Events Behavioral events pushed into Braze to trigger campaigns and Canvases. | Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. | Custom Events is specific to Braze and Workflows to Wrike — each maps to any object or custom field on the other side. | |
| Purchases Transaction records logged against profiles for revenue-based targeting. | Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. | Purchases is specific to Braze and Spaces to Wrike — each maps to any object or custom field on the other side. | |
| Segments Audience definitions read for membership export and campaign targeting. | 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. | Segments is specific to Braze and Tasks to Wrike — each maps to any object or custom field on the other side. | |
| Campaigns Message sends whose metadata and analytics are read for reporting. | 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. | Campaigns is specific to Braze and Folders & Projects to Wrike — each maps to any object or custom field on the other side. | |
| Canvases Multi-step journeys; entry and performance data is read for lifecycle analysis. | 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. | Canvases is specific to Braze and Custom Fields to Wrike — each maps to any object or custom field on the other side. |
How changes propagate between Braze 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.
Braze Wrike Interval-based propagation
DetectionStacksync polls Braze for changes on an incremental schedule, reading only records changed since the previous pass. Braze Currents streams engagement events outward.
DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.
Wrike Braze 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 Braze through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Braze: Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request.
- 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 Braze ⇄ Wrike
Connect Braze and Wrike for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Wrike connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Braze 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 Braze or Wrike record.
Observability
Monitoring
Track your Braze ⇄ Wrike sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Braze and Wrike.
How the Braze and Wrike connectors work
Braze
- Integration surface
- REST API
- Authentication
- REST API keys scoped to specific endpoints, issued per workspace
- Change detection
- Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling
- Capabilities
- read · write
- Rate limits
- Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request
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 Braze 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 Braze 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.
Braze
connected
Wrike
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Braze 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 · Braze ⇄ 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.
Braze WrikeCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Braze and Wrike integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Braze and Wrike: authenticate both systems, choose the objects to sync (such as Braze's Custom Attributes and Custom Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Braze and Wrike connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Braze–Wrike integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Braze and Wrike. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Braze: Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling. 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 Braze side: Segments, Campaigns, Canvases, Subscription Groups, plus custom fields where Braze exposes them. On the Wrike side: Folders & Projects, Custom Fields, Comments, Timelogs. 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.
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 504 integrations available for Braze and Wrike.
Popular · 6 of 504
-
Braze ⇄ Microsoft Teams -
Braze ⇄ Resend -
Wrike ⇄ Monday -
Wrike ⇄ Notion -
Wrike ⇄ Quip -
Wrike ⇄ Smartsheet
No integrations match .
