cairnkit for Slack
When a product tour points at UI that is not on the page, the guide stops there and the person following it is stuck. This tells you, in the channel you already read.
What it sends
- Broken anchors. A tour looked for something that was not there. The message names the anchor, the step, the route and the run, so it is actionable from the notification alone
- Tour copy changes, optionally. New wording appeared in production — useful when the person who writes the copy is not the person who deploys it
- A weekly report, optionally. What ran, what finished, what broke
What it will never send
Completion rates moving, tours started, or anything else that changes on its own. Those are worth looking at when you open the dashboard; they are not worth interrupting someone for, and a channel that cries wolf is one people mute before the real alert arrives.
Every alert is deduplicated. One broken anchor on a busy page is one message, not one per visitor.
What it can see
Nothing in your Slack. The app asks for a single scope — incoming-webhook — which lets it post to the one channel you pick and grants no ability to read messages, list channels, or see who is in them.
It also holds nothing of your users. cairnkit records how your tours performed, not who followed them; the privacy policy lists every field.
Installing it
- Create an account and add a project, or sign in to one you already have
- Open the project, go to Settings, and press Add to Slack
- Pick the workspace and the channel. Slack sends you back, and a test message arrives
- Tick which alerts that channel should receive
One project connects to one channel, so staging noise can go somewhere other than the channel people actually read. Disconnecting is one button and takes effect immediately.
Removing it
Disconnecting in cairnkit stops everything from our side at once — we delete the webhook and nothing is ever posted again. The app itself stays listed in your Slack until someone removes it there, under Apps in your workspace settings.