Notifications

Connect Slack to Odoo via OEC.sh

Send Odoo deploy alerts and errors to your Slack channels.

Available on the Free plan.

What this integration does

Configure outgoing webhooks in OEC.sh to post directly to Slack channels using native message formatting. Subscribe to events like deployment.succeeded, environment.created, backup.completed, or webhook.failed, and route each event to a different channel if you want.

The integration is configured from your OEC.sh project settings. If you have not created an account yet, you can start free and connect Slack 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

Get notified the moment a production deploy succeeds or fails, with the commit SHA and the user who triggered it

Pipe error spikes and unreachable health checks to your #ops channel before customers notice

Post a daily backup summary to your team channel so backups never become a quiet failure

Surface Automation Rule triggers (scheduled clones, weekly restore tests) so the team sees what fired and when

How to set it up

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

1
In Slack, open the channel you want, then create an Incoming Webhook for it via the Slack app directory
2
Copy the webhook URL (it starts with https://hooks.slack.com/services/...)
3
In your OEC.sh dashboard, go to Project, then Webhooks, then Add Webhook
4
Paste the URL, pick the Slack format preset, and select the events you want to subscribe to
5
Save the webhook and click Send Test to verify the message arrives in the right channel

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).

{
  "text": "Deploy succeeded on production",
  "blocks": [
    {
      "type": "header",
      "text": { "type": "plain_text", "text": "Production deploy succeeded" }
    },
    {
      "type": "section",
      "fields": [
        { "type": "mrkdwn", "text": "*Environment:*\nproduction" },
        { "type": "mrkdwn", "text": "*Branch:*\nmain" },
        { "type": "mrkdwn", "text": "*Commit:*\n`a62de43`" },
        { "type": "mrkdwn", "text": "*Duration:*\n2m 14s" }
      ]
    },
    {
      "type": "actions",
      "elements": [
        { "type": "button", "text": { "type": "plain_text", "text": "Open in OEC.sh" }, "url": "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. Slack's free workspace tier supports Incoming Webhooks, which is all this integration needs. Paid Slack plans only add things like longer message history and SSO, which are unrelated to the webhook itself.

Slack uses Incoming Webhooks for one-way notifications, which means there is no OAuth dance. You create a webhook URL inside Slack, 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 Slack 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.

Slack Enterprise Grid is supported the same way as standard Slack: create an Incoming Webhook in the workspace you want and paste it into OEC.sh. There is no on-premise Slack to integrate with.