Skip to main content
Auvik monitors the networks at your clients’ sites: it finds the switches, routers, firewalls and access points, maps how they connect, and raises alerts when a device goes offline. Connect Auvik to Neo once, at the MSP level, with the email and API key of an Auvik user.

What Neo can do with Auvik

Device down

Find the device from the ticket by name, IP address, serial number or MAC address. Tell whether it is really down, when Auvik last saw it, and how long its outages lasted.

Uplinks

See the switches, routers and firewalls the device connects to, on which ports, and whether each port is up. When the device has more than one such neighbour, Neo lists each as a possible uplink.

Alerts

Read the open Auvik alerts on the device or its uplink, and dismiss an alert once the condition has cleared and the ticket is resolved.

Inventory and billing

Read device details, warranty and end of life, networks and statistics, and the billable device days for each client.
Auvik’s published API reads only, apart from dismissing an alert. It has no operation that runs a command on a device, pushes a configuration, or exports a configuration backup, and Auvik says configuration backups cannot be exported through the API. So Neo cannot do these through Auvik.

Your clients are mapped automatically

Neo matches each Auvik site to a company in your PSA and keeps the mapping on the Auvik card’s Organization Mapping tab. It refreshes the mapping when you save the API key, and again on each nightly PSA sync. A client with several sites maps each site to the same company. Matching starts with the name of the multi-site the site sits under, when it is not your own top-level account. Then comes the site’s display name, then its domain prefix: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest. A name match, or one you confirm, is handed straight to your agents, so they start from the client’s sites without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Neo sees only the sites the Auvik user can access. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. One Auvik API key sees every site the Auvik user can access. On a ticket that names a company, Neo sends a call only for the Auvik sites that company is mapped to, and checks that a device, interface or alert it reads or dismisses belongs to one of them. Calls that reach every site, such as the tenant list, are made only outside a ticket, such as from a chat with Neo. If the ticket’s company has no mapped site, Neo asks you to map it on the Organization Mapping tab.

Next steps

Connect Auvik

Generate an API key in Auvik and save it in Neo with your region.