Summary
Philips Hue is a command-based integration: instead of syncing data into Philips Hue, iPaaS.com record events trigger light commands on your Hue devices. Each mapping collection flashes a chosen Hue light when a record is added or updated in iPaaS.com. Two example collections ship with the integration — Hue BOPIS Blink (a new transaction flashes a light red) and New VIP Customer (a new or updated customer flashes a light blue).
ID Format
Manual Sync ID: on the iPaaS.com Manual Sync page, enter the iPaaS.com record ID for the triggering record — a transaction ID for Hue BOPIS Blink, or a customer ID for New VIP Customer (for example,
150713). That record carries the custom field with the light command.External ID Format: after a command is sent, iPaaS.com records the external ID as the issue timestamp —
Issued: MM/DD/YYYY HH:MM:SS(for example,Issued: 01/22/2023 12:33:00). It marks when the command was sent rather than linking to a Hue record, because Philips Hue does not return a persistent record for a light command.
Deleted Record Support
Not supported. Deleting a record in iPaaS.com does not send any command to Philips Hue — the delete operation performs no action, and delete mappings are not included in the collections.
Custom Field Support
This integration is configured entirely through custom fields. Each light command is a custom field you add to a mapping collection:
Name the custom field to exactly match the target device name in your Philips Hue app. The integration uses this name to find the light (or group) to control.
Set the value with a dynamic formula that returns a light state.
A light-state value controls an individual light; a group-action value controls a Hue group.
The integration provides these dynamic-formula helpers for building a light state:
Formula | Effect |
| Flash the target light red at full brightness, then turn it off after about ten seconds. |
| Flash the target light green at full brightness, then turn it off after about ten seconds. |
| Flash the target light blue at full brightness, then turn it off after about ten seconds. |
| Flash the target light at full brightness (no color change), then turn it off after about ten seconds. |
| Flash with a custom brightness, color, saturation, and effect; |
| Helper: convert an RGB color to the coordinates the light expects. |
| Helper: convert a hex color (for example, |
Add a custom field from the mapping editor with + Add Custom Field.
Mapping Collection Status
Both collections are Enabled. Neither collection has a mapping filter, so every triggered record produces a command.
Duplicate or Conflicting Mappings
Hue BOPIS Blink and New VIP Customer are companion command collections. Keep each collection pointed at the light and behavior you intend. If more than one active collection targets the same Hue light, the most recent command wins — review your collections before enabling additional ones.
Supported Child Collections
None. Both collections are standalone command collections with no child collections.
System Caveats
Philips Hue Caveats
Device name: the custom field name must match a light or group name in your Hue app exactly; a mismatch means no command is sent and no error is raised.
Reachability: the Hue Bridge must be online and the target light powered and connected, or the command has no visible effect.
Command only: the integration sends a light state; it does not read light status back or confirm the visible result.
No rate-limit rescheduling: each command is a single best-effort call. If the Philips Hue cloud API is temporarily rate-limited or unavailable, the command is not automatically retried or rescheduled — it is simply not applied.
iPaaS.com Caveats
The triggering record must exist in iPaaS.com and must carry the configured light-command custom field.
The subscription must be authenticated to Philips Hue (OAuth) before commands can be sent.
Setup Requirements
In the Philips Hue app, confirm your Bridge is online and note the exact name of the light you want to control.
Authenticate the iPaaS.com subscription to Philips Hue (OAuth) so the Access Token, Refresh Token, and Hue Bridge User are populated. See the Philips Hue Connections and Settings and Installation Instructions articles.
On the collection, add a custom field named exactly as your Hue light and set its value with a dynamic formula (for example,
FlashRed()).To run a collection automatically, subscribe to its outbound triggers in your subscription's Outbound Data Flows section — transaction/created (and optionally transaction/updated) for Hue BOPIS Blink, or customer/created and customer/updated for New VIP Customer. Manual Sync is available at any time without this step.
Integration Flow
A record is added or updated in iPaaS.com — a transaction for Hue BOPIS Blink, or a customer for New VIP Customer — either automatically (via a subscribed Outbound Data Flow) or through Manual Sync.
The integration reads the light-command custom field on the record: its name is the target device, its value is the light state to apply.
The integration retrieves the lights on your Hue Bridge and finds the one whose name matches the custom field name.
It applies the light state to that light — the light flashes and then turns off after about ten seconds. If no light matches, nothing happens and no error is raised.
iPaaS.com records the external ID as the issue timestamp (
Issued: ...).
Mappings
Hue BOPIS Blink
Flashes a Hue light red when a transaction is added in iPaaS.com. In the example, the target light is named Playbar.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Philips Hue) | Description |
Dynamic Formula |
| Playbar (light-command custom field) | Required. Flashes the Hue light named in the custom field (here, Playbar) red at full brightness. Rename the custom field to match your own Hue light. |
New VIP Customer
Flashes a Hue light blue when a customer is added or updated in iPaaS.com. In the example, the target light is named Mood Light.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Philips Hue) | Description |
Dynamic Formula |
| Mood Light (light-command custom field) | Required. Flashes the Hue light named in the custom field (here, Mood Light) blue at full brightness. Rename the custom field to match your own Hue light. |
Error Handling
This integration does not surface configuration-specific error messages. The most common outcome to be aware of is a silent skip: if the custom field name does not match any light or group on your Hue Bridge, the transfer completes without changing a light and without raising an error. If a command does not produce a visible result, confirm the device name matches exactly, the Bridge is online, and the target light is powered and connected.
Testing & Validation
Test Scenarios
In iPaaS.com, create or choose a triggering record (a transaction for Hue BOPIS Blink, or a customer for New VIP Customer) and confirm it carries the light-command custom field named for your Hue light.
Note the record's iPaaS.com ID.
Go to Integration Monitoring > Manual Sync, select the Philips Hue system and the collection, enter the record ID, and send the command.
Confirm the target Hue light performs the expected action (for example, flashes red or blue).
Change the formula (for example, from
FlashRed()toFlashBlue()) and re-send to confirm the new behavior.
Validation Checklist
The custom field name matches a light or group name in the Hue app exactly.
The subscription is authenticated to Philips Hue.
The Hue Bridge is online and the target light is reachable.
Additional Notes
This integration is outbound and command-only: it sends commands to Philips Hue and does not import Hue data into iPaaS.com.
Initialization is not supported; historical records are not replayed as commands.
Groups are supported in the same way as lights — set the custom field value with a group-action formula to control a Hue group.