Real-time
Two-way sync
Changes in Active Directory or Freshsales instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Freshsales integration — real-time, two-way sync
Keep Active Directory and Freshsales 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 Freshsales
Keep the people Freshsales and Active Directory both track in agreement in real time: the internal users who own records in Freshsales, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Freshsales 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 Freshsales are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in Freshsales are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Freshsales, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Contacts, Accounts, Deals, Tasks in Freshsales with Directory roles, Service principals & applications, Organizational units, Organizational contacts 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-qualified leads from the warehouse into Freshsales as contacts with lifecycle stages set.
- 02 Keep Freshsales accounts aligned with a billing system so plan and revenue fields stay current.
- 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 a closed deal should provision access: Freshsales drives Active Directory
A won or activated customer in Freshsales 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 Freshsales 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 Freshsales 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 Freshsales
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 | Freshsales objects | How this pairing syncs | |
|---|---|---|---|
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Sales activities Configurable activity types logged against records, useful for engagement scoring. | Service principals & applications is specific to Active Directory and Sales activities to Freshsales — 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. | Products Catalog items attached to deals for line-level revenue data. | Organizational units is specific to Active Directory and Products to Freshsales — 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. | Contacts Person records carrying lifecycle stages; the main entity for two-way CRM syncs. | Organizational contacts is specific to Active Directory and Contacts to Freshsales — 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. | Accounts Company records kept aligned with billing, ERP, and warehouse tables. | Users is specific to Active Directory and Accounts to Freshsales — 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. | Deals Pipeline records synced to a warehouse for revenue reporting. | Groups is specific to Active Directory and Deals to Freshsales — 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. | Tasks Rep to-dos created from external triggers or synced for productivity reporting. | Group memberships is specific to Active Directory and Tasks to Freshsales — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Freshsales
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 Freshsales 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 Freshsales through its API, with automatic retries and rate-limit backoff.
Freshsales Active Directory Sub-second propagation
DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.
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.
- Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
What ships with Active Directory ⇄ Freshsales
Connect Active Directory and Freshsales for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Freshsales connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Freshsales 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 Freshsales record.
Observability
Monitoring
Track your Active Directory ⇄ Freshsales 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 Freshsales.
How the Active Directory and Freshsales 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.
Freshsales
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by Freshworks plan
How it works
How to connect Active Directory to Freshsales — 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 Freshsales 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
Freshsales
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Freshsales 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 ⇄ FreshsalesCustomers 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 FreshsalesCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Freshsales integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Freshsales: 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.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Active Directory and Freshsales records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Freshsales connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Freshsales integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Active Directory and Freshsales. 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 Freshsales: Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Freshsales side: Contacts, Accounts, Deals, Tasks, plus custom fields where Freshsales exposes them. On the Active Directory side: Directory roles, Service principals & applications, Organizational units, Organizational contacts. Stacksync auto-detects both schemas and converts types between the two systems.
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 520 integrations available for Active Directory and Freshsales.
Popular · 8 of 520
-
Active Directory ⇄ Vitally -
Active Directory ⇄ DealCloud -
Active Directory ⇄ Chorusai -
Active Directory ⇄ Clari -
Freshsales ⇄ Okta -
Freshsales ⇄ Onelogin -
Freshsales ⇄ Auth0 -
Freshsales ⇄ Jumpcloud
No integrations match .
