Odoo Helpdesk
Connect NetLock RMM to Odoo Helpdesk: alerts become tickets in a team, the all-clear adds an internal note and moves the ticket to a stage, companies can be imported as tenants.
Odoo Helpdesk
Requirements
- Odoo 17 or newer with the Helpdesk app, on a plan with access to the external API.
- The API key of a dedicated user who may read and write helpdesk tickets and read companies, created under
My Preferences,Account Security. Odoo keys can have an expiry date.
Setup
- In
Settings → Integrations, open the Odoo Helpdesk tile and chooseConnect. - Enter the
Instance addressand theAPI key.- Odoo 19 and newer: leave
Odoo 17 or 18 (JSON-RPC)off.Databaseis only needed when a server hosts several databases. - Odoo 17 and 18: switch it on and enter
DatabaseandLogin. Allow unencrypted httpis for an instance on an internal network only.
- Odoo 19 and newer: leave
- The test reads the helpdesk teams and the fields of the ticket model, so a database without the Helpdesk app, or with different fields, is detected here and not at the first alert.
- Under options, choose the
Helpdesk teamand theStage when closing. Choose a stage of that team: the list shows the stages of all teams. - Map each tenant to a company, or import companies as tenants. Tenants without a mapping are not included. Without a severity mapping the four severities follow the four priorities.
- Activate the connection.
Note: A ticket carries the mapped company as its customer. Odoo can e-mail the customer when a ticket reaches a stage with an e-mail template. Check the stages of the team before you connect, otherwise a customer gets an e-mail for every alert.
What goes to the vendor
For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.
What happens to a ticket
- An alert becomes a ticket in the chosen team. The name ends in
[NetLock-Alert-<id>], which NetLock uses to find the ticket again. - When the alert ends, the ticket gets an internal note and moves to the chosen stage if nobody is assigned.
The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.
Known limits
- If Odoo refuses the stage, the ticket stays open with its note and the history shows
close_refused. - Odoo has announced that a later version will remove the RPC interface that NetLock uses for Odoo 17 and 18. This does not affect those versions.
- Assets are not part of this integration.
Related
Freshdesk
Connect NetLock RMM to Freshdesk: alerts become tickets, the all-clear adds a private note and sets a status, companies can be imported as tenants.
ITFlow
Connect NetLock RMM to a self-hosted ITFlow: alerts become tickets, the all-clear adds an internal reply and resolves or closes the ticket, devices can be synced as assets, clients and locations can be imported.