Integrate Kisi with Slack
This is a Kisi-built integration, maintained and supported by Kisi.
As an admin, you can easily integrate Kisi with Slack to enable real-time Kisi event and custom incident policy notifications within your Slack channels. This allows you to stay fully informed, without the hassle of switching between multiple apps or worrying about missing essential updates. Setting up the integration takes less than 2 minutes.
Prerequisites
- A Slack account with permission to install apps in your workspace (or approval from a Slack workspace admin)
- Permission to post in the Slack channel you want to receive notifications in
- Kisi administrator access rights
- Each Kisi organization can have only one Slack integration.
- Each Slack workspace can be connected to only one Kisi organization.
Set up the integration
- Before configuring the integration, ensure that you have a Slack channel designated for receiving notifications
- Sign in to Kisi
- Click the integrations icon (3x3 grid of dots) > Add Integration
- Provide a name for your integration and select Slack from the dropdown
- Click on Add
- When prompted, choose the Slack channel where you want the notifications to be sent
- Click Allow
- In the Edit Channel Configuration dialog, choose what the channel receives:
- Kisi events - under Events, select specific Kisi events (e.g.
lock.unlock), or select All to receive notifications for all events - Incident policy notifications - turn on Allow incident policies notifications and select the custom incident policies to post to this channel. Leave the list empty to post all incident policies.
- Kisi events - under Events, select specific Kisi events (e.g.
- (Optional) Under places, add one or more places to filter notifications by. Leave it empty to include all places.
- Click Save
- Trigger an unlock event to test the integration. A notification should appear in your Slack channel.
Notifications are posted as plain-text messages that contain the Kisi event message.
- Each channel receives either Kisi events or incident policy notifications, not both. To receive both, set up separate channels.
- If you filter a channel by place, it only receives events directly related to that place (e.g. door unlocks) and incidents that happen at that place. It won't receive organization-scoped events (e.g. user or access link creation). To receive these, add a separate channel without place filtering.
- The bot is a one-way notification feature to receive events from Kisi.
Manage channels
You can send different types of notifications to separate channels. Open your Slack integration in Kisi to see all connected channels in the Channels table.
- Add a channel - click Add Channel, choose the channel in Slack, click Allow, then configure it as described in Set up the integration
- Edit a channel - click the channel's row, update its events, incident policies or places, then click Save
- Delete channels - select the channels' rows, click delete and confirm in the Delete Channels dialog
If a channel event and an incident policy notification cover the same activity, you may get the same notification in two channels. To prevent duplication, either disable the custom incident policy or remove the corresponding event from the channel's events.
To review or revoke the Kisi app in Slack, click Configure in Slack on the integration page.
Channel statuses
The Status column in the Channels table shows the state of each channel:
| Status | Meaning |
|---|---|
| Ok | The channel is configured and receives notifications |
| Incomplete | No events are selected and incident policy notifications are turned off |
| Disabled | The channel is turned off and doesn't receive notifications |
| Error | Slack rejected a message, so the channel was turned off. See Troubleshooting. |
A new channel starts with no events selected and shows Incomplete with the warning "Please select events or allow incident policies". Nothing is posted to the channel until you save events or incident policies.
Troubleshooting
A channel shows the Error status
If Slack rejects a message, Kisi turns off the channel and marks it Error. This can happen when:
- The channel was archived or deleted
- The Kisi app was removed from the Slack workspace
- The webhook was revoked in Slack
- Posting to
#generalis restricted in your workspace
To fix it, click the channel's row. The dialog shows "The webhook URL is invalid". Click Reauthorize and complete the Slack authorization again. Reauthorizing turns the channel back on.
Setup or authorization errors
- Slack Authorization failed - you canceled or denied the Slack consent screen. Click Retry and click Allow in Slack.
- Slack access code is invalid. Please try again. - the authorization code expired or is invalid. Start the authorization again.
- Workspace is already in use - the Slack workspace is already connected to another Kisi Slack integration. Use that integration, or delete it first.
- There can be only one Slack installation per organization - your organization already has a Slack integration. Add more channels to the existing one instead.
Uninstall the integration
- Sign in to Kisi
- Click the integrations icon (3x3 grid of dots) and select your Slack integration
- Click Delete and confirm
Deleting the Slack integration in Kisi also uninstalls the Kisi app from your Slack workspace and removes all channel configurations.