Automate with Zaps
Zapier is a workflow automation platform that connects thousands of apps and services. With Kisi's Zapier integration, you can create automated workflows (called "Zaps") that trigger actions in Kisi based on events from other apps, or use Kisi events to trigger actions in other services.
Kisi currently offers 1 trigger and 9 actions on Zapier, enabling powerful automation possibilities for access control, member management, and workflow optimization.
Core concepts
Understanding these key concepts will help you create effective automations:
Triggers
Triggers are events that start a Zap. When a trigger event occurs in an app, it signals Zapier to begin the automation workflow. Kisi has the following triggers available in Zapier:
For more advanced automation scenarios, you can also use webhooks to create custom triggers based on any Kisi event, providing greater flexibility and real-time responsiveness for complex workflows.
Actions
Actions are tasks that Zapier performs in response to a trigger. These are the automated steps that happen after a trigger event. Kisi has the following actions available in Zapier:
- Create Access Link
- Create Invite
- Create New User
- Create Unlock Schedule
- Delete Role Assignment
- Delete User
- Unlock Lock
- Fetch Role Assignment
- Fetch Users
Zaps
A Zap is the complete automation workflow connecting a trigger to one or more actions. For example: "When a new member joins in my CRM (trigger), add them to my Kisi organization and grant access to specific doors (actions)."
Common use cases
Member onboarding automation
Automatically create access when new members join through your CRM or membership management system:
- Trigger: New member added in CRM (Salesforce, HubSpot, etc.)
- Actions: Create Invite
Coworking space management
Sync membership status between coworking platforms and access control:
- Trigger: New booking in Skedda or OfficeSpace
- Actions: Create Access Link
Fitness studio integration
Connect fitness management platforms with access control:
- Trigger: New member registration in PushPress or Mindbody
- Actions: Create Invite
Access logging and reporting
Monitor new user additions and sync data to external systems:
- Trigger: New User
- Actions: Log user details in Google Sheets > Send notification to Slack > Update member database in CRM
Automated user onboarding workflows
Create comprehensive onboarding sequences when users are added:
- Trigger: New User
- Actions: Create invite for specific groups > Create welcome access link > Schedule unlock for orientation time > Send notification to facility manager
Temporary access management
Create time-limited access for visitors or temporary staff:
- Trigger: New event in calendar (Google Calendar, Outlook)
- Actions: Create Access Link
Set up the integration
- Set up Zapier automation: Learn how to connect Kisi to Zapier and create your first Zaps with step-by-step examples.
- Triggers and actions reference: Complete reference guide for all available Kisi triggers and actions with field requirements and use cases.
Frequently asked questions
I only want certain users to get access.
You can control which users get access using Zapier's Filters feature. Set up conditions based on data from your trigger (like department, role, or custom fields) to only run Kisi actions for specific users. For example, filter by email domain to only create access for users with company emails, filter by CRM field to only grant access if "Access Level" equals "Premium", or filter by group membership to only process users assigned to specific teams. See Zapier's help center to learn more about those features.
Additionally, use Kisi's Group ID field in actions like Create Invite to grant access to specific areas or permission levels rather than organization-wide access.
I want to delay access until a certain condition is met.
Zapier offers built-in delay functionality that lets you postpone any actions until specific times or conditions are met. Use Zapier's Delay action to wait until a particular date (like an employee start date from your HR system) or add time delays between steps in your workflow. You can also set up Paths in Zapier to create branching logic where different conditions trigger different access scenarios. See Zapier's help center to learn more about those features.
Kisi actions themselves provide several time-based access controls. Use Create Unlock Schedule to automatically grant and revoke access at specific times, perfect for scheduled events or maintenance windows. Both Create Access Link and Create Invite include "Valid from/until" fields that let you set expiration dates for temporary access. For complex conditional logic beyond Zapier's built-in features, consider using webhooks for more advanced scenarios.
Can I trigger Kisi actions from my CRM?
Absolutely! Most major CRMs are supported by Zapier including Salesforce, HubSpot, Pipedrive, and many others. Common CRM triggers that work well with Kisi include new contact/lead created, deal won/closed, contact updated, and lead status changed. You can map these events to Kisi actions like Create Invite, Create Access Link, Delete Role Assignment, or Create New User.
The setup process involves choosing your CRM as the trigger app, selecting the specific event (new contact, updated deal, etc.), then mapping CRM fields like name and email to the corresponding Kisi action fields. You can use CRM custom fields to determine which Kisi groups to assign users to based on their role or access level. See the setup guide for detailed step-by-step instructions.
Can I have multiple Kisi actions in one Zap?
Yes! You can chain multiple Kisi actions together in a single Zap to create comprehensive workflows. For example, when a new employee is added to your HR system, you can set up a workflow that first uses Fetch Users to check if the user already exists, then Create New User if not found, followed by Create Invite to add them to the employee group, Create Access Link for temporary orientation access, and finally send a Slack notification to your facilities team.
Sometimes it might be easier to create multiple simple flows rather than one complex Zap, especially when different triggers need different logic or when you want to isolate failure points.