Notifications

Connect Microsoft Teams to Odoo via OEC.sh

Pipe Odoo deployment events into Microsoft Teams channels.

Available on the Free plan.

What this integration does

OEC.sh ships a native MessageCard format for Microsoft Teams. Add a Teams Incoming Webhook to any channel, paste the URL into OEC.sh, and route deployment, backup, and error events with rich cards that show commit, environment, and duration at a glance.

The integration is configured from your OEC.sh project settings. If you have not created an account yet, you can start free and connect Microsoft Teams in under five minutes. Compare OEC.sh against the hosted Odoo.sh option if you are still deciding where to run Odoo.

Common use cases

Notify your IT operations channel when production goes down or a health check fails

Send deployment cards to a dev team channel so reviewers can jump straight into the platform

Alert finance or admin channels when a backup of the accounting environment completes

Route preview environment events to a QA channel during PR review cycles

How to set it up

Five steps, end to end. Most teams finish in under five minutes.

1
In Teams, open the target channel, click the three-dot menu, then choose Connectors
2
Find Incoming Webhook, click Configure, give it a name like 'OEC.sh', and upload an icon if you want
3
Copy the generated webhook URL
4
In OEC.sh, go to Project, Webhooks, Add Webhook, pick the Microsoft Teams format, and paste the URL
5
Select the events you care about, save, and use the Send Test button to confirm the card renders

Example payload

Here is the exact format OEC.sh sends (or that you would send to OEC.sh, in the case of GitHub Actions, GitLab CI, Bitbucket Pipelines, and n8n).

{
  "@type": "MessageCard",
  "@context": "https://schema.org/extensions",
  "themeColor": "0078D4",
  "summary": "Production deploy succeeded",
  "sections": [
    {
      "activityTitle": "OEC.sh deploy succeeded",
      "activitySubtitle": "production / main",
      "facts": [
        { "name": "Environment", "value": "production" },
        { "name": "Branch", "value": "main" },
        { "name": "Commit", "value": "a62de43" },
        { "name": "Duration", "value": "2m 14s" }
      ],
      "markdown": true
    }
  ],
  "potentialAction": [
    {
      "@type": "OpenUri",
      "name": "Open in OEC.sh",
      "targets": [
        { "os": "default", "uri": "https://platform.oec.sh" }
      ]
    }
  ]
}

Try this with a free account

Plan availability

Available on every plan including Free ($0/mo). No payment details needed to wire it up.

See full pricing

Frequently Asked Questions

No. Any Microsoft Teams tenant (including Microsoft 365 Business Basic) can add an Incoming Webhook connector to a channel. No premium Teams licence is required.

Microsoft Teams uses Incoming Webhooks for one-way notifications, which means there is no OAuth dance. You create a webhook URL inside Microsoft Teams, paste it into OEC.sh under Project, Webhooks, and OEC.sh signs and posts events to that URL. The URL itself is the credential, so treat it as a secret.

Yes. OEC.sh ships native message presets for Microsoft Teams that look good out of the box, but you can override the payload template per webhook. The template uses event variables like {{environment}}, {{commit}}, {{branch}}, {{duration}}, and {{actor}}. If you need fully custom formatting, switch the format to 'Raw JSON' and write your own template.

Available on every plan including Free ($0/mo). No payment details needed to wire it up.

Microsoft Teams runs in Microsoft 365 and is not self-hosted. The Incoming Webhook connector works the same way across all Teams tenants, including those with strict data residency settings, because the webhook lives inside your tenant.