Philips Hue

undefined

Detail	Value
Category	IoT
Base URL	https://api.meethue.com/route/clip/v2
Authentication	Bearer Token
Endpoints	7
Connector key	philips-hue

Using Philips Hue in a workflow

1. Go to Connections and click New Connection.
2. Pick Philips Hue from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Lights
GET	Rooms
GET	Zones
GET	Scenes
GET	Grouped Lights
GET	Devices
GET	Bridges

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Lights

Detail	Value
Operation ID	lights_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select lights_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Rooms

Detail	Value
Operation ID	rooms_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select rooms_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Zones

Detail	Value
Operation ID	zones_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select zones_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Scenes

Detail	Value
Operation ID	scenes_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select scenes_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Grouped Lights

Detail	Value
Operation ID	grouped_lights_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select grouped_lights_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Devices

Detail	Value
Operation ID	devices_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select devices_5.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.

GET

Bridges

Detail	Value
Operation ID	bridges_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Philips Hue connection from the Connection dropdown.
3. In the Operation dropdown, select bridges_6.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Philips Hue API reference.