Skip to main content
Automations are formulas embedded in an entity. They use Python syntax rather than a proprietary formula language — so instead of learning a custom expression builder, you write what you mean: 
entity.fields.mass = entity.fields.density * entity.fields.volume
Most automations start with a shorthand for readability: 
f = entity.fields
f.record_id = f"REC-{len(entity.get_field_refs())}"
Automations can calculate and update entity content and values: 
f = entity.fields
f.category = "Stability"

entity.status_tag = ("Expired", "danger")
Each automation is sandboxed to the entity it belongs to — it can only read and write fields on that entity. Automations cannot access other entities, external systems, or the wider platform. They are version-controlled through change sets and tracked in the audit trail like any other configuration change.

​
Field name access

Use dot notation with snake_case for simple field names: 
entity.fields.reactor_temp_C
Use bracket notation for field names that contain spaces or special characters: 
entity.fields["Temperature (°C)"]
entity.fields["Lot Number"] = "LOT-2026-001"
Both styles work for reading and writing. The platform automatically maps snake_case attribute access to the original field name, so entity.fields.reactor_temp_C and entity.fields["reactor_temp_C"] are equivalent.

​
Creating labels

Create PDF labels from entity data with configurable layouts. Requires the Label creation blueprint — see Creating labels blueprint.