Connect Tap Tag to Kisi and automate any workflow
1. Choose a Trigger
An event that starts an automation
2. Choose an Action
The event an automation performs after it's triggered
Endless possibilities
How Zapier works
Zapier makes it easy to integrate Tap Tag with Kisi - no code necessary. See how you can get setup in minutes.
Select a trigger from Tap Tag
A trigger is an event that starts your Zap and runs the workflow. For example, with Tap Tag, a trigger could be "New Contact Form Submission."
Setup an action from Kisi
An action is what takes place after the automation is triggered. For example, with Kisi, the action could be "Create Member."
That’s it! You just connected Tap Tag to Kisi
With Zapier, it’s never been easier to connect your apps together and automate your most tedious work. Save hours every month.
Connect Tap Tag 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
With Zapier, you can automate every part of your lead funnel and give yourself the best chance at converting leads. Automate everything from lead capture to outreach to reporting—and close more deals as a result.
Connect Tap Tag 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.
Choose a Trigger
Start here
Start here
Choose an Action
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.
- New Contact Form Submission
Triggers when the contact form is submitted.
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
- Fetch Group
Fetch all Groups available on a User Account
- 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
- The email of the member.Required
- The name of the memberRequired
- password of userRequired
- terms and conditions
- The name of the memberRequired
- The description of the lockRequired
- The place ID of the lockRequired
- The latitude of the lock.
- The longitude of the lock.
- Whether the lock is geofence restricted. Geofence restriction enforces that users may only unlock when they are near the lock.
- Whether reader restriction is enabled. Reader restriction enforces that users may only unlock when standing in front of the door.
- Whether the lock is time restricted. Time restriction enforces that users may only unlock at specific hours.
- The position of the lock, determining the sort order of the locks.
- The integration ID of the lock. Only used by integration-based locks. The only integration that is currently supported is Smartalock. When this field is set, all unlocks will go through the integration.
- The floor ID of the lock
- Whether the lock is marked as a favorite by the user. Only shown if requested.
Related categories