Entity Type Switch

Use this node to fan out a rule chain that processes messages from multiple entity types. Unlike the Entity Type Filter (which gives True/False), this node routes directly via a connection whose label matches the entity type’s human-readable name — so you can wire separate downstream paths for Device, Asset, Customer, and so on without writing any script.

Configuration

This node requires no configuration.

Message processing algorithm

Determine the incoming message’s originator entity type.
Look up the type’s normal (human-readable) name.
Route the message via the connection whose label exactly matches the normal name.

Entity type name mappings

Entity type	Connection label
`DEVICE`	Device
`ASSET`	Asset
`ENTITY_VIEW`	Entity View
`CUSTOMER`	Customer
`TENANT`	Tenant
`USER`	User
`DASHBOARD`	Dashboard
`RULE_CHAIN`	Rule Chain
`RULE_NODE`	Rule Node
`EDGE`	Edge
`AI_MODEL`	AI model

Output connections

Connection	Condition
(normal name of entity type)	Always — the message is routed via the connection matching the entity type’s normal name.
`Failure`	An unexpected error occurred during processing.

Examples

Example 1 — Originator is `DEVICE` → `Device`

The originator entity type is DEVICE. Its normal name is Device, so the message is routed via Device.

Example 2 — Originator is `ENTITY_VIEW` → `Entity View`

The originator entity type is ENTITY_VIEW. Its normal name is Entity View, so the message is routed via Entity View.

Example 3 — Originator is `AI_MODEL` → `AI model`

The originator entity type is AI_MODEL. Its normal name is AI model, so the message is routed via AI model.

JSON schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "EmptyNodeConfiguration",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}