Overview

Pult Presence integrates with UniFi (Ubiquiti) to retrieve connected WiFi client data. Unlike Cisco Meraki and Aruba Central, UniFi uses a self-hosted controller rather than a cloud API, which requires additional network configuration to allow Pult to reach the controller.

What data is pulled

Connected clients

Pult retrieves both currently active and recently connected WiFi clients from your UniFi controller:

• WiFi MAC address -- the client device's MAC address
• IP address -- the client's network IP
• Associated access point -- which AP the client is connected to
• Last connection time -- when the client was last seen
• Client hostname -- the device's hostname (when available)

UniFi does not provide 802.1x usernames through its API. User matching relies entirely on MAC address matching with MDM device data.

Access points

AP label groupings are not available through the UniFi integration. Location matching relies solely on client IP subnets in location mapping rules.

Multi-site support

If the UniFi controller manages multiple sites, Pult pulls client data from all accessible sites automatically.

Capabilities

WiFi Presence detection

Pult uses the connected client data to detect office presence:

Client MAC address → MDM device → user email → Pult user

For each connected WiFi client, Pult matches the client's MAC address against device records from your MDM integration. If a match is found, the WiFi activity is attributed to the corresponding user. The client's IP address is then evaluated against location mapping rules to determine the presence location.

How sync works

• Pult polls the UniFi controller API periodically. There are no webhooks or real-time push.
• API credentials are validated on save -- invalid credentials will be rejected immediately.
• If authentication fails repeatedly, the integration is automatically paused until an admin resets it from the Pult Dashboard.

Authentication options

UniFi supports two authentication methods (choose one during setup):

• Local user credentials -- A username and password for a local read-only user on the UniFi controller. Recommended for most setups.
• API token -- A static API token generated in the UniFi controller. A simpler alternative for newer UniFi setups (Dream Machine, Cloud Key Gen2+) that support API key authentication.

Requirements

• UniFi OS version 4.2.x or later.
• UniFi Network Controller version 9.1.x or later.
• A fixed/static public WAN IP at the site where the controller is hosted.
• Port forwarding configured to allow Pult's IP address (3.73.170.193) to reach the controller API.
• Firewall rules restricting inbound access to Pult's IP only.
• At least one MDM integration (or manual device list) to map WiFi clients to users.
• Location mapping rules configured to map client subnets to presence locations.

Next steps

See the Setup Guide for step-by-step instructions on configuring the integration.