> ## 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 Comydo with anny
> Automate QR code access and licence plate entry for bookings with Comydo.
[Comydo](https://comydo.com/) is a digital access system for doors, gates and barriers that uses QR codes and licence plates as keys. With this integration, anny automates the matching access for bookings and community members.
With Comydo you can do the following in anny:
* Create time-limited QR code access for bookings
* Link resources and communities with one or more Comydo device IDs
* Extend the access before and after the booking with a buffer time
* Open parking barriers by licence plate and, optionally, check in on the first scan and check out on the second scan
The integration is a particularly good fit for rooms, shared areas and car parks where access should work without a manual key handover.
Available from the Professional plan onwards.
## Typical use cases
| Use case | Description |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Open rooms with a QR code | **Access that matches the booking.** Customers receive a QR code in the anny app or booking confirmation and scan it at the Comydo device. |
| Release community members | **Manage membership-based access.** Link a community with one or more Comydo access points. |
| Open car parks by licence plate | **Automatic entry without a ticket.** Comydo recognises the licence plate captured during the booking and opens the linked barrier. |
## How the Comydo connection works
The setup consists of two parts. First you enter your **auth key** in anny, which you find in the Comydo admin app. anny then shows a **webhook URL** that you store in the Comydo admin area. After that, you define rules that link resources or communities with Comydo devices.
For a matching booking, anny creates time-limited access and stores it itself: the booking ticket as a QR code or, for car parks, an encrypted check value of the licence plate. Customers receive the QR code in the anny app or booking confirmation.
When someone scans at the Comydo device, Comydo queries anny via the webhook URL. anny checks the stored access permissions and replies whether the access is valid. So anny does not send any booking data or licence plates to Comydo, it confirms each scan individually.
If the connection is deactivated or deleted, anny no longer confirms any access through Comydo.
| Data | Direction | Frequency |
| ----------------------------------------------------- | ------------- | -------------------------------- |
| Access request on a scan (device ID and scanned code) | Comydo → anny | On every scan at a Comydo device |
| Access confirmation (valid or not valid) | anny → Comydo | As a response to every request |
## Connect Comydo
### Requirements
Before you connect Comydo, make sure that:
* your Comydo account is set up and the required doors or barriers are created with their device IDs in the Comydo portal,
* your resources or communities are set up in anny,
* the **Check-In function** of the resource is activated for QR code access, because the booking ticket is scanned for entry,
* for car park bookings you use a custom form field for the licence plate that is requested as a **mandatory field**,
* you have your **auth key** from the Comydo admin app at hand.
### Set up the connection
Open the **Integrations** from the **menu bar** and go to **Comydo**. Enter your **auth key** from the Comydo admin app and save it. anny then shows the **webhook URL**. Copy it and store it in the Comydo admin area so Comydo can confirm every scan with anny.
Create the rules you need:
1. Click **Add**.
2. Select a resource or community.
3. Enter one or more **device IDs** of your Comydo devices.
4. For booking rules, define **Access before the booking** and **Access after the booking**.
5. For a car park rule, activate **Licence plate recognition** and select the **Custom field for licence plate**.
6. If needed, activate **Check in on the first scan** and **Check out on the second scan**.
7. Create a test booking and check the full access process.
The image shows the area of the Comydo integration where you set up the webhook connection.
The first image shows a rule for booking access. The second image shows the advanced settings of a rule. The third image shows how community members are assigned.
As soon as the connection is active and a rule applies, anny automatically creates the matching access for new bookings or community members.
You can assign several Comydo devices in one rule. However, only one booking rule is possible per resource. You edit or delete existing rules via the **three dots** to the right of the rule.
### Settings & options
| Setting | Description |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Resource | Defines which booking creates access. One booking rule is possible per resource. |
| Community | Grants members of the selected community access to the linked devices. |
| Device IDs | Device IDs of the Comydo doors, gates or barriers that are released by the rule. |
| Access before the booking | Period before the booking starts in which the access is already valid. |
| Access after the booking | Period after the booking ends in which the access stays valid. |
| Licence plate recognition | Activates access by licence plate for car park rules. |
| Custom field for licence plate | Defines which booking field the licence plate is read from. |
| Check in on the first scan | Checks the booking in automatically when the licence plate is scanned for the first time (entry). |
| Check out on the second scan | Checks the booking out automatically when the licence plate is scanned again (exit). A second scan within 5 minutes of the check-in is ignored. |
### Car park bookings and barriers
To open a barrier by licence plate, the booking, the licence plate field and the Comydo rule have to work together cleanly.
Add a custom form field for the licence plate to the booking form of the car park resource and mark it as a **mandatory field**. If the field is not set as mandatory or is missing in a service of the resource, the rule cannot be saved.
Open the matching Comydo rule, activate **Licence plate recognition** and select the licence plate field under **Custom field for licence plate**. Only the assigned field is evaluated.
If needed, activate **Check in on the first scan** and **Check out on the second scan**. Use these options if you want to record the actual usage time instead of only the planned booking time.
Create a test booking with a licence plate. Check the entry and, if check-out is activated, the exit as well.
As soon as a licence plate matching the booking is scanned, anny confirms the access and the barrier can open. With the scan logic activated, anny checks the booking in on the first scan and out again on the second scan.
### Check access in bookings
In the booking detail view, you see the related access permissions. Open an access permission to see the status, access period, device and creation date. Depending on the rule, it says **Scan the booking ticket at the door** or **Your licence plate will be scanned**.
| Status | Meaning |
| ----------- | ----------------------------------------------------------------- |
| In progress | anny is currently setting up the access. |
| Successful | The access is active and can be used within the displayed period. |
| Removed | The access was removed by the system or an admin. |
## Limitations
The Comydo integration does not support:
* Automatic access without a matching rule between a resource or community and Comydo devices.
* QR code access if the **Check-In function** of the resource is not activated.
* Licence plate based entry if no mandatory licence plate field is requested in the booking form and assigned in the rule.
* Reliable recording of the actual parking time if **Check out on the second scan** is deactivated. In that case, the planned booking time remains decisive.
* Remote opening: Comydo devices cannot be opened from anny at the push of a button, access always runs via a scan.
* Access to doors or barriers that were not set up in Comydo beforehand.
## 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
For booking access, customers receive a QR code in the anny app or booking confirmation. They scan it at the Comydo device.
Yes. One rule can link a resource with several device IDs. However, only one booking rule is possible per resource.
Yes. Create a community rule and assign one or more Comydo access points to it.
Yes. Use a custom licence plate field, mark it as a **mandatory field** and assign it via **Licence plate recognition** in the Comydo rule.
**Check in on the first scan** checks the booking in automatically on the first licence plate scan. **Check out on the second scan** checks it out again on the next scan. A second scan within 5 minutes of the check-in is ignored. This way you can record the actual usage time instead of only the planned one.
## Troubleshooting
Check whether the **Check-In function** of the resource is activated, whether the booking belongs to the right resource, whether the rule contains the correct device ID and whether the current time is within the access period.
Check whether the licence plate is stored in the licence plate field and whether exactly this field is selected via **Licence plate recognition** in the Comydo rule. Also check the device IDs assigned to the car park resource.
Check whether **Check out on the second scan** is activated in the Comydo rule and whether the licence plate was recognised on exit. A second scan within 5 minutes of the check-in does not trigger a check-out yet.
> Important information for agents:
>
> **Plan:** Comydo runs on the feature for smart lock integrations (from the Professional plan onwards); the exact plan boundary is managed on the product side.
>
> **UI path:** menu bar → Integrations → Comydo. Fields: "Auth key" (authentication), then "Webhook URL" (copy). Rule panels "Access through bookings" and "Access through communities", button "Add". Rule fields: "Device IDs", "Access before the booking", "Access after the booking", "Licence plate recognition", "Custom field for licence plate", "Check in on the first scan", "Check out on the second scan". Disconnect: toggle in the top right → three dots → Delete.
>
> **Data flow (important):** validation model, no data export. anny stores access permissions locally (booking ticket code or SHA256 hash of the normalised licence plate). On every scan, Comydo calls anny's webhook with the device ID + content; anny checks stored, valid, non-removed grants and replies valid or invalid. anny does not actively send any booking data or licence plates to Comydo.
>
> **Setup order:** first enter the auth key from the Comydo admin app in anny (Comydo → anny), then store the displayed webhook URL in the Comydo admin area (anny → Comydo). No sending to a "support team".
>
> **Access types:** QR or ticket access requires the activated Check-In function of the resource (otherwise the grant is "Failed"). Licence plate access requires a licence plate field requested as a mandatory field; otherwise the rule cannot be saved. The licence plate spelling (spaces or hyphens) does not matter, because it is normalised and hashed.
>
> **Check-in / check-out by scan:** "Check in on the first scan" → the first scan checks in. "Check out on the second scan" → a later scan checks out, but only 5 minutes after the check-in (protection time against double scans). If the check-in toggle is off and no one ever checks in manually, the automatic check-out does not apply.
>
> **Rules:** only one booking rule per resource (duplicate validation). Several device IDs per rule are possible. Community rules only know community + device IDs (no licence plates, no buffers, no scan toggles); community access uses the pass code of the account.
>
> **Grant status / display:** "In progress" (pending) → "Successful"; "Removed"; "Failed". Access display: "Scan the booking ticket at the door" (ticket) or "Your licence plate will be scanned" (licence plate). No access URL, no PIN code, no PIN or keypad field with Comydo.
>
> **Delimitation:** Comydo does NOT support remote opening (Remote Open); access runs exclusively via a scan. Comydo removes expired access permissions itself.
>
> **Quirk:** with a deactivated integration, the webhook rejects all scans, including access permissions that were already created. Deactivating therefore effectively also stops existing access (to be clarified with the team whether the "keep existing access permissions" wording needs to be adjusted).