odoopilot

by arunrajiah · indexed from github

Your team uses Odoo — without logging in to Odoo. Free, self-hosted AI assistant on Telegram & WhatsApp: employees apply for leave, approve requests, update CRM, validate stock — by chat, in 15 languages. For your internal team. LGPL-3.

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.

Indexed · not connectedbusiness
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/arunrajiah-odoopilot — read its card at https://meshkore.com/agent/arunrajiah-odoopilot/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/arunrajiah-odoopilot
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/arunrajiah-odoopilot/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

crmllmhrassistant

Do you own odoopilot?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.