Triggers and actions reference

This reference guide provides detailed information about all available Kisi triggers and actions in Zapier, including required fields, optional fields, and practical use cases.

Available Kisi triggers

User triggers

User triggers fire when specific events happen to users in your Kisi organization. These triggers start automated workflows based on user-related activities, allowing you to respond immediately to changes in your user base.

New User

Details

Triggers when a new user is added to your Kisi organization.

Required fields:

• Organization ID (automatically configured during setup)

Optional fields:

• None (trigger fires automatically for all new users)

What to use it for:

• Automated onboarding workflows when new team members join
• Syncing new users to external databases or CRM systems
• Creating access links or invitations for new hires

Example workflows:

• New user > Create Slack channel for new hire > Send welcome email > Add to appropriate access groups
• New user > Log details in Google Sheets > Create temporary access link > Notify facility manager

Available Kisi actions

Create actions

Create actions add new users, access links, or unlock schedules to your Kisi system by using information from the trigger event. For example, when a new employee is added to your HR system (trigger), the workflow can take their name and email from that trigger data to automatically create a Kisi user account. These actions transform trigger data into seamless onboarding and access provisioning.

Create New User

Details

Creates a new user in your Kisi organization.

Required fields:

• Email address
• Name (first name and last name)

Optional fields:

• Image URL (profile picture)
• Password Flow Enabled (only relevant for SSO organizations)

What to use it for:

• When a new employee is added to your HR system
• When someone purchases a gym membership through your booking platform
• When a new member signs up through your coworking space website

Create Invite

Details

Creates a user and sends an email invitation to join a group in Kisi.

Required fields:

• Email address
• Group ID (the specific group to invite the user to)

Optional fields:

• Name
• Notify the user
• Valid from/until

What to use it for:

• When a contractor is assigned to a project in your project management tool
• When someone books a meeting room that requires special access
• When a new tenant signs a lease in your property management system

Create Access Link

Details

Generates a temporary access link for visitors or temporary access.

Required fields:

• Name (user's name)
• Group ID (the specific group to invite the user to)

Optional fields:

• Valid from/until
• User's email address
• Phone
• Generate an Access Link
• Generate a QR code (online for yes, offline for no)

What to use it for:

• When someone schedules a meeting in your calendar (Google Calendar, Outlook)
• When a delivery is scheduled in your logistics system
• When a maintenance appointment is booked through your facility management platform

Create Unlock Schedule

Details

Creates a scheduled unlock event for specific doors.

Required fields:

• Lock ID (which door to unlock)
• Starts at (when to unlock)
• Ends at (when to lock)

Optional fields:

• Name

What to use it for:

• When a class or event is scheduled in your booking system
• When cleaning services are booked for specific times
• When recurring office hours are set in your facility management system

Unlock Lock

Details

Immediately unlocks a specific door.

Required fields:

• Lock ID (which door to unlock)

What to use it for:

• When a delivery driver arrives and checks in through your delivery app
• When an emergency alert is triggered in your security system
• When a visitor checks in at your front desk system

Delete actions

Delete actions remove users or role assignments from your Kisi system by using information from the trigger to identify what should be deleted. For example, when an employee is terminated in your HR system (trigger), the workflow receives their email address from that event. Since Kisi delete actions require specific user IDs rather than email addresses, you'll typically need to first use a Search action to find the user ID, then use that ID to delete the user. This creates a multi-step workflow: trigger provides email → fetch user by email → delete user by ID.

Delete User

Details

Removes an existing user from your organization.

Required fields:

• User ID

What to use it for:

• When an employee is terminated in your HR system
• When a gym member cancels their subscription
• When a tenant's lease expires in your property management system

Delete Role Assignment

Details

Removes role assignments from users.

Required fields:

• Role Assignment ID

What to use it for:

• When someone's project ends in your project management tool
• When a temporary worker's contract expires
• When someone's department changes in your HR system

Search actions

Search actions retrieve information about users or their permissions from your Kisi system by using identifiers from the trigger to look up additional data needed for subsequent actions. For example, when your CRM removes a membership (trigger), it only provides the customer's email address. However, to delete that user from Kisi, you need their user ID. A Search action takes the email from the trigger, queries Kisi to find the matching user, and returns the user ID. This ID can then be used in other actions. Search actions are essential bridge steps that convert trigger data into the specific information required by other Kisi actions.

Fetch Role Assignment

Details

Retrieves current role assignments for users.

Required fields:

• User ID

Optional fields:

• Successful if no search results are found? (True if yes, False if no)
• If multiple search results are found, choose one:
  • Return first search result
  • Halt the run
  • Return all results as line items

What to use it for:

• When you need to verify someone's current access before making changes
• When generating compliance reports triggered by audit schedules
• When an employee changes departments and you need to update their permissions

Fetch Users

Details

Retrieves user information from your organization.

Required fields:

• Email

Optional fields:

• Successful if no search results are found? (True if yes, False if no)
• If multiple search results are found, choose one:
  • Return first search result
  • Halt the run
  • Return all results as line items

What to use it for:

• When your external system only provides email addresses but you need user IDs
• When validating if someone already exists before creating a new user
• When syncing user data between your CRM and access control system