Real-time
Two-way sync
Changes in Active Directory or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Active Directory to Folk CRM integration — real-time, two-way sync
Keep Active Directory and Folk 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 Folk CRM
Keep the people Folk CRM and Active Directory both track in agreement in real time: the internal users who own records in Folk CRM, and the customer login accounts in Active Directory.
A CRM and an identity system usually describe different populations. Folk 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 Folk 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 Folk CRM are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in Folk CRM, and a signup in Active Directory never reaches the account it belongs to.
Stacksync syncs Custom fields, Notes, Reminders, People in Folk CRM with Groups, Group memberships, Devices, Directory roles 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 enriched contact data from a data warehouse into folk custom fields.
- 02 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 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 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 Folk 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 Folk CRM, 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: Folk CRM drives Active Directory
A won or activated customer in Folk CRM 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 Folk 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 | Folk CRM objects | How this pairing syncs | |
|---|---|---|---|
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Notes Free-text context attached to people and companies, readable for reporting. | Organizational contacts is specific to Active Directory and Notes to Folk 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. | Reminders Follow-up items that can be created from external triggers. | Users is specific to Active Directory and Reminders to Folk 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. | People Contact records; the primary entity synced with outreach and enrichment tools. | Group memberships is specific to Active Directory and People to Folk 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. | Companies Organization records linked to people and kept aligned with billing or CS systems. | Devices is specific to Active Directory and Companies to Folk 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. | Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Directory roles is specific to Active Directory and Custom fields to Folk CRM — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Folk 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 Folk 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Folk CRM Active Directory Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
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.
- Folk CRM: Subject to the platform's API rate limits.
What ships with Active Directory ⇄ Folk CRM
Connect Active Directory and Folk CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Folk CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Folk 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 Folk CRM record.
Observability
Monitoring
Track your Active Directory ⇄ Folk 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 Folk CRM.
How the Active Directory and Folk 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.
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Active Directory to Folk 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 Folk 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
Folk CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Folk 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 ⇄ Folk 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 Folk CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Folk CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Folk CRM: authenticate both systems, choose the objects to sync (such as Active Directory's Groups and Organizational contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Active Directory and Folk CRM: 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: Folk CRM drives Active Directory. Signup, account status, multi-factor enrollment, and last-login from Active Directory land on the matching contact or account in Folk CRM, 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. Folk CRM: REST API. Authentication: API key (Bearer token). Stacksync manages authentication, retries, and rate limits on both sides.
-
Folk CRM: The API surface covers people, companies, groups, deals, notes, reminders, and interactions, plus webhook subscriptions for record events. Active Directory: DirectoryRole, servicePrincipal, and device objects are effectively read-only for sync; Users, Groups, and memberships are the writable surface. Stacksync's field mapping accounts for these differences between Active Directory and Folk CRM without custom code.
-
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 Folk CRM 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 Folk CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Folk CRM integration in-house.
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 414 integrations available for Active Directory and Folk CRM.
Popular · 8 of 414
-
Active Directory ⇄ SAP Sales Cloud -
Active Directory ⇄ Streak CRM -
Active Directory ⇄ SugarCRM -
Active Directory ⇄ Twenty CRM - Folk CRM ⇄ Azure Active Directory
-
Folk CRM ⇄ Okta -
Folk CRM ⇄ Onelogin -
Folk CRM ⇄ Auth0
No integrations match .
