Notifications

Overview

Notifications keep you informed about your workflow execution status in real-time. Configure alerts for workflow completion, failures, or custom conditions to stay up-to-date with test results without constantly checking the dashboard.

---

Why Use Notifications?

Real-Time Alerts

Get instant notifications when workflows complete or fail, without monitoring dashboard constantly.

Team Collaboration

Proactive Response

Audit Trail

---

Notification Types

Status Notifications

Alerts triggered by workflow status:

Event	Trigger	Use For
Workflow Started	When workflow begins execution	Tracking workflow start times
Workflow Completed	When workflow finishes (pass/fail)	Completion confirmation
Workflow Passed	When all steps pass	Success confirmation
Workflow Failed	When any step fails	Immediate failure alert
Workflow Timeout	When workflow exceeds time limit	Timeout detection

Custom Notifications

Trigger based on conditions:

• Specific step failures

• Data validation errors

• Performance thresholds exceeded

• Custom business logic

---

Notification Channels

Email Notifications

Send to email addresses:

Email Setup
├── Recipients: List of email addresses
├── Subject Template: Customize subject line
├── Body Template: Customize message content
├── Attachments: Include report files
└── Format: HTML / Plain text

When to Use: Team members, stakeholders, managers

Slack Integration

Send to Slack channels:

Slack Setup
├── Workspace: Select workspace
├── Channel: #testing, #devops, @individual
├── Message Format: Rich formatting
├── Thread: Group related messages
└── Mentions: Alert specific users

When to Use: Immediate team alerts, engineering channels

Microsoft Teams

Send to Teams channels:

Teams Setup
├── Workspace: Select tenant
├── Channel: Team channel name
├── Message Format: Adaptive cards
├── Mentions: Tag specific users
└── Card Options: Include graphs, summaries

When to Use: Enterprise environments, Teams users

Webhooks

Send to custom endpoints:

Webhook Setup
├── URL: Custom webhook endpoint
├── Method: POST / PUT
├── Headers: Authorization, custom headers
├── Payload: JSON data
└── Retry: On failure behavior

When to Use: Custom integrations, CI/CD systems

SMS Notifications

Send text messages:

SMS Setup
├── Recipients: Phone numbers
├── Message: Short text (SMS constraints)
├── Carrier: Mobile carrier
└── Priority: Standard / Urgent

When to Use: Critical failures, on-call engineers

---

Configuring Notifications

Setup for Workflow

1. Open workflow

2. Click "Notifications" or "Settings"

3. Click "Add Notification"

4. Choose trigger event:

   • Workflow started

   • Workflow passed

   • Workflow failed

   • On timeout

   • Custom condition

5. Select channel:

   • Email

   • Slack

   • Teams

   • Webhook

   • SMS

6. Configure recipients/destination

7. Customize message (optional)

8. Save notification

Example: Email on Failure

Notification Configuration

Trigger: Workflow Failed
Channel: Email
Recipients:
  - [email protected]
  - [email protected]
Subject: ⚠️ Test Failed: {workflow_name}
Include:
  - Error details
  - Step where it failed
  - Link to report

Example: Slack on Success

Notification Configuration

Trigger: Workflow Passed
Channel: Slack
Channel Name: #testing
Message: 
  "✅ {workflow_name} passed
   Duration: {execution_time}
   Tests: {total_tests} passed
   Report: {report_link}"

---

Message Templates

Available Variables

Use in notification messages:

Workflow Variables:
├── {workflow_name}
├── {workflow_id}
├── {workflow_status}
├── {execution_time}
├── {start_time}
├── {end_time}
├── {total_tests}
├── {passed_tests}
├── {failed_tests}
├── {skipped_tests}
├── {error_message}
├── {failed_step}
├── {environment}
├── {report_link}
└── {execution_url}

Template Examples

Email Template

<h2>Workflow Execution Report</h2>

<p>Workflow: <strong>{workflow_name}</strong></p>
<p>Status: <strong>{workflow_status}</strong></p>
<p>Duration: {execution_time}</p>

<h3>Results Summary</h3>
<ul>
  <li>Total Tests: {total_tests}</li>
  <li>Passed: {passed_tests}</li>
  <li>Failed: {failed_tests}</li>
  <li>Skipped: {skipped_tests}</li>
</ul>

<% if workflow_status == "FAILED" %>
<h3>Failure Details</h3>
<p>Failed Step: {failed_step}</p>
<p>Error: {error_message}</p>
<% endif %>

<p><a href="{report_link}">View Full Report</a></p>

Slack Template

✅ Workflow Passed
━━━━━━━━━━━━━━━━
Workflow: {workflow_name}
Duration: {execution_time}
Passed: {passed_tests}/{total_tests}
Environment: {environment}

View Report: {report_link}

Teams Template

{
  "@type": "MessageCard",
  "summary": "{workflow_name} - {workflow_status}",
  "themeColor": "0078D4",
  "sections": [
    {
      "activityTitle": "Test Workflow: {workflow_name}",
      "facts": [
        {
          "name": "Status",
          "value": "{workflow_status}"
        },
        {
          "name": "Duration",
          "value": "{execution_time}"
        },
        {
          "name": "Results",
          "value": "{passed_tests} passed, {failed_tests} failed"
        }
      ]
    }
  ],
  "potentialAction": [
    {
      "@type": "OpenUri",
      "name": "View Report",
      "targets": [
        {
          "os": "default",
          "uri": "{report_link}"
        }
      ]
    }
  ]
}

---

Advanced Configuration

Scheduled Notifications

Send digest notifications at specific times:

Digest Configuration
├── Frequency: Daily, Weekly, Monthly
├── Time: 9:00 AM Monday
├── Summary: All executions in period
├── Recipients: Distribution list
└── Format: Executive summary

Conditional Notifications

Send only when specific conditions met:

Conditional Logic
├── IF: Failed tests > 5
│   ├── THEN: Notify urgent channel
│   └── Escalate to @devops
├── IF: Performance degraded > 20%
│   ├── THEN: Notify performance team
│   └── Include trending data
└── IF: Production test failed
    ├── THEN: Page on-call engineer
    └── Include incident info

Notification Routing

Route based on workflow properties:

Routing Rules
├── Mobile Tests → #mobile-qa
├── API Tests → #api-testing
├── Performance Tests → [email protected]
├── Production Tests → on-call-engineer-pagerduty
└── Default → #general-testing

---

Real-World Notification Scenarios

Scenario 1: Development Team

Trigger: Any test failure
Notification:
├── Channel: Slack #development
├── When: Immediately
├── Message: Include failed step
├── Action: Link to fix issue
└── Frequency: Every failure

Scenario 2: Nightly Regression Suite

Trigger: Workflow completion
Notification:
├── Channel: Email → [email protected]
├── When: After nightly run (6 AM)
├── Include: Summary + detailed report
├── Attachment: Excel report
└── Frequency: Daily

Scenario 3: Production Smoke Tests

Trigger: Failure
Notification:
├── Channel: SMS → on-call
├── When: Immediately
├── Message: "PROD TEST FAILED: {workflow_name}"
├── Follow-up: Email with details
└── Escalation: Call if not acknowledged

Scenario 4: Performance Degradation

Trigger: Performance threshold exceeded
Notification:
├── Channel: Slack #performance
├── When: Execution completes
├── Include: Performance metrics
├── Comparison: Vs. baseline/trend
└── Action: Link to performance report

---

Notification Management

View Notification History

1. Open workflow

2. Click "Notification History"

3. See all sent notifications

4. Filter by type/date/status

Edit Notification

1. Open workflow notifications

2. Click notification to edit

3. Modify settings

4. Save changes

Disable Notification

1. Open workflow notifications

2. Toggle off or click disable

3. Notification disabled (can re-enable)

Delete Notification

1. Open workflow notifications

2. Right-click or menu

3. Delete

4. Confirm deletion

---

Integration with Other Tools

CI/CD Integration

Send notifications to CI/CD systems:

GitHub Actions:
├── Webhook URL: github-actions-webhook
├── Trigger: Workflow failed
└── Action: Fail CI/CD pipeline

Jenkins:
├── Webhook URL: jenkins-endpoint
├── Trigger: Workflow completed
└── Action: Trigger downstream job

GitLab CI:
├── API endpoint: gitlab-webhook
├── Trigger: Workflow passed
└── Action: Deploy to staging

Ticketing Systems

Create tickets from notifications:

Jira:
├── Auto-create issue on failure
├── Assign to: QA team
├── Labels: [test-failure, automation]
├── Description: Include error details
└── Link to: Test execution report

Azure DevOps:
├── Create work item on failure
├── Sprint: Current sprint
├── Tags: [test-failure]
└── Attachment: Screenshot/log

---

Best Practices

✅ Do

• Configure notifications for critical workflows

• Use appropriate channels for different teams

• Customize messages with relevant context

• Set up escalation for production failures

• Review notification logs periodically

• Test notification delivery

• Document notification policies

• Archive important notifications

❌ Don't

• Over-notify (too many alerts cause fatigue)

• Send sensitive data in notifications

• Use same channel for all workflows

• Ignore failed notifications

• Leave default generic messages

• Forget to test webhook integrations

• Configure and forget

• Miss critical failure alerts

---

Troubleshooting

Issue: Notifications not being received

Symptoms:

• Notifications configured but not received

• Missing email or Slack messages

Solutions:

1. Check notification is enabled

2. Verify recipient address/channel is correct

3. Check spam/junk folders (email)

4. Verify Slack channel exists and bot has access

5. Test notification manually

6. Check integration logs

Issue: Workflow status not reflecting correctly in notification

Symptoms:

• Notification shows wrong status

• Message content incorrect

Solutions:

1. Verify workflow completed successfully

2. Check message template variables

3. Review notification trigger condition

4. Check logs for workflow details

5. Re-test notification

Issue: Too many notifications

Symptoms:

• Receiving duplicate notifications

• Too frequent notifications

Solutions:

1. Check for duplicate notification configurations

2. Adjust trigger conditions to be more specific

3. Set notification frequency limits

4. Consolidate into digest notifications

5. Reduce notification recipients

---

Notification Best Practices by Team

Development Team

Configuration:
├── Channel: Slack #dev-alerts
├── Trigger: Workflow failed
├── Include: Error details, logs link
├── Frequency: Every failure

QA Team

Configuration:
├── Channel: Email + Slack
├── Trigger: Daily suite completion
├── Include: Summary report
├── Frequency: Daily 9 AM

DevOps/SRE

Configuration:
├── Channel: SMS + PagerDuty
├── Trigger: Production failure
├── Include: All details
├── Frequency: Immediate escalation

Management

Configuration:
├── Channel: Email
├── Trigger: Weekly digest
├── Include: Executive summary
├── Frequency: Monday 8 AM

---

Related Topics

• Scheduler

• Reports

• Action Types - Send Email

• Troubleshooting

• FAQs