Skip to content

Slack and Internal Notifications

Besides Microsoft Teams, a Muppy queue can send its Task processing notifications to Slack, or to the Odoo user interface itself (Internal notifications).

All three channels are configured on the same screen — Muppy / Qs / Queues, open the queue, Notifications tab — and they are independent: activate one, two, or all three.

Which events produce a notification is set per Message Processor, on that model's own Notifications tab (start / end / retry / terminate / fail).

Slack

Slack is connected through an OAuth flow rather than by pasting a URL:

  1. In the Slack notifications group, click the Add to Slack button.
  2. Slack asks you to pick the workspace and the channel the notifications go to, and to authorise the incoming-webhook scope.
  3. Back in Muppy, Slack Team and Slack Webhook Channel show what was granted.
  4. Click Test Slack notifications — Muppy posts a test message to the channel.

Note

The Add to Slack button builds its authorisation URL from two system parameters, imq.SLACK_APP_CLIENT_ID and imq.SLACK_OAUTH_CALLBACK. They are set on the hosted muppy.io service. On a self-hosted instance (Muppy Enterprise) they must be filled in with your own Slack app before the button can work.

Internal notifications

The simplest channel: notifications are delivered inside Muppy, to the Odoo user.

In the Internal notifications group, check Use Odoo Notifications (it is on by default), save, then click Test Internal notifications.

This channel depends on nothing outside the instance, which makes it the one to fall back on when an external connector is unavailable or being replaced.