Current + UniFi Site Manager integration

UniFi is where the network itself lives — the gateway at each location, the switches and access points behind it, and the internet circuit into the building. Current's UniFi integration is a view-only feed into the SBR/QBR module and the company alert band. It reads what Ubiquiti's Site Manager service already knows and never writes back.

What the integration does

Current authenticates to Ubiquiti's cloud service with a single account-wide API key, walks every console that key can see every six hours, and stages the result as evidence for AI-assisted Strategic Business Reviews. Instead of screenshotting a controller the week of the review, the site and circuit numbers are already sitting on the company record when you open it.

One key, every location

Most network tooling asks for a credential per controller, which is unworkable across a book of accounts. Ubiquiti's Site Manager service is scoped to the UniFi account instead, so a single key created once reads every console that account reaches. There is no region to choose, no per-site login, and no VPN into a partner's LAN — the whole feed runs against one public endpoint.

What data flows

• Consoles — the roster of UniFi devices that run each location, matched to your companies so every signal below lands on the right record.
• Sites — device and client counts, offline devices, offline gateways, devices awaiting firmware, and UniFi's own critical-notification count for each site.
• Devices — every gateway, switch, access point and camera, with model, firmware version, whether an update is offered, and online state.
• Gateway posture — the gateway model and whether intrusion prevention and traffic inspection are switched on at that site.
• The WAN circuit — the carrier's name, the uptime percentage, and hour-by-hour readings kept for ninety days.

The feed is one-way. Current does not adopt or restart devices, block a client, edit a firewall rule, change a network or an SSID, or issue a hotspot voucher. Those endpoints are not in the connector's code, so they cannot be reached by a bug either. UniFi stays the source of truth for management; Current uses the evidence.

The circuit, not just the LAN

This is the part no endpoint tool can tell you. Network discovery reports on the switches and access points it finds inside a building. UniFi reports on the line into it: which carrier serves the site, and how much of the week that line was actually up. In a business review that is the difference between your switches were fine and your internet dropped on the 14th, and here is who provides it — a conversation a partner recognises, because they felt that outage.

Unknown reads as unknown

A site UniFi returns without its statistics block reads unknown in Current, not healthy. A missing WAN uptime figure stays blank rather than defaulting to a hundred percent, because a missing figure is exactly what an unreadable site looks like, and printing a green hundred there would paint a dead circuit as a good one. The same rule applies to a console whose device list a permission gap hides: Current says the devices are not visible to the connected account, rather than reporting a zero somebody would repeat in a review.

Numbers with a unit, and numbers without

Ubiquiti publishes WAN uptime as a percentage and names it as one, so Current shows it. It publishes latency, packet loss and downtime without saying what unit they are in. Current stores those readings and holds them off partner-facing surfaces until the unit is confirmed, rather than printing a confident 14 ms against a number whose scale nobody has verified. It is a small restraint that keeps a review from carrying a figure an engineer can disprove.

Matching consoles to companies

One UniFi console is normally one partner premises, so that is the unit Current maps; a partner with several locations behind one console becomes one company with several site rows. Current tries the automatic name match first, but UniFi labels are hostnames and hardware names rather than company names, so most consoles are placed by hand — a one-time job on the mapping panel. A mapping set by hand is never overwritten by a later automatic match, and mapping a console attaches its sites, devices and circuit readings immediately instead of waiting for the next scheduled sync.

Where the data appears

• In Strategic Business Reviews, in the fleet and network chapter alongside your other network feeds such as Cisco Meraki and Fortinet.
• On the company record, where the network panel shows sites, devices, how many are offline and how many await firmware.
• On the company's network estate card, with each site's carrier and WAN state and the devices that need attention first.
• In the company alert band, where a gateway offline reads critical and clears itself once the site comes back.

Why it matters

The network section is where most business reviews go quiet, because the evidence lives in a controller nobody opens during the meeting. An MSP running UniFi for a partner like Northwind Traders can open the account and see three sites, forty-seven devices with two offline and five waiting on firmware, the carrier on each circuit and how much of the month that circuit held — without anyone logging into a controller first. The review becomes a conversation about what the network did rather than about where the numbers came from.