About the Brivo integration
Integrate Brivo with Robin so that a badge swipe at a Brivo-controlled door checks users into Robin automatically. This article shows how to set up and use the integration.
Note
The Brivo integration requires an API key for your Brivo account and Brivo Access (cloud). To get your API key, contact your Brivo representative.
How it works
When users swipe their badges at Brivo-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 Brivo integration
- In the web dashboard, go to Manage > Integrations on the left.
- On the Integrations page, scroll down to the "Access Control" section.
- Find Brivo and select Connect to start the setup.
- Under "Authentication," select your region.
-
Enter your public Brivo API key. If you do not have a public API key, contact your Brivo representative.
-
In the Brivo sign-in pop-up window, enter your Brivo owner account credentials and select login.
Make sure your web browser allows pop-ups. If you get an error with your credentials, make sure you sign in with a username, not an email address.
- When your Brivo account connects, you see a table that maps Brivo Door IDs to buildings and floors.
- In the table, configure the buildings, doors and floors where you want automatic check-ins through Brivo.
- Select Save.
- Review and confirm your changes, then select Save.
Badge data handling
Robin receives API payloads with event data from the badging system. When the payload reaches Robin's edge, Robin discards all data except the email address, timestamp and door ID before further processing.
Robin uses 1 Brivo API call for each badge swipe event. Make sure your API call limits and quotas allow for your expected usage.
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.