Real-time
Two-way sync
Changes in Active Directory or Intercom instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Intercom integration — real-time, two-way sync
Keep Active Directory and Intercom 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 Intercom
Keep the people Intercom and Active Directory both track in agreement in real time: the internal users who own records in Intercom, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Intercom 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 Intercom are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Intercom are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Intercom, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Tickets, Data Events, Custom Data Attributes, Tags in Intercom with Organizational units, Organizational contacts, Users, Groups 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 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
- 02 Mirror conversations and tickets into a warehouse for support analytics and SLA reporting
- 03 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
- 04 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
Common sync patterns
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 Intercom, 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 Intercom, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.
Where a closed deal should provision access: Intercom drives Active Directory
A won or activated customer in Intercom can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.
What you can sync between Active Directory and Intercom
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 | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Service principals & applications is specific to Active Directory and Tags to Intercom — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Segments Saved audience definitions are readable for targeting parity across tools. | Organizational units is specific to Active Directory and Segments to Intercom — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Admins & Teams Teammate records map conversation ownership to CRM users. | Organizational contacts is specific to Active Directory and Admins & Teams to Intercom — 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. | Articles Help center content is accessible via API for knowledge sync and audits. | Users is specific to Active Directory and Articles to Intercom — 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. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | Groups is specific to Active Directory and Contacts to Intercom — 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. | Companies Company records group contacts and carry plan and account attributes used in segmentation. | Group memberships is specific to Active Directory and Companies to Intercom — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Intercom
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 Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.
Intercom Active Directory Sub-second propagation
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
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.
- Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Active Directory ⇄ Intercom
Connect Active Directory and Intercom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Intercom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Intercom 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 Intercom record.
Observability
Monitoring
Track your Active Directory ⇄ Intercom 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 Intercom.
How the Active Directory and Intercom 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.
Intercom
- Integration surface
- REST API
- Authentication
- OAuth 2.0 for public apps or a workspace access token
- Change detection
- Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-app rate limits on the Intercom API
How it works
How to connect Active Directory to Intercom — 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 Intercom 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
Intercom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Intercom 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 ⇄ IntercomCustomers 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 IntercomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Intercom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Intercom: authenticate both systems, choose the objects to sync (such as Active Directory's Service principals & applications and Organizational units), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Intercom side: Tickets, Data Events, Custom Data Attributes, Tags, plus custom fields where Intercom exposes them. On the Active Directory side: Organizational units, Organizational contacts, Users, Groups. 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 Intercom: Where Active Directory runs customer login accounts: identity on the customer record; Group and entitlement membership as CRM fields; Where a closed deal should provision access: Intercom drives Active Directory. Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Intercom, so go-to-market teams see who has actually activated and who has gone dormant.
-
Active Directory: 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. Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Intercom: Webhook topics cover contact, company, conversation, and ticket lifecycle events, making event-driven sync practical. Active Directory: Writes require matching Graph application permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) with tenant admin consent; delegated and application scopes differ. Stacksync's field mapping accounts for these differences between Active Directory and Intercom without custom code.
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 511 integrations available for Active Directory and Intercom.
Popular · 8 of 511
-
Active Directory ⇄ Pipedrive -
Active Directory ⇄ Zoho CRM -
Active Directory ⇄ Shopify -
Active Directory ⇄ Affinity -
Intercom ⇄ Auth0 -
Intercom ⇄ Jumpcloud - Intercom ⇄ Azure Active Directory
-
Intercom ⇄ Okta
No integrations match .
