> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging/microsoft-teams.md).

# Microsoft Teams

Connect Microsoft Teams to Heeler with Teams Workflows webhooks — a two-minute setup, no Azure AD app.

Heeler delivers workflow notifications to Teams channels using **Teams Workflows webhooks** — a self-service setup that takes about two minutes. **No Azure AD App Registration, admin consent, or Graph permissions** are required.

## Setup summary

Create the integration (just a name), generate a webhook URL per channel in Teams, add those URLs to Heeler, and select **Send Teams Message** in workflows.

## Step 1 — Create the integration

Go to **Administration → Integrations → Add Integration → Microsoft Teams**, enter a descriptive **Integration Name** (e.g. `MS Teams Notifications`), and **Save**. No credentials are needed yet.

## Step 2 — Generate a webhook in Teams

For each channel you want notifications in:

1. Open the channel, click the **⋯** on the channel name, and select **Workflows**.
2. Search for **"Send webhook alerts to a channel"** and select it.
3. Review the name and target channel, click **Add workflow**, and copy the generated **webhook URL**.

## Step 3 — Add webhooks in Heeler

1. On the Teams integration row, open the **⋯** menu and select **Manage Webhooks**.
2. Click **Add Webhook**, enter a **Label** (e.g. `Security Alerts – General`) and paste the **Webhook URL**.
3. **Add Webhook**. Repeat for each channel.

{% hint style="info" %}
**Test it:** in the Manage Webhooks drawer, open a webhook's **⋯** menu → **Send Test Message**, and confirm an Adaptive Card from "Heeler Security" arrives in the channel.
{% endhint %}

## Step 4 — Use it

In a workflow's **Action** step, choose **Send Teams Message**, then pick the **Connection** (your Teams integration) and **Webhook Destination**. You can also set a default Teams channel on a repository, service, or module via its **Channel** field.

## Troubleshooting

<table><thead><tr><th width="330">Issue</th><th>Fix</th></tr></thead><tbody><tr><td>"Send Teams Message" missing in workflow actions</td><td>Ensure a Teams integration exists under Administration → Integrations.</td></tr><tr><td>Webhook test fails with an HTTP error</td><td>Verify the URL is correct and the Teams Workflow is still active.</td></tr><tr><td>No destinations in the workflow dropdown</td><td>Add webhooks via <strong>Manage Webhooks</strong> on the integration row.</td></tr><tr><td>Teams Workflow expired or deleted</td><td>Generate a new webhook URL in Teams and update it in Heeler.</td></tr></tbody></table>

## Related

* [Connect Messaging](/mrecEO40m5D6bt7Pq5pE/get-started/messaging.md) — the other supported messaging tools.
* [Actions](/mrecEO40m5D6bt7Pq5pE/operate/workflows/actions.md) — the workflow action that sends the message.
* [Routing and Templates](/mrecEO40m5D6bt7Pq5pE/operate/workflows/routing-and-templates.md) — controlling message content and destination.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging/microsoft-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.