OdooPilot

Your team uses Odoo — without logging in to Odoo.

OdooPilot gives every employee an AI assistant on Telegram or WhatsApp that connects to the
same Odoo instance, scoped to the same permissions they already have. They apply for leave,
approve requests, check tasks, update the CRM pipeline, and validate stock moves — by chatting
with a bot in their own language. No Odoo login, no app to install, no training.

For your internal team. Not for your customers. Each linked chat user is an Odoo user,
sees only the data they're authorised to see, and every write is recorded in the audit trail.

Mira (WhatsApp):    "I need 3 days off next month — Mar 14–16."
OdooPilot:          "Filed leave request for 3 days (Mar 14–16). Carlos has been notified."

Carlos (Telegram):  [inline button: ✅ Approve   ❌ Refuse ]
Carlos:             taps Approve.
OdooPilot:          "✅ Leave approved. Mira has been notified."

The Odoo adoption problem solved: data is no longer stale because the people who generate it
(field sales, warehouse staff, anyone who occasionally needs HR or Project) finally have a way
to reach Odoo that fits their day. Same data, same permissions, same audit trail — just lower
friction.

No external service to host. No per-seat SaaS fees. Everything runs inside your Odoo instance.
Powered by Claude AI, ChatGPT / GPT-4, Groq (free tier), or Ollama (100% local).
Works on Telegram and WhatsApp. Supports 15 languages. LGPL-3 open-source.

What it does

• Conversational queries on live Odoo data — Tasks, CRM, Sales, Invoices, Inventory, Purchase, HR, Leaves
• Write actions with a confirmation gate — Yes/No button required before any record changes
• Two channels, full parity — Telegram bot and WhatsApp Cloud API
• Choice of LLM — Anthropic Claude, OpenAI GPT-4o, Groq (free tier), or Ollama (100% local)
• 15 UI languages — per-user /language command
• Proactive notifications — daily task digest and overdue-invoice alerts
• Self-hosted — pure Odoo addon, runs entirely inside your instance, no separate service
• Auditable — immutable log of every AI action (timestamp, user, tool, args, result)
• Open source — LGPL-3, free to install, fork, and extend

Architecture

Everything runs inside the Odoo addon — no separate Python service, no Docker container, no cloud deployment.

 Telegram                       WhatsApp Cloud API
     │                                  │
     │  HTTPS POST                      │  HTTPS POST
     │  X-Telegram-Bot-                 │  X-Hub-Signature-256
     │  Api-Secret-Token                │  (HMAC-SHA256 of body)
     ▼                                  ▼
┌──────────────────────────────────────────────────────────────────┐
│  OdooPilot Odoo Addon                                            │
│                                                                  │
│  ┌────────────────────────────────────────────────────────┐     │
│  │  HTTP Controllers  (controllers/main.py)               │     │
│  │  • Verify webhook signature in constant time           │     │
│  │  • Per-(channel, chat_id) sliding-window rate limit    │     │
│  │  • Idempotency dedup on update_id / messages[].id      │     │
│  │  • Hand off to bounded worker pool                     │     │
│  └─────────────────────────┬──────────────────────────────┘     │
│                            │                                     │
│  ┌─────────────────────────▼──────────────────────────────┐     │
│  │  Agent  (services/agent.py)                            │     │
│  │  • Load session · build messages · run LLM tool loop   │     │
│  │  • Read tools execute immediately                      │     │
│  │  • Write tools → preflight → resolve target → stage    │     │
│  │    pending_args + per-write nonce → ask Yes/No         │     │
│  │  • On confirmed Yes → execute under linked-user env    │     │
│  └────┬─────────────────────────────────┬─────────────────┘     │
│       │                                 │                        │
│  ┌────▼──────────┐         ┌────────────▼────────────────┐      │
│  │  LLM Client   │         │  ORM Tools (services/tools) │      │
│  │  Anthropic    │         │  project / sales / crm      │      │
│  │  OpenAI       │         │  invoices / inventory       │      │
│  │  Groq         │         │  purchase / hr / leaves     │      │
│  │  Ollama       │         │  + 5 write tools w/ confirm │      │
│  └───────────────┘         └─────────────────────────────┘      │
│                                                                  │
│  Models                                                          │
│  ────────                                                        │
│  odoopilot.session         conversation history + pending nonce  │
│  odoopilot.identity        chat_id → Odoo user mapping           │
│  odoopilot.audit           immutable log of every tool call      │
│  odoopilot.link.token      SHA-256 hashed magic-link tokens      │
│  odoopilot.delivery.seen   webhook idempotency table             │
└──────────────────────────────────────────────────────────────────┘

Quickstart

Prerequisites

• Odoo 17.0 Community (self-hosted or Odoo.sh)
• An LLM API key — Anthropic, OpenAI, Groq (free tier, no card), or a local Ollama endpoint
• One of:
  • A Telegram bot token from @BotFather, and/or
  • A WhatsApp Business account with the Meta Cloud API enabled (phone number ID, access token, app secret)
• Odoo must be reachable from the internet (for webhook delivery)

1. Install the addon

Copy the odoopilot/ directory into your Odoo addons path, then:

# Restart Odoo and update the module list
./odoo-bin -c odoo.conf -u odoopilot

Or install from the Odoo App Store.

2. Configure in Odoo Settings

Go to Settings → OdooPilot and fill in the channels you want to enable.

Telegram

Then click Register Webhook. The action calls Telegram's setWebhook API and auto-generates a 32-byte secret, which Telegram echoes back on every delivery as X-Telegram-Bot-Api-Secret-Token. The endpoint rejects any request whose header doesn't match.

WhatsApp

Then in Meta's webhook config, set the callback URL to https://YOUR_ODOO/odoopilot/webhook/whatsapp and the verify token to whatever you pasted above.

The App Secret is mandatory. Without it the WhatsApp webhook refuses all traffic. Meta signs every POST with X-Hub-Signature-256 (HMAC-SHA256 of the raw body keyed with the App Secret); OdooPilot verifies this in constant time before any business logic runs.

LLM provider

Default models if you leave the override blank:

Optional throttling knobs

These are read once at first use from ir.config_parameter. Defaults are fine for most installs; raise them if your team is large, lower them if you suspect abuse.

3. Link employee accounts

Each employee sends /link to the bot. The bot replies with a one-time URL.
The employee opens the URL while logged into Odoo, sees a confirmation page,
clicks Confirm and link, and they're done.

The flow uses a two-step CSRF-protected handshake: GET previews, POST consumes. A logged-in admin who renders an <img src="…/odoopilot/link/start?token=…"> from a malicious record won't get silently linked — the consume only happens on a POST with Odoo's session-bound CSRF token.

4. Start chatting

Each linked user can send:

• Any natural-language question — "What invoices are overdue?", "Show my open tasks", "Approve John's leave"
• /start — short hello
• /link — re-issue a linking URL (existing identity is replaced)
• /language <code> — set their preferred reply language (15 supported); /language auto to revert to auto-detect

Read tools execute immediately. Write tools show an inline Yes / No button — the prompt names the resolved record (not the LLM's argument string), and the click carries a per-write nonce so it can't be swapped out from under you.

Supported domains

Write tools always show an inline Yes/No confirmation before touching data.

LLM providers

OdooPilot calls each provider's HTTP API directly via requests — no extra Python dependencies beyond what Odoo already ships, and you can swap providers in Settings → OdooPilot without restarting. See the Quickstart table above for the four supported providers and their default models.

To run 100% local with no third-party API calls, pick ollama and point the provider at your local Ollama endpoint via odoopilot.ollama_base_url (default http://localhost:11434). Your business data and prompts never leave your server.

Security

OdooPilot has been through a public audit (April 2026, u/jeconti on r/Odoo) and three follow-up internal reviews. The current model:

Webhook authentication

• Telegram verifies the X-Telegram-Bot-Api-Secret-Token header on every POST. The secret is mandatory and auto-generated by the Register webhook action; missing or mismatched secret returns 403.
• WhatsApp verifies Meta's X-Hub-Signature-256 HMAC-SHA256 in constant time. The Meta App Secret is mandatory; without it the endpoint returns 403.
• Both compares use hmac.compare_digest.

Per-write confirmation that survives prompt injection

• Every write tool runs preflight_write to resolve the target record before staging — the staged args carry a real res_id, not the LLM's argument string. Wildcard-only or overly-short names are rejected outright.
• The confirmation prompt names the resolved record's display_name, so a user clicking Yes sees what they're actually about to mutate (not what the LLM claimed it was).
• Every staged write generates a fresh secrets.token_urlsafe(12) nonce embedded in the Yes/No button payload. A prompt injection that tries to swap the staged tool between staging and the click rotates the nonce and the click is rejected.

Magic-link account binding

• Tokens are stored as SHA-256 digests (the raw token never persists), single-use, and expire after one hour.
• The link flow is two-step CSRF-protected: GET shows a preview page; POST with Odoo's session-bound CSRF token does the actual link. Cross-site <img src=> attacks cannot silently link an admin's account.
• Identity hijack defence: a logged-in user with a valid token cannot overwrite an existing (channel, chat_id) mapping owned by a different user — the attempt is refused at both preview and commit.

User scoping

• Each chat is resolved to an odoopilot.identity row. The agent then runs under that Odoo user (sudo_env(user=identity.user_id.id)) — every read and write is filtered by the user's existing record-rule access. The bot cannot do more than the user could do interactively.
• Webhook dispatch helpers receive sudo_env (named explicitly) only for the unavoidable bootstrap lookups (config, identity, session, link token). All business-data access uses the user-scoped env.

Cost & resource bounds

• Per-(channel, chat_id) sliding-window rate limit prevents an authenticated user (or a flood of forged messages) from driving unbounded paid-LLM spend.
• Bounded thread pool replaces the previous unbounded daemon-thread spawn — saturation drops gracefully with HTTP 200 so the platform doesn't retry-storm.

Idempotency

• Telegram retries on 5xx and timeouts; WhatsApp likewise. The odoopilot.delivery.seen table dedups on Telegram update_id and WhatsApp messages[].id with a SQL UNIQUE constraint. A redelivered confirmation click cannot re-execute the staged write.

Operational hygiene

• Audit log writes an immutable odoopilot.audit row for every tool call (timestamp, user, tool, args, result, success).
• Telegram bot tokens are scrubbed from any logged exception string.
• Static security scanning (bandit + semgrep) runs in CI on every push.

Reporting a vulnerability

Please don't disclose publicly. Use GitHub Security Advisories — see SECURITY.md for the full disclosure policy, supported versions, and threat model.

Status & roadmap

Current release: 17.0.11.0.0 (CHANGELOG: full history)

Recent line-up (all on the 17.0 branch and the Odoo App Store):

Coming next:

• 📋 Odoo 18 port — adapt to the 18 ORM, dual-branch CI
• 📋 Operator-friendly admin views — group audit log by user, recent-activity dashboard
• 📋 OCA submission once the 18 port lands

Contributing

Pull requests welcome. The fastest path to a merged PR:

1. Pick an unimplemented tool or domain from the table above
2. Add it to odoopilot/services/tools.py following the existing pattern
3. Register the tool schema in odoopilot/services/agent.py
4. Open a PR — CI must be green (ruff format + lint + XML check)

See CONTRIBUTING.md for full details.

Sponsor & feedback

OdooPilot is free, open-source, and solo-maintained. After install, Settings → OdooPilot ends with quick links for all of these — or use the URLs directly:

• ♥ Sponsor on GitHub → https://github.com/sponsors/arunrajiah
• 💬 Feedback & ideas → https://github.com/arunrajiah/odoopilot/discussions/new?category=ideas
• 🛠 Report a bug → https://github.com/arunrajiah/odoopilot/issues/new/choose
• 🔒 Report a security issue (private) → https://github.com/arunrajiah/odoopilot/security/advisories/new

License

LGPL-3.0-or-later — same as Odoo Community and OCA modules.