About the Gallagher integration
Integrate Gallagher with Robin so that a badge swipe at a Gallagher-controlled door checks users into Robin automatically. This article shows how to set up and use the integration.
Note
The Gallagher integration requires an API key for your Gallagher account and Gallagher Command Center, with Rest API and API Gateway usage.
How it works
When users swipe their badges at Gallagher-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.
Before you start
Know these points before you set up the integration:
- An operator must create the REST Client.
- An operator is a cardholder assigned to an operator group. The operator group gives them operator privileges.
- You must give Robin the API key that the interface shows. Robin needs it to connect.
Part 1: Set up Gallagher
In Gallagher, create a REST Client, configure the Command Center for cloud connection and find the email field.
Set up the Gallagher REST API
To create a REST Client in the Configuration Client:
- Go to Configure → Services & Workstations. A new window opens.
- Right-click an empty space and select New → REST Client.
- Give the REST Client a name.
- Go to the API Key tab.
- In the drop-down menu, select the REST Client Operator named "REST Operator". This operator is preconfigured for you.
Configure Gallagher Command Center for cloud connection
To turn on cloud connectivity, configure 2 items in the Command Center:
- Create the "Command Center Cloud" item.
- Let the "REST client" use the cloud API gateway.
Create the Command Center Cloud item
- Open Configuration > Configure > Services & Workstations.
- In the new window, Right-click and select New > Command Center Cloud.
- On the General tab, give it a name.
- On the Configuration tab:
- Select the Enable Gallagher API Gateway box.
- Select the region closest to you.
- Select Apply to save the configuration.
Let the REST client use the Cloud API gateway
To let a REST client connect through the Gallagher API gateway:
- Go to Configuration client > Configure > Services & Workstations.
- Select the REST client you want to connect.
- Go to the Connections tab.
- Select Allow connection via the Gallagher API Gateway.
Find the email field identifier
In addition to the API key and Gallagher API Gateway region, you must give Robin an email field identifier. This is the field where Gallagher stores user email addresses.
To find the email field:
- Go to Command Centre → Viewers → Cardholder Viewers.
- Find the Cardholder Details section.
- Find the field that stores email addresses (usually labeled "email"). Give this field name to Robin.
You can set up the integration first without the email field. But Robin does not pull or process badge events until you give Robin the field.
When you complete these steps, Gallagher is configured for API and cloud connectivity with Robin.
Part 2: Set up Robin
- In the web dashboard, go to Manage > Integrations on the left.
- On the Integrations page, scroll down to the "Access Control" section.
- Find Gallagher and select Connect to start the setup.
-
In the authentication section, select Connect account.
- Enter your public Gallagher API key.
- When your Gallagher account connects, you see a table that maps Gallagher Door IDs to buildings and floors.
- In the table, configure the buildings, doors and floors where you want automatic check-ins through Gallagher.
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 Genea API call for each badge swipe event. Make sure your API call limits and quotas allow for your expected usage.