Overview

Pult Presence integrates with Aruba Central to retrieve connected WiFi client and access point data. The integration is read-only -- Pult periodically polls the Aruba Central API to detect which devices are on the network.

What data is pulled

Connected clients

For each wireless client currently connected to your Aruba network, Pult retrieves:

• 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 category -- whether the device is a computer, smart device, or other type
• Client hostname -- the device's hostname (when available)
• 802.1x username -- if the network uses enterprise authentication, the authenticated username is available and can be used as an additional signal for user matching

Access points

Pult syncs access point data and location hierarchy from Aruba Central:

• AP name, serial number, and MAC address
• Building and floor labels -- If your Aruba Central deployment has VisualRF configured, Pult automatically imports a hierarchical label structure (buildings containing floors). These labels can be used in location mapping rules for fine-grained location matching. If VisualRF is not configured, labels are simply not available -- this does not affect client data.

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 and AP are then evaluated against location mapping rules to determine the presence location.

The hierarchical building/floor labels from Aruba Central are particularly useful for organizations with multiple floors or wings in the same building -- you can create location mapping rules that combine subnet conditions with floor-level AP labels.

How sync works

• Pult polls the Aruba Central 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.

Requirements

• An Aruba Central cloud-managed deployment.
• Access to HP GreenLake for creating a service account.
• A service account with Workspace Observer (GreenLake) and Aruba Central View Only roles. You can optionally add resource restrictions to limit Pult's access to specific networks.
• At least one MDM integration (or manual device list) to map WiFi clients to users.
• Location mapping rules configured to map client subnets (and optionally building/floor labels) to presence locations.

Next steps

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