UniFi: consoles, sites, devices and the WAN circuit

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. This connector reads four things out of Ubiquiti's Site Manager service — the consoles your UniFi account can see, the sites inside them, the devices on each site, and the hour-by-hour state of the WAN circuit — and hangs each one off the matching Current company. Current reads UniFi and can never change anything in it.

Unlike a per-site network tool, UniFi's Site Manager service is account-wide: one API key created on your UniFi account reads every console that account can see. You paste it once. There is no region to choose and no second credential per location.

1. 1
   1 · Sign in at unifi.ui.com

   Use the UniFi account that can see the consoles you manage. If your team's consoles are spread across several personal accounts, sign in with the account that reaches the most of them, or move them under one organization account first — see the warning above.
2. 2
   2 · Open Settings → API Keys

   The direct link is unifi.ui.com/settings/api-keys.
3. 3
   3 · Create a key and copy it immediately

   UniFi displays the key once, at creation, and never shows it again. Copy it before you leave the page; a lost key means creating a new one.

1. 1
   Open the UniFi card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link) and find UniFi in the Monitoring & security section.
2. 2
   Paste the API key and press Test connection

   That is the whole form — no region, no username, no client id. Current reads a single console back to prove the key works before it stores anything. If UniFi refuses, the card shows UniFi's own reason rather than a generic failure. On success the key is stored server-side only and the browser never sees it again.
3. 3
   Wait for the first sync, then map

   The first run lists every console the key can see. Because those labels are hostnames and hardware names rather than company names, expect to map most of them by hand — that is normal here, not a fault.

UniFi syncs every 6 hours on a schedule, plus whenever you press Sync now on the card. Each run walks the consoles first — so the mapping panel fills even if a later step runs out of time — then the sites, then the devices, then the last seven days of circuit readings.

Every request Current makes to UniFi passes through a read-only guard that permits exactly four read endpoints: the console list, the site list, the device list and the circuit metrics. Nothing else is reachable, including UniFi's connector passthrough — the one route that can reach a console's own management interface, and therefore adopt or restart a device, shut a switch port, block a client, reorder a firewall rule or change an SSID. That route is absent from the list and no part of the connector can construct its address, so a bug cannot reach it either. UniFi stays the source of truth; Current only reads.

In UniFi, one console is normally one partner premises, so that is what Current maps. A partner with several locations under one console appears as one company with several site rows, which is exactly how the company card wants to read it.

1. 1
   Open the mapping panel

   Integrations → UniFi → Manage → Customer mapping. It opens on the Unmapped tab.
2. 2
   Map a console to its company

   On an unmapped row press Map, type a few letters of the Current company, and pick it. That console's sites, devices and circuit readings attach to the company right away, rather than waiting for the next 6-hour sync.
3. 3
   Ignore anything internal

   For a console that should never map to a company — your own office, a lab, a bench unit — press Ignore. It moves to the Ignored tab and stops counting against the card's unmapped badge.
4. 4
   Fix a wrong match later

   The Mapped tab lists every linked console; Unmap corrects a bad automatic match, and the Ignored tab's Un-ignore brings a dismissed one back. A mapping you set by hand is never overwritten by a later automatic match, and neither is a manual unlink.

• ＋The company's network panel: sites, devices, how many are offline and how many are waiting on firmware.
• ＋The company's network estate card: each site with its carrier and WAN state, and devices worst-first — offline, then alerting, then pending firmware.
• ＋The Fleet & network chapter of a Strategic Business Review, where the WAN uptime figure and the carrier name are the parts a partner recognises about their own building.
• ＋The company alert band: a gateway offline reads critical, several other devices offline reads a warning, and both clear themselves once UniFi reports the site back to normal.