Openclaw Skill for Odoo
SuspiciousAudited by ClawScan on May 10, 2026.
Overview
This looks like a legitimate Odoo connector, but it gives an agent broad power to change ERP records and auto-create business data, so it should be reviewed before use.
Before installing, decide which Odoo modules the agent should control, use a dedicated limited-permission API user, test against a non-production database, and require human confirmation for financial, HR, inventory, deletion, posting, or public website changes.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or overly broad agent action could create, confirm, post, publish, or otherwise alter important business records.
This shows broad ERP mutation authority combined with automatic fuzzy workflows. The provided artifacts do not show explicit confirmation, dry-run, rollback, or scoping controls for high-impact business changes.
enabling autonomous, chat-driven control over 153+ business modules ... All operations use **smart actions** that handle fuzzy matching and auto-creation workflows.
Use a staging database first, require explicit human confirmation for create/update/delete/post/publish actions, and restrict the Odoo account to only the modules and operations the agent truly needs.
If configured with an admin or overly broad Odoo key, the agent could access or change much more business data than intended.
The connector requires an Odoo API key, which is expected for this integration, but that key may carry broad business privileges and the registry metadata declares no primary credential or required environment variables.
Create a file named `config.json` in the skill directory with your Odoo credentials: ... "api_key": "your_odoo_api_key"
Create a dedicated least-privilege Odoo API user, avoid admin credentials, protect `config.json`, and revoke the key if the skill is removed or no longer needed.
If enabled, the skill may keep polling or serving webhook requests until the process is stopped.
The artifacts disclose optional long-running sync components. This is purpose-aligned for real-time ERP updates, but users should notice that such components may continue operating beyond a single chat request.
Webhook server for real-time updates (optional feature) ... Background polling for change detection (optional feature)
Enable sync features only when needed, run them under supervision, document how to stop them, and monitor their activity.
A poorly configured webhook endpoint could expose or accept unintended ERP update events.
The skill has configuration for an inbound webhook server and an HMAC secret. The default empty secret means users should ensure a secret is set if webhooks are enabled.
webhook_port: int = 8069
webhook_secret: str = ""Set a strong webhook secret, bind the server only where needed, firewall the port, and verify webhook senders before using this feature.