Engine Primitives
Engine Primitives are pre-built, security-vetted building blocks you attach to your Yoke's transitions, states, and fields. Each one is a small, composable unit of "engine" logic that you configure via the Yoke Studio without writing any code.
Pick a primitive below to learn how to use it:
| Primitive | What it does | Tier |
|---|---|---|
| Aggregator | Roll up child records into a parent field — sum, count, average. | Solo+ |
| Notifier | Send email or webhook on transitions, state changes, or field updates. | Solo (email) / Pro (webhook) |
| Scheduler | Run transitions or other primitives on a cron schedule. | Pro |
| SLA Timer | Escalate stuck jobs after a fixed duration. | Pro |
| PDF Generator | Render PDFs from typst templates on transitions. | Pro |
| Approval Gate | Block transitions behind N-of-M approver votes. | Pro |
| Field Compute | Compute virtual fields at read time using formulas. | Solo+ |
| Field Mutator | Atomically increment, decrement, or set a field — with bounds. | Solo+ |
| Record Spawner | Create entity records as a side effect of events. | Pro |
| Cross-Entity Transition | Fire an FSM event on a related entity's job. | Pro |
Trigger predicates
Every primitive that fires on entity changes can use an optional trigger predicate to filter exactly when it runs — fire on a boolean edge, on a threshold crossing, or only when a specific value appears.