Data & Storage · Integration
LIFX
Add LIFX to your product for your customers, and give your AI agents governed access to it.
Embed a LIFX integration so your customers can have your product control the lights they already own, using their own LIFX account rather than a shared key. Every account has a different set of lights and groups, so selectors are configuration per customer instead of code. fastn handles per-customer credentials, retries, rate limits and API upkeep, so a customer with an unusual setup needs no release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own LIFX account so your product controls the lights they already own.
Read the lights and groups on an account so your product shows what can be controlled.
Set power, brightness and colour on a light or group when something happens in your product.
Activate a saved scene so a customer's own setup is reused instead of recreated in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists the available lights and groups before choosing what to change.
An agent sets a scene or state within governed permissions, with each action logged.
Every call runs under the customer's own credentials, so nothing is controlled through a shared account.
Example prompt
List the lights in the studio group and set them to 40 percent warm white.
Set up LIFX in 4 steps
- 01Open the LIFX connector from your fastn dashboard.
- 02Have each customer authenticate their own LIFX account.
- 03Map the lights, groups and scenes your product may control, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the LIFX integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a LIFX integration without building it. Your customers connect their own LIFX account inside your product and control their lights, groups and scenes there, with no per-customer code on your side.
- Handle the part that actually costs time: a bulb is either reachable or it is not, and a command that silently fails looks identical to one that worked. fastn owns the auth, token refresh and API upkeep, so a LIFX change is not your on-call problem.
- One integration serves your product and your agents. The same governed LIFX connection powers in-product features and gives AI agents scoped, audited access, so a scene set by an agent is attributable.
Used by these teams
Works well with
AWS Lambda
Twilio
SlackOften used alongside
Tools the same teams tend to run next to LIFX, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceLIFX integration FAQ
How do I add a LIFX integration to my product?
Enable the LIFX connector in your fastn dashboard, then let each customer authenticate their own LIFX account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LIFX client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own LIFX account?
Yes. Every connection is scoped to the individual customer, so each authorises their own LIFX account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this LIFX integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists the available lights and groups before choosing what to change.
Who maintains the LIFX integration?
fastn does. When LIFX changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
What happens when a light is offline?
The call reports that the light was unreachable rather than silently succeeding. That matters more here than in most integrations, because a scene that did not apply looks exactly like one that did unless the result is surfaced.
What can I build with the LIFX integration?
A common starting point: connect their own LIFX account so your product controls the lights they already own. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the LIFX integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LIFX does not change your per-connector cost. You can start free with 3 connected accounts.
Add LIFX to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.