Microsoft Teams Notifications¶
Muppy can post notifications about Task processing into a Microsoft Teams channel.
The notifications are produced by the Queues as they process messages, so the configuration is per queue — not global.
What gets notified¶
A queue decides whether to notify; each Message Processor decides which events are worth a notification. On the processor's Notifications tab you choose among:
- processing start,
- processing end,
- processing retry,
- processing terminate,
- processing fail.
That is where you narrow a chatty queue down to failures only.
1. Create an Incoming Webhook in Teams¶
Ask the administrator of your Microsoft Teams tenant to create a Team and a Channel, then create an Incoming Webhook connector on that channel and copy its URL.
Give the connector a name (it appears on every notification) and, if you want Muppy's notifications to be recognisable at a glance, upload an icon for it.
Warning
Muppy posts Office 365 connector cards to that webhook URL. Microsoft has been retiring Office 365 connectors in Teams in favour of Power Automate Workflows. Check what your tenant still accepts before relying on this channel — and use Internal notifications or Slack if connectors are gone on your side.
2. Configure the Muppy queue¶
Open Muppy / Qs / Queues, open the queue (Muppy is the main one), then its Notifications tab, Microsoft Teams group:
| Field | Meaning |
|---|---|
| Use Microsoft Teams notificatations | Check to activate the channel. |
| Microsoft Teams URL | Paste the Incoming Webhook URL from step 1. |
| Microsoft Teams Webhook timeout | In seconds. 0.324 means 324 ms. Default 0.5. |
| Teams HTTPS Proxy | Full URL of the HTTPS proxy to send through, if any — e.g. http://user:password@proxy_fqdn:proxy_port. User and password must be URL-encoded. |
Save, then click Test Teams notifications. Muppy posts a test card to the channel; if it does not arrive, the webhook URL or the proxy is where to look.