LIFX
Utilities & PersonalConnect AI agents to LIFX smart lights, controlled through the LIFX cloud HTTP API. Agents set colors and brightness, activate scenes, and run effects so a flow can signal state in the physical room.
What This Integration Enables
LIFX lights are controlled here through the LIFX cloud HTTP API, which means an agent is changing a physical room it has no way to see. That framing matters more than the feature list. Every action targets lights with a selector string, and the selector is the whole design: all reaches every light on the account, while label:Kitchen, group:Office, location:Home, and id:d073d5xxxxxx narrow it, and up to 25 selectors can be combined with commas. One word separates a status color on an office group from the same color applied to a family's bedrooms, and the API will carry out either instruction without comment. The connector is also honest about hardware classes in a way that catches flows out: Move Effect targets multizone devices such as LIFX Z and Beam, Morph Effect and Flame Effect target matrix devices such as Tile and Candle, and Clean targets LIFX Clean bulbs. Send any of those to incompatible hardware and nothing visible happens.
Fifteen actions cover the full surface. List Lights reads power, color, brightness, connectivity, group, location, and product capabilities, and Validate Color resolves a LIFX color expression such as "red", "#ff0000", "hue:120 saturation:1", or "kelvin:3500" into its components before you rely on it. Set State writes absolute values across a selector, Set States writes up to 50 different state objects in one request, and State Delta applies relative adjustments that are added to current values and clipped to range, which is the right tool for stepping brightness down rather than jumping it. Toggle Power flips a selector without needing to know its current state. Breathe Effect and Pulse Effect fade or flash between colors on standard bulbs. Cycle advances through 2 to 10 predefined states on each call, which is how you build a next-scene button. List Scenes and Activate Scene reach the scenes saved in the account's LIFX cloud. Clean starts or stops an HEV cycle. The API publishes no event subscription, so this service ships no triggers and the lights never tell a flow anything; every change starts from a schedule or from a state some other system reported.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Pipeline health rendered on the office wall
A team runs a build and deploy pipeline and wants its state visible without anyone watching a screen. On a schedule the agent reads pipeline status, resolves the intended color through Validate Color so a malformed expression fails at validation rather than halfway through a room, then calls Set State against group:Office with a green at kelvin 3500 for healthy and a red for a failing main branch. Pulse Effect is reserved for the transition into failure, because a flash means something the first time and nothing the tenth. Before writing, the agent calls List Lights on that selector and checks connectivity, since a light that is offline will silently not change and leave the room showing yesterday's state. Failures also post to Slack, because a color tells you that something is wrong and never what.
Different rooms, different meanings, one request
An operations team wants three surfaces showing three different things: the support queue in one room, warehouse throughput in another, and on-call status at a desk. Set States handles this in a single request, carrying up to 50 state objects each with its own selector plus any of the Set State fields, with an optional shared defaults object applied to all of them. The agent composes the three selectors from group names it first confirmed through List Lights, applies a shared duration so all three transition at the same rate, and writes once. State Delta covers the softer version of the same job, dimming a room in steps as the working day ends rather than snapping it to a value.
A saved scene as the end of a working day
The team keeps an "Evening" scene in the LIFX cloud with per-device states already tuned. At the end of the day the agent calls List Scenes to resolve the scene UUID by name rather than hard-coding it, since a scene edited or recreated in the app gets a new UUID and a stale one fails quietly. Activate Scene then transitions every light in the scene to its stored state over a duration, with Ignore used to leave power untouched so the scene does not switch on lights in an empty room, and Overrides applied where a shared brightness needs to sit on top. What the flow does not do is start a clean cycle at the same time, and that distinction is the next section.
Human-in-Loop Highlight
Clean is the action that does not belong to lighting at all. On LIFX Clean bulbs it starts an HEV cycle, using high-energy visible light to sanitize a room, and the connector will start one with a single call: leave Stop off, set a duration, done. A duration of 0 uses the device's default cleaning time, which means an agent that omits a value has not chosen a short cycle, it has chosen whatever the device decides. Now look at what the connector can tell you about that room. List Lights reports power, color, hue, saturation, kelvin, brightness, connectivity, group, location, and product capabilities. It does not report occupancy, and nothing else in the action list does either. There is no motion field, no presence signal, and no door state. The agent is being asked to run a sanitizing cycle in a physical space while being structurally blind to whether anyone is standing in it. Everything else here is recoverable in seconds: a wrong color is one Set State away from being right, a bad effect is stopped by setting cycles to 0 or duration to 0, a scene applied to the wrong group is undone by applying the right one. A clean cycle is the only operation on this connector where the recovery is not another API call. So the agent gates it, and gates it on the thing it cannot see. Before Clean runs, it calls List Lights on the target selector to confirm the bulb is connected and to name the group and location it resolves to, then posts to the facilities owner in Slack: "Ready to start an HEV clean cycle on 2 LIFX Clean bulbs, group Meeting Room 2, location Head Office, for 45 minutes starting now. LIFX reports both connected. I have no occupancy signal for that room and no way to get one from this connector. Confirm the room is empty and stays empty, or tell me a window to run it in." A person answers, and only then does the cycle start. The selector itself sits behind a lighter version of the same discipline: a flow authorized to write group:Office should never be able to expand to all, because on a personal LIFX account all includes a house. This is the digital andon cord applied to the one operation on the page that reaches past a color and into a room.
Agent Capabilities
15 actionsReading and Validation
3- List Lights Lists lights matching a selector along with their full state: power, color (hue, saturation, kelvin), brightness, connectivity, group, location, and product capabilities. Use the selector "all" for every light on the account, or narrow with "label:", "group:", "location:", or "id:". Read-only, and the right first call before any write, because it is how a flow learns what a selector actually resolves to.
- Validate Color Validates and resolves a LIFX color string (for example "red", "#ff0000", "hue:120 saturation:1", or "kelvin:3500") into its parsed hue, saturation, brightness, and kelvin components. Confirms an expression is valid before it is applied in Set State or an effect. Changes nothing.
- List Scenes Lists all scenes stored in the account's LIFX cloud, including each scene's UUID, name, and the per-device states it will apply. Resolve UUIDs here rather than hard-coding them, since a scene rebuilt in the app gets a new UUID. Read-only.
State
4- Set State Sets the power, color, brightness, and infrared level of the lights matching a selector, transitioning over an optional duration. Every field except the selector is optional and omitted fields are left unchanged, so a flow can adjust brightness without disturbing color.
- Set States Sets different states across multiple selectors in a single request, up to 50 state objects, with an optional shared defaults object applied to every state. Each state is an object containing a "selector" plus any of the Set State fields. Use it when several groups need different looks at the same instant.
- State Delta Applies a relative adjustment to the current state of the matching lights. Brightness, saturation, hue, kelvin, and infrared values are added to the current values and clipped to their valid ranges rather than set absolutely. The right choice for stepping a room down over an hour rather than jumping it.
- Toggle Power Toggles the power of the matching lights over an optional duration. If any of the selected lights are on, they all turn off; if all are off, they all turn on. Useful when a flow wants a switch without first reading state.
Effects
6- Breathe Effect Runs a slow breathe effect that smoothly fades the matching lights between a starting color and a target color, with control over the cycle length (period), the repeat count (cycles), and where the brightness peak sits within each cycle (peak). Works on standard color bulbs.
- Pulse Effect Runs a pulse effect that flashes the matching lights between a starting color and a target color with sharp transitions, with control over period and cycles. Works on standard color bulbs. Worth rationing, since a flash that happens constantly stops being a signal.
- Move Effect Runs the move effect on LIFX multizone devices such as LIFX Z and Beam, animating the current zone colors along the strip in a chosen direction. Set cycles to 0 to stop the effect, or omit it to run indefinitely. Has no visible effect on non-multizone lights.
- Morph Effect Runs the morph effect on LIFX matrix devices such as Tile and Candle, smoothly blending a palette of colors across the light's zones. Provide a palette of LIFX color strings or omit it to use the default spectrum. Set duration to 0 to stop, or omit it to loop indefinitely.
- Flame Effect Runs the flame effect on LIFX matrix devices such as Tile and Candle, producing a flickering fire-like animation across the light's zones. Set duration to 0 to stop, or omit it to run indefinitely.
- Cycle Advances the matching lights through a list of predefined states each time it is called, which is how a flow builds a next-scene button. Provide 2 to 10 state objects; on each call the lights move to whichever state does not match their current one, in the given direction. An optional defaults object supplies shared values.
Scenes and Clean
2- Activate Scene Activates a saved scene by its UUID, transitioning every light in the scene to its stored state over an optional duration. Use Ignore to leave properties such as power untouched, and Overrides to apply shared values on top of the scene. Get UUIDs from List Scenes.
- Clean Starts or stops a HEV clean cycle on LIFX Clean bulbs, which use high-energy visible light to sanitize a room. Leave Stop off and set a duration to start a cycle; enable Stop to end an active cycle early. A duration of 0 uses the device's default cleaning time. Only affects LIFX Clean-capable bulbs, and it is the one action here that should never run without a person confirming the room is empty.
Frequently Asked Questions
What can FlowRunner do with LIFX?
FlowRunner agents can run List Lights, Validate Color, and List Scenes in LIFX, plus 12 more actions.
Does connecting LIFX to FlowRunner require OAuth?
No. LIFX connects to FlowRunner with an API key, no OAuth flow required.
Can LIFX trigger a FlowRunner workflow automatically?
LIFX doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LIFX
$100 in credits. No card required. Connect in minutes.