Zammad
Connect NetLock RMM to Zammad: alerts become tickets in a group, the all-clear adds an internal note and closes the ticket, organizations can be imported as tenants.
Zammad
Requirements
- A Zammad instance with
API Token Accessswitched on. - An access token of an agent, created in the Zammad profile under
Token Access. It needs the permissionsticket.agentandadmin.group, and its account needs access to the target group.
Setup
- In
Settings → Integrations, open the Zammad tile and chooseConnect. - Enter the
Instance address, for examplehttps://helpdesk.example.com, and theAccess token.Allow unencrypted httpis for an instance on an internal network only: the token is then sent unencrypted with every request. - Under options, choose the
Groupthat receives the tickets, theStatus when closing, and the customer for tickets without an organization member. This is an e-mail address; Zammad creates the user if it does not exist. - Map each tenant to an organization, or import organizations as tenants. Tenants without a mapping are not included. Severities can be mapped to Zammad priorities; without a mapping Zammad uses its default priority.
- Activate the connection.
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 group, with the alert as an internal note. The title ends in
[NetLock-Alert-<id>], which NetLock uses to find the ticket again. - A Zammad ticket belongs to an organization through its customer, so NetLock uses the first member of the mapped organization as customer. Without members the configured customer is used, and the ticket does not belong to the organization.
- When the alert ends, the ticket gets an internal note and goes to the chosen status if nobody is assigned. A ticket counts as unassigned while it has the empty default owner of Zammad.
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
- The article is internal, but the title of the ticket is visible to the customer and to members of a shared organization in the customer interface.
- If Zammad refuses to close the ticket, for example because of a Core Workflow, the note is added and the ticket stays open. The history shows
close_refused.
Related
Integrations
The integrations store: connecting ticket and documentation systems, the setup assistant, mappings, company import, history, the log of a connection, what a connection sends, and which rights and tenant limits apply.
Jira Service Management
Connect NetLock RMM to Jira Service Management Cloud: alerts become requests of a chosen request type, the all-clear adds an internal comment and moves the request to a chosen status.