Skip to main content

​
At a glance

  • Destinations: Slack (incoming webhook URL, or bot token with chat:write + channel name), Microsoft Teams (Workflows webhook URL), Discord (webhook URL), Google Chat (webhook URL).
  • Defaults: a new connector routes no events until they are enabled in the routing matrix. This includes Auto-Heal events.
  • Delivery rule: a connector receives an event only when both the connector and that event’s routing rule are enabled.
  • Start generation from Slack: @checksum <what to test> in a thread. The whole thread becomes the agent’s instructions.
  • Permissions: the workspace admin role is required to add connectors or install the Slack app.
Developer guide
Chat-platform webhooks and tokens, the event reference, and @checksum usage

​
Get a webhook URL or bot token from your chat platform

The webhook URL or bot token comes from the destination chat platform, not from Checksum. Create it in Slack, Teams, Discord, or Google Chat, then paste it into the Checksum connector form (Connector setup). The steps for each platform follow. Check each platform’s official docs for the current UI.
Slack supports two setup methods. Use either one.

​
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.

​
Supported channels and credentials

You can have several 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 separately for each connector.
How Test Run Completed countsTest Run Completed reports the run’s outcome counts in five exclusive buckets: passed, failed, healed, bugs, and skipped. 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 ran.
New connectors route nothing by defaultNo events are enabled when you create a connector. It stays silent until you turn events on in the routing matrix (see Connector setup, step 3). This applies to Auto-Heal events too.
Separate the noisy eventsBug Detected and Test Generated can fire often on an active project. Route them to a dedicated channel so they don’t drown out rarer alerts like Health Report Ready.
Bug notifications include stable links to the bug’s page in the web app, for example https://app.checksum.ai/#/health-dashboard/bug/BUG-42. To get a focused view (for example, Checkout vs Admin), segment health reports by tags.
  • Subscriptions are per connector. Several connectors of the same type are allowed.
  • Bug notification link format: https://app.checksum.ai/#/health-dashboard/bug/BUG-42.
  • Health reports can be segmented by tags.

​
Start generation by mentioning @checksum

When someone mentions @checksum in a channel where the app is installed:
  1. Checksum reads the thread context: the mention plus recent messages in that thread.
  2. A generation agent session starts against your Checksum project.
  3. The bot replies in the thread with a link to track the session in the web app.
  4. When generation finishes, the tests are delivered the same way as other generation flows. That’s usually a PR to your tests repository, when the session has pull-request context.
Example mentions
The bot uses the whole conversation, not just the mention line, so thread replies before @checksum become part of the agent’s instructions.

​
@checksum usage tips

▦
In the Checksum web app
Connector setup, routing, and installing the Slack app

​
Two kinds of chat integration

They’re independent, so you can use both. Workspace admin role is required to configure either. To turn bugs into Jira, Linear, or ClickUp tickets with two-way status sync, use Issue Tracker Sync instead. It’s set up in its own section of Settings → Integrations.

​
Notification connectors

​
Connector setup

Connectors are managed in Settings → Integrations, in the Notification Connectors section. You need the workspace admin role to add, edit, or remove them.
1

Add a connector

Pick a channel type, give the connector a name (names must be unique in the workspace), and paste the webhook URL or bot credentials.
Channel type is permanentYou can’t change a connector’s channel type after creating it. To move a connector to another platform, delete it and create a new one.
2

Test the connection

Every connector has a Send test notification action that posts a sample message. Use it to confirm the connector works before relying on it.
3

Choose which events to route

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

Enable or disable

You can pause a connector without deleting it. A disabled connector receives nothing, whatever its routing rules say.
The connector list shows a Last used timestamp for each connector, which is a quick way to confirm it’s actually firing.
Secrets are maskedAfter creation, webhook URLs and bot tokens are masked. Only the last few characters of a webhook URL are shown, and bot tokens are hidden entirely. When editing a connector, leave a secret field blank to keep the existing value. Only type in it to replace the secret.
No undoDeleting a connector is permanent and also removes its routing rules.

​
Connector troubleshooting

​
Slack @checksum bot

The @checksum Slack bot lets your team start test generation from Slack. It’s the same capability as /checksum generate on a GitHub pull request, without leaving the channel.

​
Install the Slack app

Requires workspace admin access.
1

Open the Slack card

In the Checksum web app, go to Settings → Integrations and find the Slack card.
2

Click Add to Slack

Complete the Slack OAuth flow and choose the workspace.
3

Invite the app

Invite the Checksum app to each channel where your team should be able to use @checksum.
Once connected, the settings page shows the connected workspace name and team ID.
Only your own workspacesInstall the bot only in Slack workspaces your organization owns. The bot can only see channels it has been invited to.

​
Slack webhooks vs bot

The bot doesn’t replace notification connectors. Configure connectors separately for automated health reports, bug alerts, and run summaries. When both are set up, notification messages are formatted differently for each event type (health reports, bug detected, auto-heal batches, and so on), so you can tell them apart at a glance.

Generate from Slack

How a Slack thread becomes tests.

Feature Health Dashboard

Where bug and health events come from.

Auto-Healing

The batches behind Auto-Heal events.

Security & Access

Roles and what each integration can see.