> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Microsoft Teams Notifications

> Send GermainUX alerts and other notifications directly to a Microsoft Teams channel using a Teams Workflow webhook.

Integration
`Microsoft Teams Workflow webhook`

Availability
2026.2 or later

> **[Webhook](#create-a-webhook-in-microsoft-teams)**
>
> Create it in Teams

> **[Configure](#configure-germainux)**
>
> Point GermainUX at it

> **[Test](#test-the-notification)**
>
> Validate end to end

> **[Troubleshoot](#troubleshooting)**
>
> Fix common issues

## Overview

Configure Microsoft Teams notifications to allow GermainUX to send alerts and other notifications directly to a Microsoft Teams channel.

The integration uses a Microsoft Teams **Workflow webhook**:

GermainUX
HTTP Request
Microsoft Teams Workflow
Teams Channel

Configuration consists of two steps:

1. Create a webhook Workflow in Microsoft Teams.
2. Configure GermainUX to send notifications to the webhook URL.

## Create a Webhook in Microsoft Teams

In Microsoft Teams:

**1. Open the Team and Channel**

Open the **Team and Channel** where GermainUX notifications should be posted.

**2. Open More options**

Select **More options (...)** next to the Channel.

**3. Select Workflows**

Select **Workflows**.

**4. Choose the webhook template**

Search for and select: **Send webhook alerts to a channel**

**5. Configure the Workflow**

Configure the Workflow and select the Team and Channel that should receive GermainUX notifications.

**6. Save**

Select **Save**.

**7. Copy the webhook URL**

Once the Workflow is created, copy the generated **webhook URL**.

The webhook URL is the endpoint GermainUX will call when sending a notification.

> [!WARNING]
>
> Keep the webhook URL secure. Anyone with access to a usable webhook URL may be able to submit requests to the associated Workflow, depending on its authentication configuration.

## Configure GermainUX

In GermainUX, configure an HTTP-based action to call the Microsoft Teams webhook.

Go to:

Germain Workspace
Left Menu
Settings
Automation

Configure the action with the webhook URL generated by Microsoft Teams.

The request should use:

| Setting | Value |
| - | - |
| **Method** | `POST` |
| **URL** | Your Microsoft Teams Workflow webhook URL. |
| **Content Type** | `application/json` |

> [!NOTE]
>
> The exact request body must correspond to the payload expected by the Microsoft Teams Workflow.

## Configure the Message

Configure the Teams Workflow and GermainUX request so that useful information about the detected condition is included in the notification.

For example, a GermainUX notification may contain:

* Alert or issue
* Severity
* Application
* KPI
* Current value
* SLA threshold

> **Show all 13**
>
> * Error
> * Friction
> * Users or sessions affected
> * AI analysis
> * AI recommendation
> * Time detected
> * Link back to GermainUX

A simple notification could appear as:

> **GermainUX Alert**
>
> Application: Salesforce\\
>
> Issue: Response Time SLA Violation\\
>
> Severity: High\\
>
> Response Time: 8.2 seconds\\
>
> Users Affected: 143\\
>
> Detected: 10:42 AM
>
> Open GermainUX for additional analysis.

## Configure the Trigger

Once the Microsoft Teams request is configured, associate it with the GermainUX condition that should trigger the notification.

For example:

SLA Violation
Send Teams Notification

Or:

New Error Detected
Analyze Error
Determine Impact
Send Teams Notification

Or:

Conversion Friction Detected
Identify Affected Visitors
Send Teams Notification
Investigate in GermainUX

The trigger can be configured according to the GermainUX monitoring, SLA, Rule, or Automation associated with the use case.

## Test the Notification

After configuration:

**1. Trigger the action**

Trigger the GermainUX action manually or generate a test condition.

**2. Check the request**

Verify that GermainUX successfully executes the HTTP request.

**3. Open the channel**

Open the configured Microsoft Teams Channel.

**4. Check the notification**

Verify that the notification appears.

**5. Check the content**

Confirm that the message contains the expected GermainUX information.

**6. Check the link**

If a GermainUX link is included, verify that it opens the expected dashboard or investigation context.

The complete validation path is:

GermainUX Condition
HTTP Request
Teams Workflow
Teams Channel
Notification

## Troubleshooting

If the Teams notification is not received, verify:

* The Microsoft Teams Workflow is enabled.
* The webhook URL configured in GermainUX is correct.
* GermainUX can reach the Microsoft endpoint.
* The HTTP request uses `POST`.
* The request uses the expected JSON format.
* The Teams Workflow accepts the submitted payload.

> **Show all 9**
>
> * The Workflow is configured for the correct Team and Channel.
> * The Workflow execution history shows that the request was received.
> * GermainUX did not report an error while executing the request.

> **The Workflow receives the request but no Teams message appears**
>
> Review the Microsoft Teams Workflow configuration and execution history.

> **The Workflow does not receive the request**
>
> Review the GermainUX HTTP action, webhook URL, network connectivity, and any applicable security restrictions.

## Security

Treat the Microsoft Teams webhook URL as sensitive configuration.

* Do not expose the webhook URL in dashboards, documentation, tickets, or other locations accessible to unauthorized users.
* Limit access to the GermainUX configuration containing the webhook.
* Send only information that the destination Teams Channel is authorized to receive.
* Avoid including PII, PHI, credentials, tokens, or other sensitive information unless specifically authorized.
* Review access to the destination Team and Channel before sending production notifications.

## Microsoft Teams Workflow Ownership

Microsoft Teams Workflows are associated with their owners.

For production integrations, ensure appropriate ownership and administration of the Workflow so that GermainUX notifications do not stop if the original Workflow owner leaves the organization or loses access.

> [!TIP]
>
> Microsoft recommends adding appropriate co-owners to maintain continuity for business-critical Workflows.

## Additional Resources

> **[AI](https://docs.germainux.com/main/ai-driven-insights.md)**
>
> Insights & Recommendations

> **[Analytics](https://docs.germainux.com/main/analytics.md)**
>
> Analytics Features

> **[Automation](https://docs.germainux.com/main/automation.md)**
>
> Automation Features

> **[Dashboard](https://docs.germainux.com/main/dashboard-and-report.md)**
>
> Dashboards and Reports

> **[Reports](https://docs.germainux.com/main/reporting-automatic.md)**
>
> Reports (Automatic, Scheduled)

> **[Management](https://docs.germainux.com/main/management.md)**
>
> Management Features

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.