Verkada access control

About the Verkada integration

Integrate Verkada with Robin so that a badge swipe at a Verkada-controlled door checks users into Robin automatically. This article shows how to set up and use the integration.

Prerequisites

The Verkada integration requires Verkada Access (cloud) and an API key for your Verkada account. The API key needs these permissions:

  • Access control-read/write permission
  • Core command permission

To get your API key, contact your Verkada representative.

How it works

When users swipe their badges at Verkada-controlled doors, Robin checks them into the office automatically. This makes check-in faster and adds data to attendance and usage analytics.

  • If a user has a desk reservation, Robin checks them into their desk and shows them as "Checked in or confirmed on-site".
  • If a user has no desk reservation when they swipe their badge, Robin creates a visit, checks it in and shows the user as "Confirmed on-site".
  • Admins see a real-time list of who is in the office on the Daily Roster, and see who checked in with a badge swipe.
  • Badge data shows in analytics as a desk check-in, as a count toward "confirmed on site", or both. It also shows the check-in method.

Set up the Verkada integration

  1. In the web dashboard, go to Manage > Integrations on the left.
  2. On the Integrations page, scroll down to the "Access Control" section.
  3. Find Verkada and select Connect to start the setup.
  4. Under "Authentication," select your region.Screenshot 2025-02-14 at 4.06.00 PM.png
  5. Enter your public Verkada API key. If you do not have a public API key, contact your Verkada representative.
  6. When your Verkada account connects, you see a table that maps Verkada Door IDs to buildings and floors.
  7. In the table, configure the buildings, doors and floors where you want automatic check-ins through Verkada.
  8. Select Save.
  9. Review and confirm your changes, then select Save.

Badge data handling

Robin pulls event data at regular intervals (every 5 minutes). Robin discards all data except the timestamp and door ID before further processing.

FAQ

Answers to common questions about badge swipe data in Robin.

Why integrate badge swipe data with Robin?

Badge swipe data makes check-in and attendance data more accurate. This helps most in organizations that use assigned desks, have low check-in rates or have users who come to the office without a desk reservation.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share