Notifications
Post a card to Slack, Google Chat, Microsoft Teams, Discord or your own webhook when a Live session ends, an Automate run finishes or an Accessibility scan completes.
Overview
Organization → Integrations → Notifications posts a message to a chat channel when something happens in Live, Automate or Accessibility. Each connected channel is a rule: a webhook URL plus the list of events it wants.
What you can be notified about
| Product | Event | When it fires |
|---|---|---|
| Live | Session ended | A Live session was closed — by the End button, by closing the tab, or by the idle timeout |
| Live | Session dropped | A Live session ended because of a fault — the device went unreachable, the video connection failed, the fleet was under maintenance |
| Automate | Run passed | An Automate session finished with no failures |
| Automate | Run failed | An Automate session finished with failing tests |
| Automate | Test could not finish | An Automate session ended because of a platform fault, not a failing test |
| Accessibility | Scan completed | A scan finished — however many issues it found |
| Accessibility | Scan could not run | A scan did not start or did not finish (for example, no scan browser was free) |
When you connect a channel you pick a preset — Only when something breaks (the failure events above) or Everything — or choose events one by one.
A scan that finds 500 issues has completed. "Could not run" means the platform failed, not your site. The same distinction applies to Automate: "Run failed" is your tests; "Test could not finish" is us.
What a card contains
Every card says what happened, on what, when, and why — not an id and a timestamp:
ℹ️ Live session ended
Live · Browser on Windows 11
Run by: [email protected]
Started: 7 Sep at 6:18 PM ← in each reader's own timezone on Slack
Duration: 24s
Reason: Closed by the tester
Open sessionAutomate cards lead with the build and test name and link to the video and logs; Accessibility cards show the pages, standard, browser, and either the issue count and score or the reason the scan could not run. The device model and OS appear on every card from a real device.
Connect a channel
Each channel has its own page with the exact clicks to get its webhook URL:
- Slack
- Google Chat
- Microsoft Teams
- Discord
- Custom webhook — raw JSON to any HTTPS endpoint
The TestKase side is the same for all of them:
- Open Organization → Integrations → Notifications and click Connect on the channel's card.
- Give the rule a name (for example QA alerts) and paste the webhook URL.
- Choose Only when something breaks, Everything, or pick events.
- Save. The card shows a tick and Connected.
Edit or remove a rule
Click the ⋮ menu on a connected card. Edit opens the rule with its saved name, events and URL. Reset deletes the rule and its URL.
One webhook is one channel. To send failures to #qa-alerts and everything else to #qa, create two rules with two webhooks.
Test Management notifications
Test Management events (test case created, cycle completed, and so on) are configured per project in the project's Settings → Notifications, not here. See Test Management notifications.
