Skip to main content
Use the @bijectionhq/connectors/workos-directory entrypoint to declare WorkOS Directory Sync resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Directory users

enumeration: Users with ordered event hints and reconciliation

The following example matches configuration standard.

Configuration: standard

Case: workos-directory/users/enumeration/standard. Connection and resource configuration are declared by this exact case. Credential kind: workos. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Verification scope Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.

Directory groups

enumeration: Groups with ordered event hints and reconciliation

The following example matches configuration standard.

Configuration: standard

Case: workos-directory/groups/enumeration/standard. Connection and resource configuration are declared by this exact case. Credential kind: workos. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Verification scope Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.

Active group members

enumeration: Current group-scoped user observations

The following example matches configuration standard.

Configuration: standard

Case: workos-directory/members/enumeration/standard. Connection and resource configuration are declared by this exact case. Credential kind: workos. Keep credential material in the private credential inventory. Inspect the complete configuration contract below for settings and conditional requirements.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Verification scope Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.

Provider guidance

These resources acquire reviewed directory observations through the existing native source, credential, listener and publication owners. They grant no roles, link no identities by email and perform no application provisioning side effects.
Install a native workos bearer credential containing a WorkOS API key. Bind the resource and credential using the ordinary deployment resource bindings. The fixed API origin is https://api.workos.com; secrets remain in native transport custody. Identity admission reads the selected directory and requires its exact directory ID, organization ID and active state. WorkOS provides no read-only API-key environment identity, so this proves the selected directory; it does not infer an environment from a credential label. users.enumeration and groups.enumeration use immutable provider IDs, enumeration and point reconciliation. An admitted 404 or explicitly inactive user withdraws the applicable observation. Authentication failures, outages, malformed pagination and unknown user states establish no empty population. Incomplete pages never claim completion. Native source freshness and the application’s participation policy determine how long earlier observations remain usable during an outage. members.enumeration({directory,organization,group}) acquires positive group-scoped user observations. The group must belong to the reviewed directory. WorkOS has no point membership read or snapshot guarantee for its live pages, so coverage remains none. A missing member’s earlier observation retains its original time and must expire under an explicit per-record source freshness requirement. Finishing a pass cannot renew it or prove deletion. Do not project these observations into unbounded durable grants. The deprecated user.groups field is never read. Each resource consumes the ordered Events API with a retained native after cursor and its documented 90-day retention. Events trigger source acquisition; late or replayed event payloads never overwrite current directory records. Periodic reconciliation remains independent of event delivery. An expired or refused cursor requires source repair and enumeration; it never silently skips an interval. Optional webhooks are additional signed refresh hints using exact raw-body HMAC verification, millisecond timestamps and a five-minute tolerance. Install the channel’s signing credential through the native listener owner. Inspect the existing source and listener owners for transport progress and native publication/coverage. The consumed provider cursor and applied access publication are separate observations; neither implies the other is current. Use the native source’s publication revision and coverage when projecting directory observations into participation. Keep that projection under its existing exclusive provisioning writer, and declare an access freshness bound. Removing this source removes its contribution; it does not delete a person or their independently granted authority. The package scenarios explicitly report missing provider qualification. The colocated source tests establish parsing and declaration behavior only. Live qualification remains opt-in. Provider contracts: Directory users, Directory groups, Events API.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 455b2e3ba5a436b66a8f4c3fb2b05a442c4711673952d2f858e9da4ebdc097d6. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.