About Poly Lens
Poly Lens is HP’s cloud service for managing Poly devices, such as video conferencing systems, and the rooms and sites they’re placed in. This integration connects Serval to the Lens API so workflows can look up devices, rooms, and sites, and act on devices: reboot them, start or end calls, and collect logs. Authentication: Poly Lens API credentials, a client ID and client secret created in the Poly Lens Admin Portal. Serval stores the secret encrypted and exchanges the credentials for a Lens access token, which it adds to requests server-side, so workflows never handle the credentials or the token. Serval sends the credentials only to the Poly token endpoint,login.lens.poly.com, and the token only to the Lens API, api.silica-prod01.io.lens.poly.com.
Data sync: No background sync starts when you connect, and the integration has no installable workflows. Data access is on demand through workflows.
What the Poly Lens integration enables
Get your credentials
Serval needs a set of Poly Lens API credentials. Creating them requires Administrator permissions in Poly Lens.Open API Credentials
Add credentials for Serval
Name the credentials and choose a role
Serval, and choose a role. Lens uses the role to control what the credentials can access, so choose one that covers only what your workflows need. Select Confirm.Copy the Client ID and Client Secret
Connect in Serval
Open the Poly Lens connect form
Enter the Client ID
Enter the Client Secret
Save, then check the health check
Verifying the connection
The connection ships one health check that makes a live call to Poly Lens:- List Poly Lens Accounts: exchanges the credentials for an access token, then asks Lens for one account the credentials can reach. On success: “Successfully reached Poly Lens (accounts visible: 1).”
Gotchas and troubleshooting
The health check passes with 0 accounts visible
The health check passes with 0 accounts visible
The health check fails
The health check fails
Revoking credentials in Lens
Revoking credentials in Lens
Any GraphQL error fails the workflow step
Any GraphQL error fails the workflow step
Large queries can exceed Poly's cost limits
Large queries can exceed Poly's cost limits
Device search returns 10 devices per page by default
Device search returns 10 devices per page by default
deviceSearch returns 10 devices unless you set params.pageSize, up to 5,000. To read every device, pass pageInfo.nextToken back as params.nextToken until pageInfo.hasNextPage is false. Send the same pageSize on every page: Lens returns an error if it changes after the first request, including dropping it to fall back to the default.Some Lens queries are deprecated
Some Lens queries are deprecated
devices, searchDevices, rooms, and sites queries as deprecated. In workflows you write yourself, use deviceSearch, roomData, and siteData instead.Outbound network access
Outbound network access
login.lens.poly.com for access tokens and api.silica-prod01.io.lens.poly.com for the Lens API. If the Serval deployment or worker serving the connection restricts outbound traffic, allow HTTPS to both.Need help? Contact support@serval.com for assistance with your Poly Lens integration.

