NetLock RMMNetLock RMM Docs
IV — Administration

Freshservice

Connect NetLock RMM to Freshservice: alerts become tickets, the all-clear adds a private note and sets a status, devices can optionally be synced as assets.

Freshservice

Requirements

  • A Freshservice account, reached at https://<account>.freshservice.com. Other addresses are refused.
  • The API key of an agent who may create tickets, add notes and change the status. The key is shown in the profile settings of the agent, and the integration has the rights of the agent.
  • For the asset sync, the right to manage assets, and an account on the classic asset model, see Known limits.

Setup

  1. In Settings → Integrations, open the Freshservice tile and choose Connect.
  2. Enter the Instance address and the API key.
  3. Under options, set Freshservice for MSPs if you use that product: tenants then map to clients instead of departments. Enter the requester of tickets, the e-mail address under which tickets are created. Freshservice creates the contact if it does not exist. Optionally choose a Group, and choose the Status when closing.
  4. Map each tenant to a department or client, or import them as tenants. Tenants without a mapping are not included. Without a severity mapping the four severities follow the four priorities.
  5. 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.

With the asset sync on, also: device name, operating system, manufacturer, model, serial number, IP address and MAC address.

What happens to a ticket

  • An alert becomes a ticket with the reference as tag. The subject ends in [NetLock-Alert-<id>].
  • When the alert ends, the ticket gets a private note and moves to the chosen status if nobody is assigned.
  • If your account requires fields on closing, Freshservice refuses the status. The ticket stays open with its note and the history shows close_refused. Skip mandatory fields when closing avoids that; it works only with the API key of an administrator.

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.

Asset sync

The sync is off by default, because assets can count against your Freshservice license. To use it:

  1. Switch on Sync devices as assets.
  2. Map device classes to asset types, or choose a Default asset type. A device without a type is skipped and named in the history.
  3. Optionally map locations.

Every hour NetLock sends the authorized devices of the mapped tenants that changed since the last run, at most 200 per run; if more devices changed, the next run starts right after. Synchronize now starts a run immediately. NetLock recognises a device by its asset tag NetLock-Device-<id>. The device details are written to the description of the asset, because the other fields differ per asset type. A ticket for a device links to its asset.

A device that fails is named in the history and waits for the next hourly run; the other devices are still processed, and the connection is not affected. Nothing is deleted in Freshservice: a device removed from NetLock stays there.

Known limits

  • The asset sync supports accounts created up to 31 March 2026. Newer accounts use Freshservice IT Asset Management; leave the asset sync off there. Tickets are not affected.
  • In Freshservice for MSPs an asset cannot be moved to another client. A device that moved to another tenant reports that in the history.