A property-change start trigger is an EVENT_BASED eventFilterBranches entry with filterBranchType: UNIFIED_EVENTS, eventTypeId: "4-655002", operator: HAS_COMPLETED and an hs_name IS_EQUAL_TO <property> filter. It re-enrolls the same record on every change, custom objects included.
Measured
More facts from this area
- In the Automation v4 spec, an
AB_TEST_BRANCHaction routes each path throughtestBranches[].connection.Source pending - The workflow action-type catalog (
GET /automation/2026-09-beta/action-types) carries each type'sactionTypeId,name,groupand input names only. It has no field that says an action is Breeze, uses AI, or consumes credits, so credit-using actions can only be recognized from a curated list of ids.Measured - The action-type catalog
GET /automation/2026-09-beta/action-typesdoesn't list the classic actions0-3(task),0-8(internal email) or0-11(rotate owner), though flows using them save and run.Measured - Add to static list is workflow action
0-63809083at version 5, withfields: { listId, targetObject: "{{ enrolled_object }}" }.Source pending - A multi-checkbox "add to existing values" edit (
0-5) isvalue: { type: APPEND_OBJECT_PROPERTY, appendPropertyName }, and it works together withassociation. A guessedfields.appendValueis silently dropped.Measured
Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]