Camera Goes Offline? ServiceNow Ticket Opens Itself.

Rhombus + Claude Series — Tying Into the Enterprise

A camera at a branch office stops working. In most organizations, nobody finds out for days — until someone needs footage that isn’t there. By then, the outage has become a customer-service problem, a compliance problem, or both.

This isn’t because your IT team isn’t watching. It’s because camera health lives in one system, and the ticket queue that actually drives facilities work lives in another. The two don’t talk. The gap between “camera failed” and “ticket filed” is entirely filled by humans noticing things.

Self-healing infrastructure is a standard pattern in software. It should be a standard pattern in physical security too.

Rhombus exposes camera health as structured data. ServiceNow exposes a ticketing API. Connecting the two is the entire project.

For the developers:

With Claude and the Rhombus plugin, the integration is a scheduled prompt:

“Check camera health across all sites. For anything offline more than 30 minutes, open a ServiceNow incident with the camera details at P3.”

Claude runs the health check, identifies outages, and creates tickets — each one pre-filled with location, hardware model, and last-seen timestamp.

The payoff: Failures get addressed before anyone notices they happened. Field technicians get dispatched with full context. And the gap between “the camera broke” and “someone is fixing it” closes to minutes — without adding a single person to the rotation.