Automation

Connect n8n to Odoo via OEC.sh

Drive Odoo deploys, clones, and alerts from n8n workflows.

Available on the Starter plan.

What this integration does

n8n is the open source automation platform that pairs well with Odoo. Call the OEC.sh Public API from any HTTP Request node using a Bearer token, then subscribe to outgoing webhooks to receive events back. The result: low-code workflows that clone, restore, notify, and sync Odoo with whatever else your business runs on.

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

Auto-clone production into a fresh staging env every Sunday night for QA on Monday

When a deploy fails, post to Slack, open a Jira ticket, and page the on-call engineer in one flow

Sync new Odoo CRM leads into HubSpot, Pipedrive, or a Google Sheet without writing custom code

Trigger an Odoo backup before a scheduled module upgrade, and only proceed if the backup succeeded

How to set it up

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

1
In OEC.sh, go to Settings, API Tokens, and generate a token with the scopes you need (deploys, backups, environments)
2
In n8n, add an HTTP Request node and set Authentication to 'Header Auth' with header 'Authorization: Bearer YOUR_TOKEN'
3
Point the node at https://api.oec.sh/v1/... for the action you want (deploy, clone, restore, list)
4
For incoming events, add an n8n Webhook node and paste its URL into OEC.sh under Project, Webhooks
5
Pick the events to subscribe to (deployment.succeeded, backup.completed, environment.created) and save

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

{
  "nodes": [
    {
      "name": "Trigger OEC.sh deploy",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "url": "https://api.oec.sh/v1/projects/{{$json.projectId}}/deploy",
        "method": "POST",
        "authentication": "headerAuth",
        "sendBody": true,
        "bodyContentType": "json",
        "jsonBody": "={ \"environment\": \"production\", \"branch\": \"main\" }"
      },
      "credentials": {
        "httpHeaderAuth": { "name": "OEC.sh API Token" }
      }
    }
  ]
}

Try this with a free account

Plan availability

Uses the OEC.sh Public API, which is available on Starter ($19/mo) and above. Free accounts can still receive webhook events, but cannot call the API outbound.

See full pricing

Frequently Asked Questions

No. n8n is open source and free to self-host. If you use n8n Cloud, the free tier is enough to call OEC.sh's API for personal projects, and the paid tiers add execution volume.

n8n authenticates against the OEC.sh Public API using a Bearer token. Inside OEC.sh, go to Settings, API Tokens, and generate a token scoped to the actions you need (deploy, backup, environment management). In n8n, configure the HTTP Request node with Header Auth and the header 'Authorization: Bearer YOUR_TOKEN'.

Yes. Because n8n is the consumer (not the producer), you control the message format end to end. OEC.sh sends a JSON payload to your webhook node, and from there you can transform it however you want with Function or Set nodes before passing it to Slack, email, a database, or any other downstream service.

Uses the OEC.sh Public API, which is available on Starter ($19/mo) and above. Free accounts can still receive webhook events, but cannot call the API outbound.

Yes. Self-hosted n8n works exactly the same as n8n Cloud, because the integration is just HTTPS calls to the OEC.sh Public API and HTTPS webhooks back. As long as your n8n instance can reach api.oec.sh and OEC.sh can reach your n8n webhook URL, you are set.