- Docs
- Administration
- Integrations
- Slack, Teams & WhatsApp
Slack, Microsoft Teams and WhatsApp
Chat notifications tell your team when a pipeline starts, passes or fails, when a task is created, and once a day how yesterday went. Slack and Teams post to a channel; WhatsApp sends approved templates to up to 20 phones.
In short
On this page you can
- Post a message to Slack or Teams when a pipeline starts, completes or fails.
- Alert the channel when a task, or a critical task, is created.
- Send a daily summary of yesterday’s runs and today’s open tasks at a chosen hour.
- Add
@here,@channelor a name to failure messages. - Send failures and the daily summary to phones through WhatsApp Business.
How to use it
- Create an incoming webhook in Slack or a Workflows webhook in Teams.
- Paste the URL in the settings dialog and click Test Connection.
- Choose the events under Notification Preferences and save.
- Click Send Test Message and check the channel.
- Run a pipeline; the result message follows when it ends.
Which events send a message#
All three channels share the same events. Each is a switch in Notification Preferences.
| Switch | Sent when | Slack / Teams default | WhatsApp default |
|---|---|---|---|
| Pipeline Started | A pipeline run starts. | Off | Off |
| Pipeline Completed | A run ends and every test case passed. The message shows total, passed, failed, pass rate and duration. | On | On, but see Finished runs |
| Pipeline Failed | A run ends and at least one test case failed or did not run. The message shows the first error. | On | On |
| Test Failed | Saved with the settings, but this version sends no separate message per failed test. Failed tests are reported by Pipeline Failed. | On | Off |
| Task Created | A task with any severity other than Critical is created. | On | Off |
| Critical Task | A task with severity Critical is created. | On | Off |
| Send Daily Summary | Once a day at the Summary Time hour. See daily summary. | Off | On |
A run sends either Completed or Failed, never both. Messages sent by background jobs, such as scheduled runs and the daily summary, are in English. Autonomous AI agents can also post their reports to these channels; that is set in the agent.
Pipeline Failed
Pipeline **Nightly regression** has failed!
Error: Element not found: Click Sign In
CC: @hereSlack#
Create the webhook in Slack
Create a new application in your Slack workspace, turn on Incoming Webhooks, and add a webhook for the channel. Copy the URL; it starts with
https://hooks.slack.com/services/.Enter it in SmartestQA
Open IntegrationsSlack and click Setup. Under Webhook Settings paste the Webhook URL and, for your own reference, a Channel Name (optional) such as
#qa-alerts. Click Test Connection.Success! and the channel receives “SmartestQA Slack integration test successful!”.
Choose events and mentions
Under Notification Preferences turn the events on or off. Pick a Summary Time (whole hours, 00:00 to 23:00) if you use the summary, and Mention on Failure: None,
@hereor@channel. Click Save.Check from the page
The page shows Active. Click Send Test Message any time to post a test with the saved webhook.
On the Slack page you can also switch events, the daily summary, the hour and the mention directly; click Save in the Unsaved changes bar. Integration Active turns all messages off without losing the webhook.
Microsoft Teams#
Create a Workflows webhook
In Teams open Workflows (Apps › Workflows, or a channel’s ••• menu › Workflows), choose the template Send webhook alerts to a channel, select the team and channel, and save. Copy the webhook URL from the workflow’s details.
Enter it in SmartestQA
Open IntegrationsMicrosoft Teams, click Setup, paste the Teams Webhook URL and click Test Connection.
The channel receives a card “SmartestQA connected”.
Choose events
Set the events, the Summary Time, and in Mention (Email or name) the person to name on failures, for example
user@company.com. Keep Enable Integration on and click Save.
Messages arrive as Adaptive Cards. If you paste an address of the retired Office 365 connector type (…webhook.office.com/webhookb2/…), the dialog and the page warn that messages may no longer arrive. Create a Workflows webhook instead.
WhatsApp Business#
Before you start#
Add a business number
In Meta Business Suite open WhatsApp Manager and add a business phone number. Note its Phone number ID (WhatsApp Manager › Phone numbers › ID), not the phone number itself.
Create a permanent token
Create a system user with a permanent access token that has the
whatsapp_business_messagingpermission.Create the templates
WhatsApp only lets a business start a conversation with a template Meta has approved. Create the four templates below in the Utility category, in the language you will use, with exactly these names, and wait for approval. The WhatsApp page lists them with their text and sample values, ready to copy.
| Template | Used for | Variables |
|---|---|---|
smartest_pipeline_failed | Pipeline Failed | project, pipeline, link |
smartest_pipeline_completed | Pipeline Completed | project, pipeline, passed, failed, link |
smartest_daily_summary | Daily summary | project, date, runs, passed, failed, link |
smartest_alert | Pipeline Started, Task Created, Critical Task, agent warnings | project, summary, link |
SmartestQA: the {{2}} run in project {{1}} failed. Report: {{3}} . This message was sent automatically by SmartestQA.Set up WhatsApp#
Fill the settings
Click Setup. In WhatsApp Business settings enter Phone number ID, Access token, Recipients (one number per line, international format such as
+905321234567, up to 20), SmartestQA address for links (report links start with it) and Template language (for exampleen,troren_US; it must match the approved templates).Choose events
Pick the events. Keep Finished runs: only when a test failed on unless you want a message for green runs. Under Advanced: template names and API you can use other template names (empty = default template) and, only for a corporate relay, another API address.
Test and save
Click Test Connection: each recipient gets Meta’s ready-made
hello_worldtemplate. Then Save.“Test message sent. Check the phones in the recipient list.” The test counts as passed when at least one phone received it; failed numbers are listed with Meta’s error.
Cost and content#
- Meta charges per template message. By default only failures and the daily summary are sent, and routine agent reports are skipped; only agent warnings and critical reports go out.
- Finished runs. Pipeline Completed is sent only for runs where every test passed. With Finished runs: only when a test failed on, those messages are skipped, so in practice you get Pipeline Failed for red runs and nothing for green ones.
- No test data. Messages carry only the project and pipeline names, counts and a report link.
- Last delivery error. When Meta refuses a message, the page shows Last delivery error.
The daily summary#
A background job runs at the start of every hour. For each channel with Send Daily Summary on, it sends the summary when the hour of Summary Time matches the server’s clock and the channel has not sent anything yet that day.
Daily Test Summary - 07 November 2026, Saturday
**Tests run yesterday:** 48
Passed: 45 | Failed: 3 | Rate: 93.8%
**Open Tasks:**
Open: 6
In Progress: 2
Critical: 1How each number is counted: daily summary formulas.
Another message earlier that day skips the summary
The “already sent today” check looks at the channel’s last message of any kind. If a pipeline message went to the channel at 07:00 and the summary is set for 09:00, that day’s summary is skipped. Pick an hour before the first run of the day. The check is per channel: Slack, Teams and WhatsApp each keep their own.
Mentions#
With a mention set, SmartestQA adds a last line CC: value to Pipeline Failed, Test Failed and Critical Task messages. Slack offers @here and @channel; Teams takes an email or a name. Completed, Started, Task Created and daily summary messages carry no mention.
Best practices#
Do
- Use a dedicated channel such as
#qa-alerts. - Keep Pipeline Started off for frequent pipelines.
- Use mentions only on channels that people watch.
- Send a test message after rotating a webhook.
Don’t
- Post to a channel with external guests: error texts may show URLs and names.
- Turn on every WhatsApp event: each message is billed.
- Share the webhook URL: anyone with it can post to the channel.
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai