Real-time
Two-way sync
Changes in Active Directory or Clari instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Clari integration — real-time, two-way sync
Keep Active Directory 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 Active Directory and Clari
Keep the people Clari and Active Directory both track in agreement in real time: the internal users who own records in Clari, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Clari tracks customers, contacts, and the deals in motion; Active Directory governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Clari are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Clari are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Clari, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Opportunity field extensions, Audit Events, Forecast, Quota in Clari with Devices, Directory roles, Service principals & applications, Organizational units in Active Directory in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.
Common use cases
- 01 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.
- 02 Enrich Clari Account records with firmographic or billing data points through the ingest API in incremental mode.
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Where a closed deal should provision access: Clari drives Active Directory
A won or activated customer in Clari can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
Where Active Directory governs your workforce: CRM users kept current
New employees in Active Directory become active users in Clari with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.
Deactivation and record hand-off
When someone is disabled in Active Directory, the matching user in Clari is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
What you can sync between Active Directory 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.
| Active Directory objects | Clari objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. | Users is specific to Active Directory and Audit Events to Clari — each maps to any object or custom field on the other side. | |
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. | Groups is specific to Active Directory and Forecast to Clari — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. | Group memberships is specific to Active Directory and Quota to Clari — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | 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. | Devices is specific to Active Directory and Opportunities to Clari — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. | Directory roles is specific to Active Directory and Activity (Capture) to Clari — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | 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. | Service principals & applications is specific to Active Directory and Account field extensions to Clari — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory 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.
Active Directory Clari Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is written to Clari through its API, with automatic retries and rate-limit backoff.
Clari Active Directory 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 Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
- 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 Active Directory ⇄ Clari
Connect Active Directory and Clari for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Clari connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory 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 Active Directory or Clari record.
Observability
Monitoring
Track your Active Directory ⇄ Clari sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Clari.
How the Active Directory and Clari connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
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 Active Directory 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 Active Directory 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.
Active Directory
connected
Clari
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory 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 · Active Directory ⇄ 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.
Active Directory ClariCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Clari integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Clari: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Clari. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged 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 Clari side: Opportunity field extensions, Audit Events, Forecast, Quota, plus custom fields where Clari exposes them. On the Active Directory side: Devices, Directory roles, Service principals & applications, Organizational units. 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 Active Directory and Clari: Where a closed deal should provision access: Clari drives Active Directory; Where Active Directory governs your workforce: CRM users kept current; Deactivation and record hand-off. A won or activated customer in Clari can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
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 420 integrations available for Active Directory and Clari.
Popular · 8 of 420
-
Active Directory ⇄ Kustomer -
Active Directory ⇄ Nimble -
Active Directory ⇄ Nutshell -
Active Directory ⇄ Oracle CX Sales -
Clari ⇄ Auth0 -
Clari ⇄ Jumpcloud - Clari ⇄ Azure Active Directory
-
Clari ⇄ Okta
No integrations match .
