BusyBot
Search all guides

Reference · Credentials

Connect Philips Hue to BusyBot

Used by 1 BusyBot node.

Type philipsHueOAuth2 6 fields

Fields

FieldTypeRequiredNotes
Access Token
accessToken		 password Yes OAuth2 access token obtained from the Hue authorization flow. Expires after 24 hours.
Refresh Token
refreshToken		 password Yes OAuth2 refresh token for automatic token renewal when the access token expires.
Client ID
clientId		 string Yes OAuth2 client ID from the Philips Hue developer portal.
Client Secret
clientSecret		 password Yes OAuth2 client secret from the Philips Hue developer portal.
App ID
appId		 string Yes The Philips Hue Remote API application ID, registered at https://developers.meethue.com/
Token Expiry (Unix timestamp)
expiresAt		 string No Unix timestamp (seconds) when the access token expires. Managed automatically after refresh.

Setting up Philips Hue OAuth2

  1. In Philips Hue OAuth2, create the credential this connection needs — the values listed in the table above. These are issued from your own Philips Hue OAuth2 account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Philips Hue OAuth2.
  3. Paste each value into the matching field and save.
  4. Add the Philips Hue node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Philips Hue credentials?

One node: Philips Hue. Create the credential once and select it in that node.

What does a Philips Hue credential need?

6 fields: Access Token, Refresh Token, Client ID, Client Secret, App ID, Token Expiry (Unix timestamp). Required: Access Token, Refresh Token, Client ID, Client Secret, App ID. The values come from your own Philips Hue account.

How are Philips Hue secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Does Philips Hue use OAuth?

Yes. This credential connects through OAuth (fields: Access Token, Refresh Token, Client ID, Client Secret, App ID, Token Expiry (Unix timestamp)): you approve access in Philips Hue, and the resulting tokens are stored encrypted like every other credential.

Nodes that use Philips Hue OAuth2

One credential works across every node below — create it once and reuse it.