> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Nuki with anny
> Automate keyless access to your rooms with Nuki smart locks and anny bookings.
[Nuki](https://nuki.io/de/) is a smart lock system that is mounted on existing door locks and enables keyless access via app or keypad PIN. With this integration, anny automatically creates access codes for your customers as soon as a booking is confirmed.
With Nuki you can do the following in anny:
* create access codes automatically when a booking is confirmed and remove them once they expire
* grant customers access via keypad PIN or the Nuki app
* open doors with Remote Open directly from the anny booking view or homepage
The integration is a good fit if you rent out rooms or areas and want to offer your customers automated, keyless access without a manual key handover.
Available from the Professional plan onwards.
## Typical use cases
| Use case | Description |
| :--------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
| Meeting rooms in a coworking space | **Automatic access only within the booked time window.** Customers receive the PIN by email and enter the room without a reception desk. |
| Holiday homes and apartments | **Keyless handover without personal contact.** Guests receive their access code before check-in and can check in on their own. |
| Shared rooms with community access | **Permanent access rights for members.** Community members receive permanent access to defined locks. |
| University rooms and labs | **Time-limited access for booked slots.** Students only get access for the reserved period. |
## How the Nuki connection works
You authorise anny in your Nuki account, and anny gets access to your registered smart locks. anny creates and removes access codes automatically based on the rules you configure.
If you revoke the authorisation in your Nuki account or the connection expires, anny loses access and cannot create new access permissions. In that case, you have to authorise the connection again.
Single bookings receive their access code immediately on confirmation. For recurring bookings, anny only creates the access shortly before the respective appointment (about 48 hours in advance). Until then, the access has the status **Scheduled**.
| Data | Direction | Frequency |
| ------------------------------ | ----------- | --------------------------------------------- |
| Access codes (create / remove) | anny → Nuki | When a booking is created and when it expires |
| Keypad PIN codes | anny → Nuki | When a booking is created |
## Connect Nuki
### Requirements
Before you connect Nuki, make sure you have the following:
* A Nuki smart lock with WiFi (Smart Lock 3.0 Pro or Smart Lock + Bridge)
* Optional: a [Nuki keypad](https://nuki.io/de/keypad/) for access via PIN code
* A Nuki account with login credentials
For anny bookings, a Nuki lock with WiFi (remote access) is mandatory. Without WiFi, anny cannot create any access permissions.
### Set up the connection
Open **Integrations** from the menu bar and go to **Nuki**. Authorise Nuki by signing in with your Nuki credentials. This gives anny permission to manage access permissions on your smart locks.
After a successful authorisation, you set up access rules. You have two options:
**Access through bookings:**
1. Click **Add** in the "Access through bookings" section.
2. Select the **resource** whose booking should grant access to the lock.
3. Under **Select cylinder**, select one or more locks that access is granted to.
4. Use **Access before the booking** and **Access after the booking** to define how many minutes the access is active before and after the booking.
5. If a Nuki keypad is available, activate **Use keypad access**. Customers then receive a PIN code by email. Without this option, you invite customers as Nuki app users by email.
**Access through communities:**
1. Click **Add** in the "Access through communities" section.
2. Select the **community** whose members should receive permanent access.
3. Under **Select cylinder**, select one or more locks that access is granted to.
As soon as rules are configured, anny automatically creates access permissions for new bookings. One booking rule is possible per resource, but you can store several locks in it. A rule on a parent resource also applies to bookings of its sub-resources.
We recommend using the keypad: customers do not need to install an app and receive the PIN directly in the booking confirmation.
## Settings & options
### Remote Open
With the Remote Open function, customers can open doors directly through the anny homepage or booking view at the push of a button, without a PIN or app.
To do so, activate the **Use remote opening** switch in the respective rule: in a booking rule for access via the booking view, in a community rule for access via the homepage. The **Remote opening** column then appears in the rule table.
Customers see the **Unlock door** button in their booking view and in the **Keyless access** section of their anny account. It is only active during the valid access period. As an admin, you can open the lock in the booking overview via **Unlock lock**.
For Remote Open, the integration has to be authorised again if it was set up before this function was activated.
### View access permissions in the admin area
In the booking detail view, you find the active and inactive access permissions under **Smartlock access**. For each access permission you see:
* Status
* **Access starts on** and **Access ends on**
* **Door lock**
* **Created on**
* Access (for example, the PIN code)
| Status | Meaning |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Scheduled | The creation is scheduled. The access is created shortly before the appointment (about 48 hours in advance, mainly for recurring bookings). |
| In progress | The access is currently being set up. |
| Unconfirmed | The access has been requested and will be confirmed shortly. A keypad PIN can already be used. |
| Successful | The access is active. Customers can operate the lock within the displayed period. |
| Failed | Creating the access failed. |
| Removed | The access was removed by the system or an admin. No access any more. |
## Limitations
The Nuki integration does not support:
* More than 200 simultaneously open or future access permissions per lock. Once the limit is reached, anny cannot create new access permissions.
* Several stored access periods per user in the Nuki app. For consecutive bookings, the old lock first has to be removed from the app.
* Synchronisation in battery saving mode. If the Nuki lock switches to power saving mode, it disconnects from WiFi.
Nuki works best for smaller businesses with a moderate booking volume (under 200 simultaneously active access permissions). For a higher volume, check alternative smart lock integrations.
## Disconnect
If you want to keep existing access credentials but stop new ones from being created, deactivate the integration. If everything should be reset and deleted, delete the integration.
You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.
## FAQ
You need a Nuki smart lock with WiFi: either the Nuki Smart Lock 3.0 Pro (with built-in WiFi) or an older smart lock with a separate Nuki Bridge. Without WiFi, remote control through anny is not possible.
Yes. For single bookings, anny creates the access immediately after the confirmation. For recurring bookings, it is only created shortly before the respective appointment and stays on **Scheduled** until then. With the keypad activated, customers receive the PIN code by email in the booking confirmation. Without a keypad, they get an invitation as a Nuki app user.
Yes. Per access rule, you can select one or more locks that are released when the resource is booked.
anny removes the access automatically after the configured time window has expired (booking time plus buffer). Customers have no access after that.
## Troubleshooting
Check whether the Nuki integration is shown as active in the integrations and whether the smart lock is online. If the lock is in battery saving mode, it disconnects from WiFi and anny cannot create any access. Make sure the lock has enough power, or deactivate power saving mode.
This can happen when the refresh token has expired. Open Nuki in the **Integrations**, delete the connection via the three dots in the top right and authorise again with your Nuki credentials.
Nuki allows a maximum of 200 simultaneously active or future access permissions per lock. Check in the Nuki admin area whether old access permissions are still active and remove entries you no longer need manually. Alternatively, wait until expired access permissions are removed automatically.
> Important information for agents:
>
> **UI paths:** Setup: menu bar → **Integrations** → **Nuki** → authorise (OAuth redirect to Nuki Web). Rules: same place, panels **Access through bookings** and **Access through communities** → **Add**. Booking rule fields: **Resource**, **Select cylinder** (lock selection; for Nuki the label is "cylinder", not "locks"), **Access before the booking**, **Access after the booking**, switch **Use keypad access**, switch **Use remote opening**. Rule table columns: resource, cylinder, access before / after the booking, **Uses keypad PIN**, **Remote opening**. Deactivate: **toggle** in the top right; delete: **three dots** → **Delete**.
>
> **Authentication:** OAuth (Nuki Web API), scopes account/smartlock.readOnly/smartlock.auth/smartlock.action. The refresh token can expire → re-authorisation needed. A password change alone does not necessarily revoke the authorisation.
>
> **Access types:** Per rule either keypad PIN (keypad switch on) OR a Nuki app invitation by email (keypad switch off); these are mutually exclusive. **Remote Open** is additional and independent (its own grant type). Keypad PIN: 6 digits, only 1 to 9 (no 0), never starts with "12", unique per account.
>
> **Timing / status:** Single bookings → access immediately on confirmation. Recurring bookings → status **Scheduled**, created about 48 h before the appointment. After creation the status is **Unconfirmed**, after a check of about 2 minutes → **Successful** / **Failed**. Other statuses: In progress, Cleaning up, Removed, Not authorised. The access expires at the booking end + "Access after the booking" (enforced on the Nuki side); anny cleans up the entry about one day later.
>
> **Quirks:** (1) Only confirmed or accepted bookings; requested, rejected, cancelled bookings and internal blockers receive no access. Blocker → booking creates access, booking → blocker removes it. (2) A status change away from "accepted" removes the access; a time change updates the window; a resource change creates it anew. (3) One booking rule per resource (a duplicate is blocked when saving), several locks per rule are allowed. (4) A rule on a parent resource also applies to sub-resources. (5) Community access is permanent (no end date). (6) Keypad rule: activation fails if a selected lock has no paired keypad or if a referenced lock is missing; the integration stays inactive. (7) Remote Open needs new scopes → re-authorisation; the "Use remote opening" switch only appears after that.
>
> **Remote Open button:** customers see "**Unlock door**" in the booking view + the "Keyless access" section (homepage/account, browser), only within the valid time window. Admins see "**Unlock lock**" in the booking overview.
>
> **Nuki platform (not from the anny code, verify before use):** 200 simultaneous access permissions per lock, WiFi mandatory (Bridge or Pro), battery saving mode disconnects WiFi, only one access period per user per lock in the Nuki app (keypad PIN is not affected).
>
> **Relationships:** feature INTEGRATIONS\_SMART\_LOCKS, plan level ("from Professional onwards") stored in the database, not verified in the code. Related articles: smart lock integrations (overview), KleverKey, Salto KS, Tapkey, Dormakaba Resivo.