Real-time
Two-way sync
Changes in Active Directory or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ ERP
Active Directory to Linnworks integration — real-time, two-way sync
Keep Active Directory and Linnworks 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 Linnworks
Keep the employee, group, and account records that Linnworks and Active Directory share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Linnworks holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Active Directory controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Linnworks and their account still being active in Active Directory is a real security exposure.
Stacksync syncs Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks with Group memberships, Devices, Directory roles, Service principals & applications in Active Directory in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
- 02 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
- 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
Common sync patterns
Disable access at offboarding
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
Keep profile attributes current
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
What you can sync between Active Directory and Linnworks
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 | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Directory roles is specific to Active Directory and Open Orders to Linnworks — 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. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Service principals & applications is specific to Active Directory and Processed Orders to Linnworks — 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. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Organizational units is specific to Active Directory and Stock Items to Linnworks — 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. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Organizational contacts is specific to Active Directory and Stock Levels to Linnworks — 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. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Users is specific to Active Directory and Locations to Linnworks — 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. | Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Groups is specific to Active Directory and Purchase Orders to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Linnworks
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 Linnworks 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 Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks Active Directory Interval-based propagation
DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.
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.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Active Directory ⇄ Linnworks
Connect Active Directory and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Linnworks 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 Linnworks record.
Observability
Monitoring
Track your Active Directory ⇄ Linnworks 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 Linnworks.
How the Active Directory and Linnworks 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.
Linnworks
- Integration surface
- REST API
- Authentication
- Application credentials and an install token exchanged for a session token
- Change detection
- Polling on order and stock endpoints
- Capabilities
- read · write
- Rate limits
- Per-endpoint rate limits apply on the Linnworks API
How it works
How to connect Active Directory to Linnworks — 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 Linnworks 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
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Linnworks 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 ⇄ LinnworksCustomers 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 LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Linnworks: authenticate both systems, choose the objects to sync (such as Active Directory's Directory roles and Service principals & applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Linnworks: Disable access at offboarding; Keep profile attributes current; Align group and department membership. When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
-
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. Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
Linnworks: Orders are modeled in two populations, open orders and processed orders, and syncs typically treat processing as the state transition that moves a record between them. 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 Linnworks 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 Linnworks records are not retained after a sync operation.
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 502 integrations available for Active Directory and Linnworks.
Popular · 8 of 502
-
Active Directory ⇄ Acumatica -
Active Directory ⇄ SAP S/4HANA -
Active Directory ⇄ Odoo -
Active Directory ⇄ Blue Yonder WMS - Linnworks ⇄ Azure Active Directory
-
Linnworks ⇄ Okta -
Linnworks ⇄ Onelogin -
Linnworks ⇄ Auth0
No integrations match .
