Philips Hue
Utilities & PersonalControl and read Philips Hue smart lighting through the Hue Bridge CLIP v2 API. Control lights, grouped lights, rooms, zones, and scenes, and read devices and sensors. Authenticates with a hue-application-key header sent to the bridge local IP.
What This Integration Enables
FlowRunner agents use Philips Hue to bring a physical room into an operational workflow. On the read side an agent can get lights, grouped lights, rooms, zones, and scenes, and read devices along with motion, temperature, and light-level sensors, so a flow can branch on presence or ambient conditions. On the control side it can set a single light's state, set a grouped light for a whole room or zone at once, and activate a stored scene. Set Light State and Set Grouped Light build the CLIP v2 body from only the fields you supply, so power, brightness, color, color temperature, and transition can change independently. Get Bridge doubles as a connection check for the bridge IP, key, and local TLS reachability. What the connector does not do is drive every physical change unchecked. When a lighting change affects a shared space or timing matters, the agent runs what is routine and asks a person before the rest.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Sensor-Driven Lighting
A schedule or an upstream signal starts the flow. The agent reads a motion sensor with Get Motion Sensors and the ambient level with Get Light Level, compares them against the expected condition, and, when the room is empty or occupied as expected, applies a routine change with Set Grouped Light. The room responds to conditions without anyone touching the app.
Status Signaling
When a build, a deploy, or an alert fires from another service, the agent recalls a colored scene with Activate Scene or flashes a room with Set Grouped Light to signal the state at a glance. It reads the current state first, then applies a short, low-risk change. The room becomes a status indicator without a dashboard.
Confirmed Shared-Space Change
An agent is about to make a lighting change that other people in a shared room will experience, such as switching every light off in an occupied office or recoloring a zone during a meeting. Reading state and preparing the change happens automatically. The change to the shared space does not. The agent holds it for a person to confirm, then calls Set Grouped Light or Activate Scene once the confirmation comes back.
Human-in-Loop Highlight
When a workflow reaches a lighting change that other people in a shared space will experience, such as switching every light off in an occupied room, recoloring a zone during a meeting, or recalling a scene that changes the mood others depend on, the agent does not run it on its own. It pauses and routes to the responsible person through their preferred channel: "The workflow wants to run [action] on [room or zone], which will change the space by [effect]. Current state: [reading]. Confirm the change, or hold?" The person confirms, and only then does the agent call the action. The reads and the routine, low-risk changes keep running automatically; the physical changes others share get a human first.
Agent Capabilities
15 actionsLights
3- Get Lights Retrieves all light resources on the bridge, including on/off state, brightness, color, and color temperature, each addressed by its rid. Used to read light state and pick a light by name.
- Get Light Retrieves a single light by its rid, returning full state. Used to load one light's state before acting on it.
- Set Light State Updates a single light by its rid, sending only the fields you provide: power, brightness (0-100 percent), color as CIE xy coordinates, color temperature in mirek, and a transition duration. Used to change one light, and a physical change worth a human confirmation in a shared space.
Grouped Lights
2- Get Grouped Lights Retrieves all grouped_light resources, each aggregating a room or zone's on/off and dimming state. Used to read the combined state of a group.
- Set Grouped Light Updates a grouped_light by its rid, applying the change to every light in the room or zone at once, using the same fields as Set Light State. Used to control a whole room, and a physical change worth a human confirmation in a shared space.
Rooms & Zones
3- Get Rooms Retrieves all room resources, each grouping devices by physical location and referencing a grouped_light service. Used to discover rooms and the group that controls them.
- Get Room Retrieves a single room by its rid, including its child devices and its grouped_light service. Used to load one room's structure.
- Get Zones Retrieves all zone resources, each a flexible grouping of lights not tied to physical location. Used to discover zones that can span rooms.
Scenes
2- Get Scenes Retrieves all scene resources, each storing a set of light states for a room or zone. Used to find a scene's rid before recalling it.
- Activate Scene Recalls a scene by its rid, applying its stored light states to the associated room or zone. Used to set a room's lighting in one call, and a physical change worth a human confirmation in a shared space.
Devices & Sensors
4- Get Devices Retrieves all device resources on the bridge with their product metadata and the service resources they expose. Used to map devices to the lights and sensors they provide.
- Get Motion Sensors Retrieves all motion sensor resources, each reporting whether motion is detected. Used to drive presence-based logic.
- Get Temperature Retrieves all temperature sensor resources, each reporting the current temperature in Celsius. Used to read ambient temperature into a flow.
- Get Light Level Retrieves all light_level sensor resources, each reporting the measured ambient light level. Used to drive daylight-aware lighting.
Bridge
1- Get Bridge Retrieves the Hue Bridge resource, including its bridge_id. Used as a connection check to confirm the bridge IP, application key, and local TLS reachability.
Start building with Philips Hue
$100 in credits. No card required. Connect in minutes.