Notifications (Teams & e-mail)

Every run tells the team what happened, so nobody has to watch the terminal or the CI log. The framework posts a card to Microsoft Teams (and/or a message to Slack) for each distribution, and e-mails an HTML report after each AI test run.

What you will receive

Pick a message to see exactly what it looks like:

Step 1: Create a Teams Workflows webhook

winget install Microsoft.Teams

Microsoft retired Office 365 connectors in favour of Workflows (Power Automate). The framework posts to a Workflows webhook URL, as described in Microsoft: create incoming webhooks with Workflowsopen_in_new.

The screenshots below are from the Teams desktop app. Pink numbered boxes mark what to click, in order.

1. 1

   Open the Workflows app

   In the left rail select ⋯ (View more apps) ①, type Workflows and open it ②.

   

2. 2

   Open the templates

   On the Workflows Home tab, select Templates ①. If you want to post to a team channel, you can also start straight from the Send webhook alerts to a channel card.

   

3. 3

   Choose where the alerts should go

   Pick Send webhook alerts to a chat to post into a group chat (or your own chat while testing), or Send webhook alerts to a channel to post into a team channel. Older tenants call the channel template Post to a channel when a webhook request is received.

   

4. 4

   Select the chat (or team and channel), then Save

   Open the Chat drop-down ① and pick the conversation that should receive release cards. Then select Save ②. For the channel template you pick a Team and a Channel instead.

   

5. 5

   Copy the webhook link

   Teams shows “Workflow created” and opens Workflow details. Select Copy webhook link ①. You can come back to this page any time from Workflows → Home → Your workflows.

   

6. 6

   Save it as TEAMS_WEBHOOK_URL

   .env

   content_copy

   TEAMS_WEBHOOK_URL=https://prod-12.westeurope.logic.azure.com:443/workflows/.../invoke?api-version=2016-06-01&sp=...&sv=1.0&sig=...

   On GitHub Actions, add the same value as a repository secret (GitHub: using secretsopen_in_new).

Step 2: Enable it in environments.yml

Set the global defaults once, then switch channels on or off per environment:

notifications:                       # global defaults
  teams: { enabled: true,  webhook_url: "${TEAMS_WEBHOOK_URL}" }
  slack: { enabled: false, webhook_url: "${SLACK_WEBHOOK_URL}" }

android:
  environments:
    development:
      notifications:
        teams: { enabled: false }      # keep dev builds quiet
    production:
      notifications:
        teams: { enabled: true }

An environment's notifications block is deep-merged over the global one, so you only write what changes.

Step 3: Test the webhook

Send a test card before your first real run. A Workflows webhook accepts only Adaptive Card payloads. Plain { "text": … } fails with “Property 'type' must be 'AdaptiveCard'”. The framework always sends cards.

# Load the URL into this session (PowerShell does not read .env)
PS C:\my-app> $env:TEAMS_WEBHOOK_URL = "https://prod-12.westeurope.logic.azure.com:443/workflows/..."content_copy
PS C:\my-app> $card = @{ type="message"; attachments=@(@{ contentType="application/vnd.microsoft.card.adaptive"; content=@{ type="AdaptiveCard"; version="1.4"; body=@(@{ type="TextBlock"; text="Fastlane webhook test"; weight="Bolder" }) } }) } | ConvertTo-Json -Depth 10content_copy
PS C:\my-app> Invoke-RestMethod -Uri $env:TEAMS_WEBHOOK_URL -Method Post -ContentType "application/json; charset=utf-8" -Body ([Text.Encoding]::UTF8.GetBytes($card))content_copy
# No output = HTTP 202 Accepted. The card appears in the channel within a few seconds.

curl -sS -o /dev/null -w "%{http_code}\n" -X POST "$TEAMS_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"type":"message","attachments":[{"contentType":"application/vnd.microsoft.card.adaptive","content":{"type":"AdaptiveCard","version":"1.4","body":[{"type":"TextBlock","text":"Fastlane webhook test","weight":"Bolder"}]}}]}'
# → 202

During a real run the result is logged right after the lane finishes:

~/my-app $ bundle exec fastlane android distribute environment:stagingcontent_copy
...
[14:07:01]: Microsoft Teams notification sent (HTTP 202).
[14:07:01]: Fastlane completed successfully: distribute

[16:08:34]: Notification integration failed: Microsoft Teams webhook returned 401: ... — the webhook URL's signature (sig=) was rejected: the URL is incomplete or outdated. Copy the full URL again from the Power Automate trigger and update the webhook secret/env value.

Step 4 (optional): Slack

Create a Slack app with an incoming webhookopen_in_new for your channel, put its URL in SLACK_WEBHOOK_URL and set notifications.slack.enabled: true. Slack receives the plain-text version of each message (see the Slack tab above).

Step 5: E-mail the AI test report

After every App Testing agent run, the framework e-mails the HTML report shown above. It uses plain SMTP, so any provider works: Microsoft 365, Gmail (with an app password), Amazon SES or SendGrid.

notifications:
  email:
    enabled: true
    notify_on_success: true    # set false to e-mail only failures
    notify_on_failure: true
    recipients: "${TEST_ALERT_EMAIL_RECIPIENTS}"

[14:10:13]: [EmailNotifier] Test report email sent to qa-lead@example.com, dev-team@example.com
[14:10:13]: [EmailNotifier] SMTP_HOST not set; skipping email alert.

Troubleshooting