Nexudus is a coworking management platform that provides many features as for example that coworkers can book resources.
In this example it is shown how to build an integration for bookings in Nexudus, so that in KleverKey an existing user gets one or more permission with a time profile or non-existing users get an sign up invitation.
Enable the Nexudus Zapier app
- Sign into Nexudus (https://dashboard.nexudus.com) with your admin account
- Go to Integrations > Zapier (https://dashboard.nexudus.com/settings/integrations/zapier)
- Press "Connect" and follow the instructions
Create a lookup table in Google Sheets
The Zap needs to know for which KleverKey locks a coworker requires permissions to access a specific Nexudus resource. In this example it is the main entrance door and the meeting room door.
Because coworking members with subscriptions (to plans) usually already have access to common areas, we want to exclude those areas when they book an additional resource (2. row).
Coworking space guests require permissions for all locks leading to the booked resource (3. row).
|Nexudus Resource ID
|Nexudus Resource Comment
|Coworker is member
|KleverKey Lock IDs
|KleverKey Lock Comment
|Only meeting room
|Main entrance and meeting room
Sign into Google Sheets an create a lookup table according to the example above.
Create the Zap in Zapier
You already should have basic knowledge about creating Zaps in Zapier. Start with signing into Zapier and creating a new Zap.
The Zap starts with the "New Booking" trigger from Nexudus.
Because the booking event only contains minimal information about the coworker who made the booking, we need to load more details about the coworker in the next step.
Because the details about the coworker don't include a property that tells us about the membership status, we need a small coding step to do that. In this example we only check if the coworker has a contract or not. Depending on the use case, that check has to be modified.
Now we add a spreadsheet lookup action with the lookup table we created before.
The last action will create or update a booking in KleverKey. In KleverKey, this booking will lead to permissions or an email invitation for this coworker, depending on whether the coworker already has a KleverKey account or not.
The finished Zap should contain the following steps.