Skip to main content
Checksum can push platform events into your team’s existing chat tools, so test results and health updates show up where the team already works. These are configured as notification connectors in your workspace settings.

​
Supported Channels

You can have multiple connectors of the same type — for example, a #qa-alerts Slack channel for bugs and a #release Slack channel for run completions.

​
What You Can Be Notified About

Each connector subscribes to one or more event types, configured independently per connector.
Test Run Completed carries the run’s outcome counts as exclusive buckets — passed, failed, healed, bugs and skipped — and total is the sum of all five. Skipped tests count toward total, so a run that skips tests reports a total higher than the number of tests that actually executed.
New connectors route nothing by default. No events are enabled when a connector is created — it stays silent until you turn events on in the routing matrix (see Setup, step 3).
Some events are high-volume. Bug Detected and Test Generated can fire often on an active project — route those to a dedicated channel so they don’t drown out lower-frequency alerts like Health Report Ready.

​
Getting a Webhook URL or Token

The webhook URL (or bot token) belongs to the destination chat platform, not to Checksum. You create it on Slack / Teams / Discord / Google Chat, then paste it into the Checksum connector form. Below is the short path for each — follow each platform’s official docs for the current UI.
Slack supports two setup methods — use either.Incoming Webhook
  1. Go to api.slack.com/apps and create a new app (From scratch).
  2. Open Incoming Webhooks and toggle it On.
  3. Click Add New Webhook to Workspace and choose the channel.
  4. Copy the webhook URL (https://hooks.slack.com/services/...).
Bot Token
  1. Go to api.slack.com/apps and create a new app (From scratch).
  2. Under OAuth & Permissions, add the chat:write bot token scope.
  3. Click Install to Workspace and copy the Bot User OAuth Token (xoxb-...).
  4. In Slack, invite the bot to each target channel: /invite @your-app-name.
  5. In the Checksum connector, enter the token and the channel name.
A webhook is quickest for a single channel; a bot token can post to any channel it’s invited to.
  1. In Teams, open the target channel → ⋯ → Workflows.
  2. Add the Post to a channel when a webhook request is received workflow.
  3. Complete the steps and copy the generated webhook URL.
  1. Open the target channel → Edit Channel → Integrations.
  2. Click Webhooks → New Webhook.
  3. Name it, optionally pick the channel, then Copy Webhook URL.
  1. Open the target space → space name → Apps & integrations.
  2. Click Manage webhooks, add a webhook, and give it a name.
  3. Copy the generated webhook URL.

​
Setup

Connectors are managed in Settings → Integrations (Notification Connectors section). Workspace admin role is required to add, edit, or remove them.
1

Add a connector

Pick a channel type, give it a name (names are unique per workspace), and paste the webhook URL or bot credentials.
The channel type is locked after creation. To switch a connector from one platform to another, delete it and create a new one.
2

Test the connection

Every connector has a Send test notification action that posts a sample message, so you can confirm it’s wired up before going live.
3

Choose which events to route

Open the routing matrix and toggle each event on or off per connector. A connector receives an event only when both the connector and that event’s rule are enabled.
4

Enable / disable

Connectors can be paused without being deleted. A disabled connector receives nothing, regardless of its routing rules.
The connector list also shows a Last used timestamp for each connector — a quick way to confirm a connector is actually firing.
Webhook URLs and bot tokens are masked after creation — only the last few characters of a webhook URL are shown for identification, and bot tokens are hidden entirely. When editing a connector, leave a secret field blank to keep the existing value; only type in it if you want to replace the secret.
Deleting a connector is permanent and also removes its routing rules. There is no undo.

​
Troubleshooting

​
Next Steps