Directory Sync

Build frictionless onboarding for entire organizations with real-time provisioning and deprovisioning of users based on changes to your customers’ directories.


Organizations use directories from providers like Okta or Workday to easily manage employees and user access to resources. Directories enable IT admins to activate and deactivate employee accounts, create groups that inform access rules, accelerate adoption of new tools, and more. Directory Sync connects your application with their directories, keeping your app informed of any changes in their users, groups, and access rules. Get seamless user lifecycle management for both you and your customers by keeping your app in sync with their employee directory.

The WorkOS Directory Sync API supports read-only operations. We will never mutate end-user directories.

Request a Directory Provider

Don't see a Directory Provider you need? Contact us to request a Directory Provider!

Creating an IP Allowlist

WorkOS makes use of Cloudflare, so if you are looking to create an IP allowlist you can use the IP Ranges listed in the Cloudflare documentation.

What you’ll build

In this guide, we’ll take you from learning about Directory Sync and POC-ing all the way through to building production-ready features fully integrated with the WorkOS Directory Sync API.

Sign in to your Developer Dashboard account to see code examples pre-filled with your API keys and resource IDs.

This guide will show you how to:


Create a new Directory in the Developer Dashboard.


Add Directory Sync to your app and fetch Directory resources.


Use webhooks to receive real-time events relating to Directory changes.

Before getting started

To get the most out of this guide, you’ll need:

API Object Definitions




A Directory stores information about an Enterprise’s employee management system (i.e. Directory Provider).

Directory User

A Directory User represents an Enterprise user that is active in an Enterprise’s Directory Provider.

Directory Group

A Directory Group is an organizational unit of Enterprise users, e.x. IT admins, HR, Database admins, etc.


Create a new Directory Connection

The first step to connecting with an organization’s directory is creating an Organization in the WorkOS Dashboard. Then, you can create a new Connection to the directory within the Organization. Let’s start by creating one for development in your Sandbox Project - get Directory Provider specific instructions by selecting which directory provider you want to connect to.

The unique identifier for the Directory is the last part of the URL path and takes the form directory_*

Directory Provider


You can create a Connection with Azure AD SCIM by reading through our integration guide below. It provides end-to-end instructions for creating your Connection in the WorkOS Developer Dashboard.

Connect to Azure AD SCIM

Our guide to creating a new Connection with Azure AD SCIM.


Add Directory Sync to your app

Let’s add Directory Sync to your app to enable programmatic fetching on Directory resources.

Install the WorkOS SDK of your choice

WorkOS offers native SDKs in several popular programming languages. Choose a language below to see instructions in your application’s language.

  • Node.js


  • Ruby


  • Go


  • Python


  • PHP


  • Laravel


  • .NET


  • Java


Request an SDK

Don't see an SDK you need? Contact us to request an SDK!

Install the SDK using the command below.

Install the WorkOS SDK

npm install @workos-inc/node
You can also download the workos-node source code from GitHub.

Set environment variables

As a best practice, your WorkOS API key should be kept secret and set as an environment variable on process start. The Client ID should also be set dynamically based on the release environment.

Environment Variables


Fetch Directory resources

Get the details of an existing Directory User.

Get User

const WorkOS = require('@workos-inc/node');

const workos = new WorkOS(process.env.WORKOS_API_KEY);

directoryUserID =  // ... The ID of the Directory User to fetch
const user = await workos.directorySync.getUser(directoryUserID);
Example use case: Pre-populate user attributes for new user accounts.

Get real-time updates with incoming webhooks

Subscribe your app to changes in Directories by registering incoming webhooks to receive Directory Sync events.

There is currently no rate limiting on event deliveries.

Event Types

Build a webhook URL

Webhooks should use HTTPS and expect to receive POST requests with the following headers:

, v1=

NOTE: We send the header as WorkOS-Signature, but many web servers will normalize all HTTP request headers to their lowercase variants. In this case, you'll extract the workos-signature header.

Below, we’ve provided example approaches for implementing a webhook endpoint.

Webhook endpoint

const express = require('express')

const app = express();

app.use(express.json());'/webhook', (req, res) => {
  const payload = req.body;
  const sigHeader = req.headers['workos-signature'];

  // Verify the signature and process the event


Register the webhook

Set and save the webhook URL in the Developer Dashboard so WorkOS knows where to deliver events.

The Webhook Secret is used to verify webhook requests from WorkOS. Be sure to keep the value secure.

Receive events

We suggest handling events using two concurrent processes to avoid the possibility of unnecessary retry requests hitting your webhook handler.

Process A: Respond with HTTP 200 OK

On receiving an event, you should respond with an HTTP 200 OK. Otherwise, WorkOS will consider the event delivery a failure and retry up to 12 times, with exponential backoff over 3 days.

Process B: Process the request

Before processing the request payload, verify the request was sent by WorkOS and not an unknown party.

The WorkOS SDKs have methods for validating the timestamp and signature of a webhook. Examples using these methods are included below. The parameters are the payload (raw request body), the WorkOS-Signature header, and the Webhook Secret. There is an optional parameter, tolerance, that sets the time validation for the webhook in seconds. The SDK methods have default values for tolerance, usually 3-5 minutes.

Webhook validation

import WorkOS from '@workos-inc/node';

const workos = new WorkOS(process.env.WORKOS_API_KEY);

const webhook = workos.webhooks.constructEvent(
  payload: payload,
  sigHeader: sigHeader,
  secret: process.env.WEBHOOK_SECRET,

If implementing webhook validation yourself, you'll need to use the following steps:

First, extract the timestamp and signature from the header. There are two values to parse from the WorkOS-Signature, delimited by a , character.

  1. issued_timestamp: The epoch time at which the event was issued, prefixed by t=.
  2. signature_hash: The HMAC SHA256 hashed signature for the request, prefixed by v1=.

To avoid replay attacks, we suggest validating that the issued_timestamp does not differ too much from the current time.

Next, construct the expected signature. The expected signature is computed from the concatenation of:

  1. issued_timestamp
  2. The . character
  3. The request’s body as a utf-8 decoded string

Hash the string using HMAC SHA256, using the Webhook Secret as the key. The expected signature will be the hex digest of the hash. Finally, compare signatures to make sure the webhook request is valid.

Once you’ve determined the event request is validly signed, it’s safe to use the event, i.e. the request body, in your application’s business logic.

Go live checklist

Make sure you're ready to go live to production by going through this checklist.

  • You may occasionally receive duplicate webhook events. To prevent duplicate processing of events, we suggest caching received events and implementing logic to skip processing seen events.

    Since webhook events may be delivered out of order, i.e. not in the order in which they were generated, be sure to handle accordingly. The issued_timestamp extracted from the WorkOS-Signature header can be used to determine order.

  • Depending on your network architecture, you may need to allowlist incoming traffic from

    WorkOS currently cannot promise that webhook traffic will originate from a static set of IP addresses.