Configure the 2N Intercom integration

How to configure the 2N Intercom integration

The 2N Intercom integration lets visitors use the QR code from their invitation at a 2N intercom for building access. When enabled, Salto IDM synchronizes the visitor's person lifecycle (create, revoke, delete), company, and validity window with 2N, and keeps a single pincode between IDM and 2N to avoid mismatches.

The integration is enabled and configured per environment, each with its own credentials and connection test.

Use this guide to enable the integration, configure it correctly, and validate the QR, pincode, and person lifecycle behavior end-to-end.

Prerequisites

Before you start, make sure you have:

• 2N API credentials and network reachability from Salto IDM to the 2N endpoint.
• A Salto IDM administrator account with access to Settings > Integrations.
• At least one IDM environment to configure. If you have both a Staging and a Production environment, validate on Staging first.
• Visitor invitation templates that include the QR code, if visitors use QR codes at the intercoms.

Step 1: Enable the 2N Intercom module

1. Go to Settings > Integrations.
2. Locate 2N Intercom and toggle the module On for the target environment.
3. If Send QR to Salto is on, an additional Store 2N QR-code toggle appears. Enable it if you want the QR code stored in IDM for auditing or resending invitations.

Step 2: Add 2N credentials and test the connection

1. Open the 2N configuration page under Settings > Integrations > 2N.
2. Enter your 2N API endpoint and credentials, as provided by your 2N administrator.
3. Select Test Connection.

Step 3: Configure behavior for the environment

1. Choose which identity types are allowed to sync to 2N. Visitors are the primary use case.
2. Confirm that visitor invitation templates include a QR code. If your process uses a kiosk or email pincode, make sure the format matches what 2N expects.
3. Decide whether to store 2N QR codes in IDM. Storing them helps with support and re-sending invitations.

Step 4: Validate the integration

1. Create a test visitor with a valid visit window, then send the invitation and confirm the QR code is generated.
2. At a 2N device, present the QR code and confirm access is granted within the visit window.
3. Confirm the same pincode appears in the kiosk or email invitation and in 2N.
4. Revoke, then delete the test person, and confirm the corresponding updates happen in 2N.

Step 5: Go live

Before enabling the integration in Production, confirm that:

• 2N credentials are stored securely (for example, in a password manager) and rotated according to your policy.
• Test Connection succeeds in both Staging and Production.
• Visitor templates include the QR code and have been reviewed by stakeholders.
• The pincode format doesn't conflict between IDM and 2N.
• Administrators and Front Desk staff are trained on expected behavior and troubleshooting.

How synchronization works

• Create person—IDM sends a create (or update) request to 2N with the Person, Company, QR code, and validity window.
• Revoke or deactivate—IDM updates 2N to restrict or remove the person's validity.
• Delete person—IDM sends a delete request to 2N to remove the identity.

When the 2N module is disabled for an environment, IDM doesn't call the 2N API for any person lifecycle event.

Common error messages

FAQ

Does disabling the 2N module stop all calls to 2N? Yes. When the module is disabled for an environment, IDM doesn't call the 2N API for person create, revoke, or delete.

How do we ensure the same pincode appears in IDM and 2N? The integration synchronizes pincode generation so the kiosk, email, and 2N all receive the same value. If you see a mismatch, verify the environment's pincode format policy and re-save the person to trigger a new sync.

Can we store 2N QR codes in IDM? Yes. When Send QR to Salto is on, enable Store 2N QR-code to keep the QR code inside IDM for support and re-sending invitations.