Integrations
Available today: SAML sign-in, custom JSON user synchronization, custom URLs and Exchange/EWS as a preview. ServiceNow, Stripe and Nuki smart locks are planned and currently not configurable.
In short
The Third Party Integrations section of the Admin Panel manages connections to external systems. Available today: SAML sign-in with a mandatory connection test, custom user synchronization from a JSON source, and custom URLs for app, panel and API. Microsoft Exchange/EWS can be configured as a preview, but does not synchronize yet. ServiceNow, Stripe payments and Nuki smart locks are planned and currently not configurable.
Your SAML identity provider, configured in the Admin Panel with certificate, entity ID, NameID format and separate service provider credentials for app and panel. A successful connection test is required before the configuration can be saved.
Members from a secured JSON source, with field mapping, field detection, offboarding and sync status. The route for organizations where OIDC and Graph are not enough.
Your own hostnames for the member app, the Admin Panel and the API.
For on-premises Exchange the connection can be configured today. Booking and calendar synchronization are not active yet; settings are stored and take effect once synchronization ships.
An ITSM connection for tickets from problem reports is on the list. The integration is currently disabled and cannot be configured.
Stripe-based billing for use cases with a payment step is planned and currently not configurable.
A Nuki connection is planned and currently not available. For other locking systems we check the interface before offering anything.
Each integration is a card in the Admin Panel. Available ones can be switched on and configured; planned ones are grouped separately and marked as unavailable – no toggle that leads nowhere.
For tenders we phrase it like this: Door James has a modular architecture and can integrate with existing systems or access control solutions using common technical standards where the third-party system provides a suitable interface and the connection is finished on our side. Which integrations those are today is listed above; the planned ones are marked as planned.
That wording is deliberately conservative. Project experience shows that integration promises almost always fail at the third party – missing API documentation, commercial hurdles or no test access. A verification step before the commitment costs days; an unsustainable commitment costs the project.
Door James has a modern web and backend architecture and can communicate with third-party systems through interfaces. Scope and documentation are agreed per project rather than promised as a generally available public API.
We do not have dates, which is why this page says planned rather than coming soon. All three exist as cards in the Admin Panel and are marked as unavailable there too. If one of them is decisive for you, raise it before the contract rather than after – it belongs in the project plan, not in an expectation.
Only after checking it. Access control vendors frequently use proprietary interfaces or restrict API access, and the Nuki integration on our own side is planned rather than finished. We verify the interface and test access before offering an integration, and we would rather say no than promise a connection that stalls in the project.
Usage and booking data can be exported. For automated transfers into your BI system we agree the route during the rollout.
Which tenant, which directory, which calendars, which identity provider. Thirty minutes is enough to say whether it fits – and where it will not.
