agentsclimarketplace

Odoo integrations

Skill wpmoo-org/odoo-skills/skills/odoo-integrations

Agent Skills for Odoo, OCA-compatible addon development, porting, and open-core Odoo products.

Install
npx -y skills add wpmoo-org/odoo-skills --skill odoo-integrations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when designing, implementing, reviewing, or debugging Odoo integrations with external APIs, webhooks, payment/shipping/accounting systems, queues, connectors, imports, exports, and RPC endpoints.

SKILL.md

2.8 KB, as published. Nobody here has run it

Odoo Integrations

Use this skill for external API connectors, webhooks, payment providers, shipping carriers, accounting integrations, imports, exports, queues, and Odoo RPC endpoints. Pair it with the target skills/odoo-13 through skills/odoo-19 skill for version-specific ORM, controller, and test APIs.

First steps

  1. Identify data ownership, direction, frequency, retry behavior, and whether Odoo or the external system is the source of truth.
  2. Confirm authentication, rate limits, idempotency keys, pagination, webhook signature validation, and error semantics from official provider docs.
  3. Map external identifiers to stable Odoo fields or binding models.
  4. Define failure handling before implementation: retry, quarantine, manual review, rollback, or compensating action.

Odoo design rules

  • Keep credentials in Odoo configuration, settings models, or deployment secrets according to project policy. Never hard-code secrets.
  • Use binding models for durable external IDs when records can be synced more than once.
  • Make imports idempotent. Replaying the same payload should update or skip, not duplicate business records.
  • Validate access, state, company, and record rules for public RPC methods and controllers.
  • Use queues or cron jobs for slow or unreliable external calls.
  • Keep external I/O out of transactions where retry behavior could duplicate side effects.
  • Log enough context to debug without storing secrets or personal data unnecessarily.

Data mapping checklist

  • Partners, addresses, companies, currencies, taxes, fiscal positions, units of measure, products, lots, stock locations, journals, and payment terms.
  • Time zones, dates, rounding, precision, and currency conversion.
  • Multi-company ownership and allowed-company context.
  • Attachments and binary payload size limits.
  • Deletions, cancellations, refunds, and conflict resolution.

Testing

  • Unit-test mapping and idempotency with fixture payloads.
  • Mock network calls; do not depend on live external services in regular tests.
  • Add integration smoke tests only when credentials and sandbox endpoints are intentionally configured.
  • Test webhook authentication failures, duplicate events, stale events, and out-of-order delivery.

Done criteria

  • Data ownership, retry semantics, and idempotency are explicit.
  • Credentials and webhook secrets are handled by approved configuration paths.
  • External failures do not corrupt Odoo transactions or create duplicates.
  • Logs are useful and do not leak secrets.
  • Mapping, security, and replay tests pass.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.