Overview

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

What data is pulled

Connected clients

For each WiFi client connected to a Meraki 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
• 802.1x username -- if the network uses enterprise authentication (e.g., RADIUS), the authenticated username is available and can be used as an additional signal for user matching

Access points

Pult syncs access point data from your Meraki organization:

• AP name, serial number, and MAC address
• Network labels -- each Meraki network becomes a flat label that can be used in location mapping rules to match clients by network in addition to subnet

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.

Non-wireless device override (pult-wifi-ap tag)

Some offices route WiFi traffic through a non-wireless Meraki device -- for example, an MX appliance acting as an upstream for external access points. By default, Pult only considers clients connected to wireless Meraki devices.

To include clients connected through a non-wireless device, tag that device with pult-wifi-ap in the Meraki Dashboard. Pult will then treat the tagged device as a WiFi access point, and clients connected through it will be included in WiFi Presence detection.

The tag is case-insensitive (e.g., Pult-WiFi-AP works too).

Multi-organization support

If the API key has access to multiple Meraki organizations, Pult pulls client and AP data from all of them. All networks of type Wireless or Appliance are included automatically.

How sync works

• Pult polls the Meraki Dashboard 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

• A Cisco Meraki cloud-managed network.
• An admin account (or a dedicated service account) with Organization Observer and Network Observer roles.
• 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.