| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 529 |
| Technical Name |
kontext_connect |
| License | OPL-1 |
| Website | https://kontextsystems.com |
| Versions | 16.0 17.0 18.0 |
Kontext Connect
Real-time Webhook Connector for Odoo
Send live webhook events to your backend the moment a Sale Order, Invoice, Delivery, or Contact changes â with zero external dependencies and a single-screen setup.
- ✅ Works on self-hosted Odoo 18 and Odoo.sh
- ✅ Pure Python stdlib â no pip install required
- ✅ One-click token generation & automatic rule management
Why Kontext Connect?
Most webhook addons rely on heavy frameworks or background job queues that
need extra infrastructure. Kontext Connect takes a different
approach: it uses Odoo's built-in Automation Rules engine and
Python's standard urllib library to dispatch events inline â
no queue_job, no requests, no system packages.
Install it on Odoo.sh in under two minutes with zero dependency headaches.
Features
Bearer Token Auth
Generate a cryptographically secure API token in one click. Every
outgoing request carries it as an Authorization: Bearer
header.
Zero External Dependencies
Uses only Python's built-in urllib â no
requirements.txt changes, no pip installs, no conflicts.
Odoo.sh ready out of the box.
Per-Model Control
Toggle webhooks for Sale Orders, Invoices, Stock Pickings, and Partners independently. Rules are created, activated, and deactivated automatically.
Full Audit Log
Every outgoing webhook is recorded: event type, model, record ID, HTTP status code, response time, and full request/response bodies.
Synchronous Dispatch
Events fire within the same Odoo transaction. No background workers, no job queues â your backend receives the event immediately on record save.
Smart Field Filters
On-update rules only fire when business-critical fields change (e.g. state, amount, payment_state) â not on every minor UI write.
Never Breaks Odoo
Dispatch errors are caught silently and written to the audit log. A failed webhook never raises an exception or rolls back the user's transaction.
Rich JSON Payloads
Payloads include the full serialised record â order lines, invoice amounts, delivery moves, partner details â ready for your backend to process without extra API calls.
How It Works
Install
Install Kontext Connect from the Apps menu. A configuration record is created automatically.
Generate Token
Click Generate Token. Copy the token to your Kontext Systems dashboard.
Select Models
Toggle which models to watch (Sale Orders, Invoices, Pickings, Partners), then click Apply Rules.
Live
Events start flowing immediately. Monitor them in the Webhook Log.
Screenshots
Configuration form â one screen to rule them all.
Webhook Audit Log â every outgoing call recorded with HTTP status and response time.
Auto-managed Automation Rules â up to 12 rules (4 models à 3 triggers) created and maintained for you.
Configuration
Complete setup takes under 5 minutes.
https://api.kontextsystems.com/prod/v1/odoo-api is pre-filled.
Change it only if you are running a private Kontext instance.
Webhook Payload
Every event is a JSON POST to {API URL}/events with an
Authorization: Bearer <token> header.
{
"event": "sale_order.updated",
"timestamp": "2026-03-25T14:32:11.045Z",
"model": "sale.order",
"record_id": 42,
"data": {
"id": 42,
"name": "S00042",
"state": "sale",
"partner_id": [7, "Acme Corp"],
"amount_total": 1540.00,
"date_order": "2026-03-25T14:30:00+00:00",
"order_line": [
{
"product_id": [12, "Widget Pro"],
"product_uom_qty": 4.0,
"price_unit": 385.00
}
]
}
}
Compatibility
| Environment | Supported | Notes |
|---|---|---|
| Odoo 18.0 (Community) | ✓ | Fully tested |
| Odoo 18.0 (Enterprise) | ✓ | Fully compatible |
| Self-hosted | ✓ | No extra packages needed |
| Odoo.sh | ✓ | Add as Git submodule â no requirements.txt changes |
| Odoo Cloud (SaaS) | ✗ | Odoo Cloud does not support custom addons |
| Odoo 18 / 18 | ⋯ | Not tested â separate versions planned |
Frequently Asked Questions
Does Kontext Connect retry failed webhooks?
No. Webhooks are dispatched synchronously and not retried automatically. Failed calls are recorded in the Webhook Log so you can investigate and manually re-trigger if needed. For high-reliability requirements, implement idempotent event processing on your backend and reconcile periodically via the Odoo REST API.
Will high webhook volume slow down Odoo?
Webhooks are synchronous â each call adds the HTTP round-trip time to the record save. With a typical API response time of 50â200 ms, this is imperceptible for most workflows. For companies processing tens of thousands of records per hour, consider using Kontext Connector (our queue-based async addon) instead.
What happens if I regenerate the API token?
The old token is immediately replaced. All subsequent webhook calls use the new token. Update your Kontext Systems dashboard with the new token before regenerating, or expect a brief period of 401 errors logged in the Webhook Log.
Can I use this with Odoo Cloud?
No. Odoo Cloud (the fully-managed SaaS) does not allow custom addons. Kontext Connect works on self-hosted Odoo 18 and Odoo.sh. If you are on Odoo Cloud, contact Kontext Systems â we have an alternative integration path.
What is the difference between Kontext Connect and Kontext Connector?
Kontext Connect (this addon) is lightweight and
synchronous â zero extra dependencies, ideal for Odoo.sh and lower to
moderate volumes.
Kontext Connector is our asynchronous, queue-based
addon that uses queue_job for high-throughput environments
(100k+ events/day) with retry logic and backpressure handling. It
requires queue_job and the requests library.
Where do I get support?
Email us at support@kontextsystems.com or visit kontextsystems.com. We typically respond within one business day.
Kontext Connect — version 18.0.1.0.0 — Odoo 18 — OPL-1 License
© 2026 Kontext Systems | support@kontextsystems.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 529 |
| Technical Name |
kontext_connect |
| License | OPL-1 |
| Website | https://kontextsystems.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module