Skip to main content
Every workflow has exactly one trigger node. It defines which entities, filtered by tags, start a run. 
{
  "nodeType": "TRIGGER",
  "entityType": "PRODUCT",
  "includeTags": ["fast-mover"],
  "excludeTags": ["discontinued"]
}

​
Fields

FieldMeaning
entityTypeWhat kind of entity triggers the workflow: PRODUCT, PRODUCT_VARIANT, BRAND, or INVENTORY_ITEM.
includeTagsThe entity must carry all of these tags.
excludeTagsThe entity must carry none of these tags.

​
How matching works

At run time, the data platform finds entities of entityType that match the tag filters (have every includeTags tag and none of the excludeTags). The resulting list is recorded on the run as matchedEntityIds (part of the run’s trigger context), and the downstream actions operate over those entities. The first matched entity is also exposed to interpolation as {{trigger.entityId}}, and the entity kind as {{trigger.entityType}} — see interpolation.
Tags are produced manually or by tagging rules. A workflow is therefore the “act” half of the detect → classify → automate loop: alerts and tags classify, workflows react.