Real-time
Two-way sync
Changes in Active Directory or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Business productivity
Active Directory to Gatekeeper integration — real-time, two-way sync
Keep Active Directory and Gatekeeper 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 Gatekeeper
Keep the users, groups, and profile details that Gatekeeper and Active Directory share consistent in real time, so who can work in Gatekeeper always matches who your directory in Active Directory says belongs there.
Active Directory is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. Gatekeeper is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.
Stacksync syncs Vendors (Suppliers), Files, Workflow form data, Custom data groups in Gatekeeper with Service principals & applications, Organizational units, Organizational contacts, Users in Active Directory bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.
That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.
Common use cases
- 01 Sync Vendors (Suppliers) with a CRM or ERP so counterparty, compliance, contact, and spend records match across the VCLM and the systems of record.
- 02 Push generated documents into Gatekeeper Files, or pull executed contract PDFs and compliance evidence out into a document store or archive.
- 03 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
- 04 Two-way sync Users and Groups between Microsoft Entra ID and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
Common sync patterns
Provision access when someone joins
A user added to Active Directory, or moved into a group inside it, gets the matching account or membership created in Gatekeeper, so a new hire can start working without a separate setup ticket.
Close access when someone leaves
When a user is disabled or removed in Active Directory, their account in Gatekeeper is deactivated in step, so offboarding shuts down access everywhere instead of leaving a live login behind.
Keep profile attributes current
A person's name, email, department, manager, or phone number corrected in either system updates the other, so the productivity tool shows the same details the directory holds of record.
What you can sync between Active Directory and Gatekeeper
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 | Gatekeeper objects | How this pairing syncs | |
|---|---|---|---|
| Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. | Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Contracts The core contract records holding value, key dates, renewal terms, status, type, owner, and the linked vendor; created, read, updated, and deleted so contract data moves two-way between Gatekeeper and a database, ERP, or CRM. | Service principals & applications is specific to Active Directory and Contracts to Gatekeeper — 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. | Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. | Organizational units is specific to Active Directory and Vendors (Suppliers) to Gatekeeper — 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. | Files Document files attached to contracts and vendors - executed PDFs, certificates, and compliance evidence; read to pull signed files and evidence out, or written to push generated documents in. | Organizational contacts is specific to Active Directory and Files to Gatekeeper — 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. | Workflow form data The structured data captured on Gatekeeper workflow forms (intake requests, vendor onboarding, risk assessments); exposed by the API since 2025 so form results sync into an operational database, not only contract and vendor records. | Groups is specific to Active Directory and Workflow form data to Gatekeeper — 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. | Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. | Group memberships is specific to Active Directory and Custom data groups to Gatekeeper — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Gatekeeper
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 Gatekeeper 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 Gatekeeper through its API, with automatic retries and rate-limit backoff.
Gatekeeper Active Directory Interval-based propagation
DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.
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.
- Gatekeeper: Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
What ships with Active Directory ⇄ Gatekeeper
Connect Active Directory and Gatekeeper for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Gatekeeper connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Gatekeeper 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 Gatekeeper record.
Observability
Monitoring
Track your Active Directory ⇄ Gatekeeper 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 Gatekeeper.
How the Active Directory and Gatekeeper 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.
Gatekeeper
- Integration surface
- RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant.
- Authentication
- API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently.
- Change detection
- No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream.
- Capabilities
- read · write
- Rate limits
- Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
How it works
How to connect Active Directory to Gatekeeper — 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 Gatekeeper 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
Gatekeeper
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Gatekeeper 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 ⇄ GatekeeperCustomers 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 GatekeeperCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Gatekeeper integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Gatekeeper: authenticate both systems, choose the objects to sync (such as Active Directory's Users and Service principals & applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Gatekeeper side: Vendors (Suppliers), Files, Workflow form data, Custom data groups, plus custom fields where Gatekeeper 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 Gatekeeper: Provision access when someone joins; Close access when someone leaves; Keep profile attributes current. A user added to Active Directory, or moved into a group inside it, gets the matching account or membership created in Gatekeeper, so a new hire can start working without a separate setup ticket.
-
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. Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. Stacksync manages authentication, retries, and rate limits on both sides.
-
Gatekeeper: Write access is per API key per endpoint: when you create a key you choose read-only or write for each object, so the API is write-capable and can create and update records rather than only export them. Active Directory: Microsoft Graph delta tokens for directory objects expire after about seven days; a sync paused longer must reinitialize with a full read. Stacksync's field mapping accounts for these differences between Active Directory and Gatekeeper 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 405 integrations available for Active Directory and Gatekeeper.
Popular · 8 of 405
-
Active Directory ⇄ Full Enrich -
Active Directory ⇄ Google Sheets -
Active Directory ⇄ Klaviyo -
Active Directory ⇄ Lemlist -
Gatekeeper ⇄ Auth0 -
Gatekeeper ⇄ Jumpcloud - Gatekeeper ⇄ Azure Active Directory
-
Gatekeeper ⇄ Okta
No integrations match .
