Connect Checkfront to Kisi and automate any workflow
How Zapier works
Zapier makes it easy to integrate Checkfront with Kisi - no code necessary. See how you can get setup in minutes.
Select a trigger from Checkfront
Setup an action from Kisi
That’s it! You just connected Checkfront to Kisi
Connect Checkfront and Kisi to integrate crucial parts of your business
With Zapier, you can integrate everything from basic data entry to end-to-end processes. Here are some of the business-critical workflows that people automate with Zapier.
Automate your lead management and improve conversions
Connect Checkfront and Kisi to unlock the power of automation
With Zapier's 7,000 integrations, you can unify your tools within a connected system to improve your team's efficiency and deepen their impact.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- Booking Change
Triggers when a booking has been changed.
Try It - New Item
Triggers when an Item is created.
Try It - Events
Triggers when there's a new kisi event.
Try It - Whether the schedule is enabledRequired
- Whether to override other events of the same consequenceRequired
- Defines what happens to the scheduleable when the schedule is occuring. The unlock value only applies to schedules with scheduleable_type set to Lock. The permit value only applies to schedules with scheduleable_type set to ElevatorStop. Allowed values: unlock permit allowRequired
- The type of the schedulableRequired
- The ID of the schedulableRequired
- The type of the schedule
- Which region's holiday rules to follow for event generation
- Whether the events should consider observancesRequired
- New Booking
Triggers when a booking goes from a pre-booking status to "locked in".
Try It - Item Change
Triggers when an existing item has been changed.
Try It - The name of the memberRequired
- The URL to the profile picture of the member.
- Whether the member should receive emails. Can only be specified for organization members.
- Whether the member's corresponding user should be auto-confirmed on creation. Can only be specified for organization members.
- Whether the member is allowed to access locks and elevators. If the user is managed by SCIM, user access will be disabled unless both the access_enabled field and scim_access_enabled fields are set to true.
- Whether the member can login with password flow. Only relevant for organizations.
- Whether the member needs to activate the card to gain access.
- The notes for the member.
- The email of the member.Required