Real-time
Two-way sync
Changes in Braze or Clari instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ CRM
Braze to Clari integration — real-time, two-way sync
Keep Braze and Clari 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 Clari
Sync what happens in Braze with the customer records in Clari, 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 Braze 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 Campaigns, Canvases, Subscription Groups, Content Blocks in Braze to Account field extensions, Opportunity field extensions, Audit Events, Forecast in Clari with bi-directional, real-time sync. Activity and record changes in Braze update the matching contact or account in Clari, and CRM data flows the other way wherever Braze can store and use it.
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 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.
- 04 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
Common sync patterns
Where Braze supplies contact or company data
Enriched fields land directly on records in Clari, and refreshes keep them from going stale.
Where Braze processes payments
Charges, refunds, and subscription changes appear on the account in Clari, so revenue context lives with the relationship.
Where Braze can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Clari sync into Braze, so people working there have the context without switching tools.
What you can sync between Braze and Clari
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 | Clari objects | How this pairing syncs | |
|---|---|---|---|
| Purchases Transaction records logged against profiles for revenue-based targeting. | Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. | Purchases is specific to Braze and Opportunities to Clari — each maps to any object or custom field on the other side. | |
| Segments Audience definitions read for membership export and campaign targeting. | Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. | Segments is specific to Braze and Activity (Capture) to Clari — each maps to any object or custom field on the other side. | |
| Campaigns Message sends whose metadata and analytics are read for reporting. | Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. | Campaigns is specific to Braze and Account field extensions to Clari — 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. | Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. | Canvases is specific to Braze and Opportunity field extensions to Clari — each maps to any object or custom field on the other side. | |
| Subscription Groups Channel-level opt-in states synced with consent records in other systems. | Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. | Subscription Groups is specific to Braze and Audit Events to Clari — each maps to any object or custom field on the other side. | |
| Content Blocks Reusable message content referenced across campaigns. | Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. | Content Blocks is specific to Braze and Forecast to Clari — each maps to any object or custom field on the other side. |
How changes propagate between Braze and Clari
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 Clari 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 Clari through its API, with automatic retries and rate-limit backoff.
Clari Braze Interval-based propagation
DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).
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.
- Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
What ships with Braze ⇄ Clari
Connect Braze and Clari for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Clari connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Braze or Clari 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 Clari record.
Observability
Monitoring
Track your Braze ⇄ Clari 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 Clari.
How the Braze and Clari 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
Clari
- Integration surface
- REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
- Authentication
- API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
- Change detection
- Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
- Capabilities
- read · write
- Rate limits
- Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
How it works
How to connect Braze to Clari — 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 Clari 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
Clari
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Braze and Clari 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 ⇄ ClariCustomers 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 ClariCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Braze and Clari integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Braze and Clari: authenticate both systems, choose the objects to sync (such as Braze's Purchases and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Braze and Clari. 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 Clari: Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Braze side: Campaigns, Canvases, Subscription Groups, Content Blocks, plus custom fields where Braze exposes them. On the Clari side: Account field extensions, Opportunity field extensions, Audit Events, Forecast. 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 Braze and Clari: Where Braze supplies contact or company data; Where Braze processes payments; Where Braze can store CRM context: fields kept current. Enriched fields land directly on records in Clari, and refreshes keep them from going stale.
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 415 integrations available for Braze and Clari.
Popular · 5 of 415
No integrations match .
