Skip to main content
Choose an operator by the path you need:

Route values

Use filter when the condition depends only on the value. Use gate when another signal supplies the condition. Use partition when both the matching and remaining paths do work.
automations/route-requests.automation.ts
Exactly one partition emits. The other closes, so actions attached to that path don’t run.

Route declaration sections

Use branch when an entire synchronous section changes:
Don’t declare triggers inside branch or withPrerequisites. Each trigger starts an independent root context. Use correlate to join related occurrences from separate triggers.

Keep runs and declarations readable

Use markSignificant when an emitted signal should keep its connected run visible in Recent runs. Use scope to isolate durable hook numbering without changing execution. Use group when the same section also needs a name and initial presentation in run details.