Real-time
Two-way sync
Changes in Active Directory or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Twenty CRM integration — real-time, two-way sync
Keep Active Directory and Twenty CRM 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 Twenty CRM
Keep the people Twenty CRM and Active Directory both track in agreement in real time: the internal users who own records in Twenty CRM, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Twenty CRM 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 Twenty CRM are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Twenty CRM are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Twenty CRM, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Opportunities, Tasks, Notes, Custom Objects in Twenty CRM with Service principals & applications, Organizational units, Organizational contacts, Users 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 Mirror support tickets or tasks between Twenty and an operations tool.
- 02 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 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
Deactivation and record hand-off
When someone is disabled in Active Directory, the matching user in Twenty CRM is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
Where Active Directory runs customer login accounts: identity on the customer record
Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Twenty CRM, so go-to-market teams see who has actually activated and who has gone dormant.
Group and entitlement membership as CRM fields
Membership of a directory group or an entitlement in Active Directory maps to fields in Twenty CRM, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.
What you can sync between Active Directory and Twenty CRM
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 | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Tasks To-dos linked to people, companies, or deals. | Organizational contacts is specific to Active Directory and Tasks to Twenty CRM — each maps to any object or custom field on the other side. | |
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Notes Free-form notes attached to records, useful for mirroring activity from other tools. | Users is specific to Active Directory and Notes to Twenty CRM — 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. | Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | Groups is specific to Active Directory and Custom Objects to Twenty CRM — 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. | Attachments Files linked to records. | Group memberships is specific to Active Directory and Attachments to Twenty CRM — 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. | Workspace Members User accounts used for record ownership and assignment mapping. | Devices is specific to Active Directory and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Directory roles is specific to Active Directory and People to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Twenty CRM
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 Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Active Directory Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Active Directory ⇄ Twenty CRM
Connect Active Directory and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Active Directory ⇄ Twenty CRM 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 Twenty CRM.
How the Active Directory and Twenty CRM 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.
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Active Directory to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Twenty CRM: authenticate both systems, choose the objects to sync (such as Active Directory's Organizational contacts and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Twenty CRM. 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 Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Twenty CRM side: Opportunities, Tasks, Notes, Custom Objects, plus custom fields where Twenty CRM exposes them. On the Active Directory side: Service principals & applications, Organizational units, Organizational contacts, Users. 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 Twenty CRM: Deactivation and record hand-off; Where Active Directory runs customer login accounts: identity on the customer record; Group and entitlement membership as CRM fields. When someone is disabled in Active Directory, the matching user in Twenty CRM is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
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 433 integrations available for Active Directory and Twenty CRM.
Popular · 7 of 433
-
Active Directory ⇄ Zoho SalesIQ -
Active Directory ⇄ Vitally -
Active Directory ⇄ DealCloud -
Twenty CRM ⇄ Okta -
Twenty CRM ⇄ Onelogin -
Twenty CRM ⇄ Auth0 -
Twenty CRM ⇄ Jumpcloud
No integrations match .
